Обсуждение: Autovacuum not running properly
-- Find current setting (this is at database level)
select * from pg_settings where name in ('autovacuum','autovacuum_analyze_scale_factor','autovacuum_analyze_threshold','autovacuum_vacuum_scale_factor');
select current_setting('autovacuum_vacuum_scale_factor') as "analyze_scale_factor",current_setting('autovacuum_vacuum_threshold') as "vacuum_threshold";
select current_setting('autovacuum_analyze_scale_factor') as "analyze_scale_factor", current_setting('autovacuum_analyze_threshold') as "analyze_threshold";
-- Note: The smaller number = more aggressive = vacuum more frequence
-- Current:
-- autovacuum_analyze_scale_factor = 0.05
-- autovacuum_vacuum_scale_factor = 0.1
-- Fine Tune at table level = ALTER TABLE mytable SET (autovacuum_analyze_scale_factor = 0.02);
ALTER TABLE your_schema.your_table SET (autovacuum_enabled = true,autovacuum_analyze_scale_factor = 0.002,autovacuum_vacuum_scale_factor = 0.001);
-- Put it back to use global setting
ALTER TABLE your_schema.your_table RESET (autovacuum_enabled,autovacuum_analyze_scale_factor,autovacuum_vacuum_scale_factor);
From: Rajesh Kumar <rajeshkumar.dba09@gmail.com>
Sent: Sunday, August 27, 2023 4:09 AM
To: pgsql-admin@lists.postgresql.org
Subject: [EXTERNAL] Autovacuum not running properly
Hi
Why Autovacuum is not running on specific tables while it works on other tables and how to resolve this.
And for some tables the last autovacuum done is 2days ago whereas most are till today.
How to analyze autovacuum and take action?
-- Find current setting (this is at database level)
select * from pg_settings where name in ('autovacuum','autovacuum_analyze_scale_factor','autovacuum_analyze_threshold','autovacuum_vacuum_scale_factor');
select current_setting('autovacuum_vacuum_scale_factor') as "analyze_scale_factor",current_setting('autovacuum_vacuum_threshold') as "vacuum_threshold";
select current_setting('autovacuum_analyze_scale_factor') as "analyze_scale_factor", current_setting('autovacuum_analyze_threshold') as "analyze_threshold";
-- Note: The smaller number = more aggressive = vacuum more frequence
-- Current:
-- autovacuum_analyze_scale_factor = 0.05
-- autovacuum_vacuum_scale_factor = 0.1
-- Fine Tune at table level = ALTER TABLE mytable SET (autovacuum_analyze_scale_factor = 0.02);
ALTER TABLE your_schema.your_table SET (autovacuum_enabled = true,autovacuum_analyze_scale_factor = 0.002,autovacuum_vacuum_scale_factor = 0.001);
-- Put it back to use global setting
ALTER TABLE your_schema.your_table RESET (autovacuum_enabled,autovacuum_analyze_scale_factor,autovacuum_vacuum_scale_factor);
From: Rajesh Kumar <rajeshkumar.dba09@gmail.com>
Sent: Sunday, August 27, 2023 4:09 AM
To: pgsql-admin@lists.postgresql.org
Subject: [EXTERNAL] Autovacuum not running properly
Hi
Why Autovacuum is not running on specific tables while it works on other tables and how to resolve this.
And for some tables the last autovacuum done is 2days ago whereas most are till today.
How to analyze autovacuum and take action?
On Sun, Aug 27, 2023 at 2:16 PM Rajesh Kumar <rajeshkumar.dba09@gmail.com> wrote: > > Hi > > Why Autovacuum is not running on specific tables while it works on other tables and how to resolve this. > > And for some tables the last autovacuum done is 2days ago whereas most are till today. I bet such tables do not require autovacuum attention, that is their overall activity is under the thresholds. Luca
On Fri, Sep 1, 2023 at 6:32 PM Rajesh Kumar <rajeshkumar.dba09@gmail.com> wrote: > > In that case how to be sure of autovacuum is not necessary for this table? On what basis? Do we have any calculation The idea should be the number of "manipulated tuples" exceed the thresholds. For example, in the case of insert workload, something like: SELECT current_setting( 'autovacuum_vacuum_insert_threshold' )::numeric + current_setting( 'autovacuum_vacuum_insert_scale_factor' )::numeric * reltuples FROM pg_class WHERE relname = <your relation> and relkind = 'r'; will give you the amount of tuples that, once inserted, will trigger an autovacuum. Therefore, unless your table receive more tuples than the above, autovacuum will not consider vacuuming the table (thn there's autoanalyze, that is another story but the reasoning is similar). Long story short: if your table is pretty much static, than it is clear that autovacuum is not goint to vacuum over an over the same data. Luca
On Fri, Sep 1, 2023 at 6:32 PM Rajesh Kumar <rajeshkumar.dba09@gmail.com> wrote:
>
> In that case how to be sure of autovacuum is not necessary for this table? On what basis? Do we have any calculation
The idea should be the number of "manipulated tuples" exceed the
thresholds. For example, in the case of insert workload, something
like:
SELECT current_setting( 'autovacuum_vacuum_insert_threshold' )::numeric
+ current_setting( 'autovacuum_vacuum_insert_scale_factor' )::numeric
* reltuples
FROM pg_class
WHERE relname = <your relation> and relkind = 'r';
will give you the amount of tuples that, once inserted, will trigger
an autovacuum. Therefore, unless your table receive more tuples than
the above, autovacuum will not consider vacuuming the table (thn
there's autoanalyze, that is another story but the reasoning is
similar).
Long story short: if your table is pretty much static, than it is
clear that autovacuum is not goint to vacuum over an over the same
data.
Luca
On Mon, Sep 4, 2023 at 1:44 PM Rajesh Kumar <rajeshkumar.dba09@gmail.com> wrote: > > The result I get "amount of tuples inserted" is not very clear. Let's say I get 10000 which is 10k , in this case, do youmean autovacuum will trigger for every 10k (inserts+updates+deletes) ? Assuming you are referring to the value autovacuum_vacuum_insert_threshold + autovacuum_vacuum_insert_scale_factor * reltuples = 10k, then it means that under 10k inserts, your table will not be vacuumed. With thed default configuration, essentially you get vacuum running every time you insert at least 20% of new tuples, and the same is for delete and updates. Please see <https://www.postgresql.org/docs/15/runtime-config-autovacuum.html>. Luca