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-21 16:17:49 |
Message-ID: | 9fed2b70-cc36-1239-d5b6-7a81afeafb82@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 8/21/23 09:09, Rihad wrote:
> On 8/21/23 20:00, Adrian Klaver wrote:
> Thanks for the detailed reply, no tables have custom settings.
>
> I need to make it clear once again that all autovac/analyze work as
> expected when n_live_tup matches reality, i.e. when analyze has been run
> on them since last reset.
>
> A way to fix this is to simply analyze the whole database. Before doing
> that, while n_live_tup starts from basically 0 and grows based on DB
> activity, these usual calculations of 10-20% table size for
> vacuum/analyze don't work. They don't trigger autovac for most tables,
> or do it much much later.
>
You still have not said or shown whether the other autovacuum settings
are the default values or not. Assuming they are, then the only other
explanation I can come up with is that there is a process or processes
that are creating long running open transactions that prevent autovacuum
from running on the affected tables.
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2023-08-21 16:23:06 | Re: Will PostgreSQL 16 supports native transparent data encryption ? |
Previous Message | Rihad | 2023-08-21 16:09:03 | Re: Why doesn't autovacuum/analyze run in due time after calling pg_stat_reset? |