Re: log_autovacuum in Postgres 14 -- ordering issue

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Nikolay Samokhvalov <samokhvalov(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz>
Subject: Re: log_autovacuum in Postgres 14 -- ordering issue
Date: 2021-08-27 19:43:07
Message-ID: CAH2-WznGTL9WexqTo3nTuxtcKDvqhsUA3=qr99YvhJ2_NqgjwQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Aug 27, 2021 at 12:30 PM Stephen Frost <sfrost(at)snowman(dot)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 Content-Type Size
v3-0002-Show-zero-values-in-track_io_timing-log-output.patch application/octet-stream 2.9 KB
v3-0001-Reorder-log_autovacuum_min_duration-log-output.patch application/octet-stream 5.5 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2021-08-27 19:55:46 Re: log_autovacuum in Postgres 14 -- ordering issue
Previous Message Andres Freund 2021-08-27 19:42:04 Re: RFC: Improve CPU cache locality of syscache searches