ions) from pg_class where relname =
'some_table';
Mike
*From:*Adrian Klaver
*Sent:* Tuesday, December 3, 2024 11:57 AM
*To:* Tefft, Michael J ;
pgsql-general@lists.postgresql.org
*Subject:* Re: Autovacuum and visibility maps
On 12/3/24 08: 32, Tefft, Michael J wrote: > We
#autovacuum_vacuum_insert_threshold = 1000 # min number of row inserts
>
>
>
> So I thought we should be triggering by inserts.
>
>
>
> Mike
>
>
>
> *From:* Adrian Klaver
> *Sent:* Tuesday, December 3, 2024 11:57 AM
> *To:* Tefft, Michael J ;
: Adrian Klaver
Sent: Tuesday, December 3, 2024 11:57 AM
To: Tefft, Michael J ;
pgsql-general@lists.postgresql.org
Subject: Re: Autovacuum and visibility maps
On 12/3/24 08: 32, Tefft, Michael J wrote: > We have some batch queries that
had occasionally having degraded > runtimes: from 2
On Tue, Dec 3, 2024 at 11:57 AM Adrian Klaver
wrote:
[snip]
>
> I have to believe it is due to this:
>
>
> https://www.postgresql.org/docs/current/routine-vacuuming.html#VACUUM-FOR-SPACE-RECOVERY
>
> "If you have a table whose entire contents are deleted on a periodic
> basis, consider doing it w
On 12/3/24 08:32, Tefft, Michael J wrote:
We have some batch queries that had occasionally having degraded
runtimes: from 2 hours degrading to 16 hours, etc.
Comparing plans from good and bad runs, we saw that the good plans used
index-only scans on table “x”, while the bad plans used index sc
