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

From Nikolay Samokhvalov
Subject Re: log_autovacuum in Postgres 14 -- ordering issue
Date
Msg-id CANNMO+KszpK7b385y+g71k5vw=TVksCcTE5uU5Ba6gSyN0AoiQ@mail.gmail.com
Whole thread Raw
In response to 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
On Wed, Aug 25, 2021 at 10:34 AM Peter Geoghegan <pg@bowt.ie> wrote:
It would be a lot clearer if the "buffer usage" line was simply moved
down. I think that it should appear after the lines that are specific
to the table's indexes -- just before the "avg read rate" line. That
way we'd group the buffer usage output with all of the other I/O
related output that summarizes the VACUUM operation as a whole.

The last two lines are also "*** usage" -- shouldn't the buffer numbers be next to them? 

pgsql-hackers by date:

Previous
From: Jacob Champion
Date:
Subject: Re: [PoC] Federated Authn/z with OAUTHBEARER
Next
From: John Naylor
Date:
Subject: Re: badly calculated width of emoji in psql