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

From Rui DeSousa
Subject Re: Request for feature: VACUUM FULL updates pg_stat_all_tables.last_vacuum
Date
Msg-id D8F01496-4E99-4EFE-B974-41861E3A0F69@icloud.com
Whole thread Raw
In response to Re: Request for feature: VACUUM FULL updates pg_stat_all_tables.last_vacuum  (Ron Johnson <ronljohnsonjr@gmail.com>)
List pgsql-admin


On May 9, 2024, at 4:39 PM, Ron Johnson <ronljohnsonjr@gmail.com> wrote:

On Thu, May 9, 2024 at 4:11 PM Laurenz Albe <laurenz.albe@cybertec.at> wrote:
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.

Make VACUUM (FULL) a synonym for RECREATE TABLE, then say in the docs that VACUUM (FULL) is deprecated.
 

I think if you rename vacuum full then vacuum compact would be better fit than recreate table.

pgsql-admin by date:

Previous
From: Ron Johnson
Date:
Subject: Re: Request for feature: VACUUM FULL updates pg_stat_all_tables.last_vacuum
Next
From: Nikolay Samokhvalov
Date:
Subject: Re: Request for feature: VACUUM FULL updates pg_stat_all_tables.last_vacuum