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 CANzqJaBzVjiMBTQduOP+S5bOhJSarxqR12Nf=9W1uqsoBvebLQ@mail.gmail.com
Whole thread Raw
In response to Re: Request for feature: VACUUM FULL updates pg_stat_all_tables.last_vacuum  (Laurenz Albe <laurenz.albe@cybertec.at>)
Responses Re: Request for feature: VACUUM FULL updates pg_stat_all_tables.last_vacuum
Re: Request for feature: VACUUM FULL updates pg_stat_all_tables.last_vacuum
List pgsql-admin
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.
 
Then drop it in PG 27...

Perhaps you could write a patch to add a column "last_rewritten"
to "pg_stat_all_tables"...

I'm a worse C programmer than I am a DBA. 
 

pgsql-admin by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: Request for feature: VACUUM FULL updates pg_stat_all_tables.last_vacuum
Next
From: Rui DeSousa
Date:
Subject: Re: Request for feature: VACUUM FULL updates pg_stat_all_tables.last_vacuum