Thread: number of updated or deleted tuples needed to trigger a VACUUM in any one table



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?

I've Googled with no luck.

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

Re: number of updated or deleted tuples needed to trigger a VACUUM in any one table

From
Achilleas Mantzios - cloud
Date:


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!