Re: log_autovacuum in Postgres 14 -- ordering issue - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: log_autovacuum in Postgres 14 -- ordering issue
Date
Msg-id 20210827195546.GN17906@tamriel.snowman.net
Whole thread Raw
In response to Re: log_autovacuum in Postgres 14 -- ordering issue  (Peter Geoghegan <pg@bowt.ie>)
Responses Re: log_autovacuum in Postgres 14 -- ordering issue  (Peter Geoghegan <pg@bowt.ie>)
List pgsql-hackers
Greetings,

* Peter Geoghegan (pg@bowt.ie) wrote:
> On Fri, Aug 27, 2021 at 12:30 PM Stephen Frost <sfrost@snowman.net> wrote:
> > I don't particularly care for that explain rule, ultimately, but it's
> > been around longer than I have and so I guess it wins.  I'm fine with
> > always showing the read/write for VACUUM and ANALYZE.
> >
> > Including 'ms' and lower-casing 'Timings' to 'timings' still strikes me
> > as something that should be consistent for all of these, but that's
> > independent of this and I'm not going to stress over it, particularly
> > since that's pre-existing.
>
> Okay. Plan is now to push these two patches together, later on. The
> second patch concerns this separate track_io_timing issue. It's pretty
> straightforward.
>
> (No change to the first patch in the series, relative to the v2 from earlier.)

Looks alright to me.

Thanks,

Stephen

Attachment

pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: log_autovacuum in Postgres 14 -- ordering issue
Next
From: Robert Haas
Date:
Subject: Re: Queries that should be canceled will get stuck on secure_write function