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

From Ron Johnson
Subject Re: Request for feature: VACUUM FULL updates pg_stat_all_tables.last_vacuum
Date
Msg-id CANzqJaC0Eev08o8nfG+AzV1UYDvC3Atm3TbnaHGx9mK2A2YT5A@mail.gmail.com
Whole thread Raw
In response to Re: Request for feature: VACUUM FULL updates pg_stat_all_tables.last_vacuum  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-admin
On Fri, May 10, 2024 at 7:21 AM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
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 --

I considered that, for the same reason. But there's no such thing as an unsorted CLUSTER, since the whole purpose of CLUSTER is to sort the data.

pgsql-admin by date:

Previous
From: Srinivasarao Oguri
Date:
Subject: Re: PostgreSQL on netapp AFF C250A storage ?
Next
From: Philippe Strauss
Date:
Subject: syntax error at or near "gist_trgm_ops" on debian