public inbox for [email protected]
help / color / mirror / Atom feedFrom: DINESH NAIR <[email protected]>
To: Dimitrios Apostolou <[email protected]>
To: [email protected] <[email protected]>
Subject: Re: Why isn't my table auto-analyzed/vacuumed?
Date: Fri, 31 Oct 2025 06:38:54 +0000
Message-ID: <PN4P287MB4381BB1C21BCA7703327230A9CF8A@PN4P287MB4381.INDP287.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
Hi,
Since the autovacuum decides whether to vacuum or analyze a table based on thresholds .As the threshold to trigger autovacuum is high so it might not have been triggered .
vacuum_trigger_threshold =
autovacuum_vacuum_threshold + (autovacuum_vacuum_scale_factor × n_live_tup)
You may check below mentioned parameters:
autovacuum = on
autovacuum_vacuum_threshold = 50 # min number of row updates before vacuum
autovacuum_vacuum_scale_factor = 0.01 # vacuum triggers at 1%
autovacuum_naptime = X # time between autovacuum runs
Thanks & Regards
Dinesh Nair
________________________________
From: Dimitrios Apostolou <[email protected]>
Sent: Thursday, October 30, 2025 9:25 PM
To: [email protected] <[email protected]>
Subject: Why isn't my table auto-analyzed/vacuumed?
Caution: This email was sent from an external source. Please verify the sender’s identity before clicking links or opening attachments.
Hello list,
I have a table that is constantly growing, and it's not being
vacuumed/analyzed. I think my problem is rather common, but how to even
debug it if "nothing works"?
I've already set log_autovacuum_min_duration = 0 but the table is never
mentioned in my logs, grep'ing for "vacuum".
I have run ANALYZE manually once but nothing automatic.
Here is more info:
> SELECT * FROM pg_stat_user_tables WHERE relname =
'test_runs_summarized_per_function' \gx
-[ RECORD 1 ]-------+----------------------------------
relid | 780653
schemaname | public
relname | test_runs_summarized_per_function
seq_scan | 32
last_seq_scan | 2025-10-19 10:31:08.289922+00
seq_tup_read | 26484817584
idx_scan | 4554128
last_idx_scan | 2025-10-10 22:02:50.987532+00
idx_tup_fetch | 7418587674
n_tup_ins | 921064234
n_tup_upd | 0
n_tup_del | 0
n_tup_hot_upd | 0
n_tup_newpage_upd | 0
n_live_tup | 6484485348
n_dead_tup | 0
n_mod_since_analyze | 423101205
n_ins_since_vacuum | 921064234
last_vacuum |
last_autovacuum |
last_analyze | 2025-09-30 18:24:47.550543+00
last_autoanalyze |
vacuum_count | 0
autovacuum_count | 0
analyze_count | 1
autoanalyze_count | 0
> SELECT reltuples FROM pg_class WHERE relname =
'test_runs_summarized_per_function' \gx
-[ RECORD 1 ]-----------
reltuples | 6.061923e+09
> SELECT name,setting FROM pg_settings WHERE name ILIKE '%factor%' ;
name | setting
---------------------------------------+---------
autovacuum_analyze_scale_factor | 0.1
autovacuum_vacuum_insert_scale_factor | 0.2
autovacuum_vacuum_scale_factor | 0.2
recursive_worktable_factor | 10
How can I get more info from postgres on the autovacuum logic?
Thank you in advance,
Dimitris
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Why isn't my table auto-analyzed/vacuumed?
In-Reply-To: <PN4P287MB4381BB1C21BCA7703327230A9CF8A@PN4P287MB4381.INDP287.PROD.OUTLOOK.COM>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox