From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
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:55:46 |
Message-ID: | 20210827195546.GN17906@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Greetings,
* Peter Geoghegan (pg(at)bowt(dot)ie) wrote:
> 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.)
Looks alright to me.
Thanks,
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2021-08-27 20:07:02 | Re: Queries that should be canceled will get stuck on secure_write function |
Previous Message | Peter Geoghegan | 2021-08-27 19:43:07 | Re: log_autovacuum in Postgres 14 -- ordering issue |