Re: a verbose option for autovacuum

From: "Euler Taveira" <euler(at)eulerto(dot)com>
To: "Masahiko Sawada" <sawada(dot)mshk(at)gmail(dot)com>, "Tommy Li" <tommy(at)coffeemeetsbagel(dot)com>
Cc: "Stephen Frost" <sfrost(at)snowman(dot)net>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: a verbose option for autovacuum
Date: 2021-03-08 15:57:36
Message-ID: 48bfe111-0de1-4295-957f-443e495732b9@www.fastmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Mar 8, 2021, at 2:32 AM, Masahiko Sawada wrote:
> * Proposed idea
> LOG: automatic vacuum of table "postgres.public.test": index scans: 1
> pages: 0 removed, 443 remain, 0 skipped due to pins, 0 skipped frozen
> tuples: 1000 removed, 99000 remain, 0 are dead but not yet removable,
> oldest xmin: 545
> indexes: "postgres.public.test_idx1" 276 pages, 0 newly deleted, 0
> currently deleted, 0 reusable.
> "postgres.public.test_idx2" 300 pages, 10 newly deleted, 0 currently
> deleted, 3 reusable.
> "postgres.public.test_idx2" 310 pages, 4 newly deleted, 0 currently
> deleted, 0 reusable.
Instead of using "indexes:" and add a list of indexes (one on each line), it
would be more parse-friendly if it prints one index per line using 'index
"postgres.public.idxname" 123 pages, 45 newly deleted, 67 currently deleted, 8
reusable.'.

> It still lacks some of what VACUUM VERBOSE shows (e.g., each index
> vacuum execution time etc) but it would be enough information to know
> the index page statistics. Probably we can output those by default
> without adding a new parameter controlling that.
Perfect is the enemy of the good. Let start with this piece of information.

--
Euler Taveira
EDB https://www.enterprisedb.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2021-03-08 15:59:01 Re: Yet another fast GiST build
Previous Message Ibrar Ahmed 2021-03-08 15:54:53 Re: [PATCH] New default role allowing to change per-role/database settings