Re: Why doesn't autovacuum/analyze run in due time after calling pg_stat_reset?

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Rihad <grihad(at)gmail(dot)com>, pgsql-general General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Why doesn't autovacuum/analyze run in due time after calling pg_stat_reset?
Date: 2023-08-20 16:22:52
Message-ID: 9440ab9c-4ee1-7668-5476-dc28e8086524@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 8/18/23 22:35, Rihad wrote:
> On 8/17/23 13:01, rihad wrote:
>>
>> Hi, all. After calling pg_stat_reset all statistics used by autovacuum
>> got zeroed, and started accumulating from scratch. Some tables get
>> acted upon properly, some don't.
>>
>>
> Self-replying: yup, it seems there's an arbitrary limit of 100K of
> n_live_tup after which autovac/analyze kicks in, or it seems so.

To know rather then guess read:

https://www.postgresql.org/docs/current/routine-vacuuming.html#AUTOVACUUM

>
> There are still many tables waiting for their turn, which is long due.
>
> Although there are some tables having only 60-70 (not 60-70K) n_live_tup
> that have had autovacuum run on them. Weird.
>
>
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Rihad 2023-08-20 19:10:33 Re: Why doesn't autovacuum/analyze run in due time after calling pg_stat_reset?
Previous Message Amn Ojee Uw 2023-08-20 14:00:41 JDBC + PG-15 but not psql