Re: log_autovacuum in Postgres 14 -- ordering issue

From: Nikolay Samokhvalov <samokhvalov(at)gmail(dot)com>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: 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-25 18:42:22
Message-ID: CANNMO+KszpK7b385y+g71k5vw=TVksCcTE5uU5Ba6gSyN0AoiQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Aug 25, 2021 at 10:34 AM Peter Geoghegan <pg(at)bowt(dot)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?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Pryzby 2021-08-25 19:29:51 Re: Autovacuum on partitioned table (autoanalyze)
Previous Message Jacob Champion 2021-08-25 18:41:39 Re: [PoC] Federated Authn/z with OAUTHBEARER