Re: number of updated or deleted tuples needed to trigger a VACUUM in any one table - Mailing list pgsql-admin

From Achilleas Mantzios - cloud
Subject Re: number of updated or deleted tuples needed to trigger a VACUUM in any one table
Date
Msg-id 3745e187-bf8f-48f8-8311-8da66eaff1cc@cloud.gatewaynet.com
Whole thread Raw
In response to number of updated or deleted tuples needed to trigger a VACUUM in any one table  (Ron Johnson <ronljohnsonjr@gmail.com>)
List pgsql-admin


On 11/7/24 16:30, Ron Johnson wrote:


autovacuum_vacuum_threshold (integer

Specifies the minimum number of updated or deleted tuples needed to trigger a VACUUM in any one table.


Are the number of updated and deleted tuples since the last vacuum exposed anywhere, like n_ins_since_vacuum is exposed?

By /usr/local/src/postgresql-17.0/src/backend/postmaster/autovacuum.c:3026 :

               reltuples = classForm->reltuples;
               vactuples = tabentry->dead_tuples;
               instuples = tabentry->ins_since_vacuum;
               anltuples = tabentry->mod_since_analyze;

So, this number should be the pg_stat_all_tables.
n_dead_tup


I've Googled with no luck.

--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

pgsql-admin by date:

Previous
From: Ron Johnson
Date:
Subject: Re: Running rsync backups in pg15
Next
From: Achilleas Mantzios - cloud
Date:
Subject: Re: Hi Corruption in Postgres