From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Ron Johnson <ronljohnsonjr@gmail.com>
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: Request for feature: VACUUM FULL updates pg_stat_all_tables.last_vacuum
Date: Thu, 09 May 2024 22:11:55 +0200
Message-ID: <d16beb9b163929894a35f2a9703bc29800b721f5.camel@cybertec.at> (raw)
In-Reply-To: <CANzqJaBDOrzCsd-hp15ya6JEScgqWYUhN5xUZBsUqZxWv9p6DQ@mail.gmail.com>
References: <CANzqJaBDOrzCsd-hp15ya6JEScgqWYUhN5xUZBsUqZxWv9p6DQ@mail.gmail.com>
On Thu, 2024-05-09 at 09:58 -0400, Ron Johnson wrote:
> Because vacuum is vacuum.
The problem is that the two commands do something different, so it
would be misleading. Renaming VACUUM (FULL) is a good idea in principle,
but I think that is more than 10 years too late. The compatibility
break would be too painful.
Perhaps you could write a patch to add a column "last_rewritten"
to "pg_stat_all_tables"...
Yours,
Laurenz Albe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: laurenz.albe@cybertec.at, ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: Request for feature: VACUUM FULL updates pg_stat_all_tables.last_vacuum
In-Reply-To: <d16beb9b163929894a35f2a9703bc29800b721f5.camel@cybertec.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox