Re: log_autovacuum in Postgres 14 -- ordering issue

On Wed, Aug 25, 2021 at 5:02 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> > I like it better than the current layout, so +1.
>
> This seems like a release housekeeping task to me. I'll come up with
> a patch targeting 14 and master in a few days.

Here is a patch that outputs log_autovacuum's lines in this order:

LOG: automatic vacuum of table "regression.public.foo": index scans: 1
pages: 9600 removed, 0 remain, 0 skipped due to pins, 0 skipped frozen
tuples: 2169423 removed, 0 remain, 0 are dead but not yet
removable, oldest xmin: 731
index "foo_pkey": pages: 5951 in total, 5947 newly deleted,
5947 currently deleted, 0 reusable
I/O timings: read: 75.394 ms, write: 76.980 ms
avg read rate: 103.349 MB/s, avg write rate: 73.317 MB/s
buffer usage: 47603 hits, 32427 misses, 23004 dirtied
WAL usage: 46607 records, 1 full page images, 15841331 bytes
system usage: CPU: user: 1.18 s, system: 0.23 s, elapsed: 2.45 s

I'll commit this in a day or two, backpatching to 14. Barring any objections.

Thanks
--
Peter Geoghegan