Re: Request for feature: VACUUM FULL updates pg_stat_all_tables.last_vacuum - Mailing list pgsql-admin

From Alvaro Herrera
Subject Re: Request for feature: VACUUM FULL updates pg_stat_all_tables.last_vacuum
Date
Msg-id 202405101121.lnko2euk3ohc@alvherre.pgsql
Whole thread Raw
In response to Re: Request for feature: VACUUM FULL updates pg_stat_all_tables.last_vacuum  (Nikolay Samokhvalov <samokhvalov@gmail.com>)
Responses Re: Request for feature: VACUUM FULL updates pg_stat_all_tables.last_vacuum
List pgsql-admin
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/



pgsql-admin by date:

Previous
From: Wells Oliver
Date:
Subject: Confirming pg_repack being successful
Next
From: Achilleas Mantzios - cloud
Date:
Subject: PostgreSQL on netapp AFF C250A storage ?