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

From Laurenz Albe
Subject Re: Request for feature: VACUUM FULL updates pg_stat_all_tables.last_vacuum
Date
Msg-id d16beb9b163929894a35f2a9703bc29800b721f5.camel@cybertec.at
Whole thread Raw
In response to Request for feature: VACUUM FULL updates pg_stat_all_tables.last_vacuum  (Ron Johnson <ronljohnsonjr@gmail.com>)
Responses Re: Request for feature: VACUUM FULL updates pg_stat_all_tables.last_vacuum
List pgsql-admin
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.

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

Yours,
Laurenz Albe



pgsql-admin by date:

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