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

From Peter Geoghegan
Subject Re: log_autovacuum in Postgres 14 -- ordering issue
Date
Msg-id CAH2-WznGTL9WexqTo3nTuxtcKDvqhsUA3=qr99YvhJ2_NqgjwQ@mail.gmail.com
Whole thread Raw
In response to Re: log_autovacuum in Postgres 14 -- ordering issue  (Stephen Frost <sfrost@snowman.net>)
Responses Re: log_autovacuum in Postgres 14 -- ordering issue  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
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.)

-- 
Peter Geoghegan

Attachment

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: RFC: Improve CPU cache locality of syscache searches
Next
From: Stephen Frost
Date:
Subject: Re: log_autovacuum in Postgres 14 -- ordering issue