From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Nikolay Samokhvalov <samokhvalov@gmail.com>
Cc: Ron Johnson <ronljohnsonjr@gmail.com>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: Request for feature: VACUUM FULL updates pg_stat_all_tables.last_vacuum
Date: Fri, 10 May 2024 13:21:08 +0200
Message-ID: <202405101121.lnko2euk3ohc@alvherre.pgsql> (raw)
In-Reply-To: <CANNMO+K2ikym0DpV8CeDcoM9wvoThNVPxh7_xVC8_V=10o-kcw@mail.gmail.com>
On 2024-May-09, Nikolay Samokhvalov wrote:
> With RECREATE TABLE, one day, we would be probably have RECREATE TABLE
> CONCURRENTLY implemented, making pg_repack less needed.
If we really wanted to rename VACUUM FULL, I would go for a name that
betrays its CLUSTER implementation -- maybe CLUSTER UNSORTED or so --
and document it together with regular CLUSTER. We don't really need a
new top-level command for it IMO.
As for pg_repack, I'd much rather get VACUUM SQUEEZE using pg_squeeze as
an implementation starting point (without the scheduling stuff though.)
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
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: alvherre@alvh.no-ip.org, samokhvalov@gmail.com, ronljohnsonjr@gmail.com, laurenz.albe@cybertec.at, pgsql-admin@lists.postgresql.org
Subject: Re: Request for feature: VACUUM FULL updates pg_stat_all_tables.last_vacuum
In-Reply-To: <202405101121.lnko2euk3ohc@alvherre.pgsql>
* 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