Re: Unfortunate Nested Loop + Missing Autovacuum
Andrei Lepikhov <lepihov@gmail.com>
From: Andrei Lepikhov <lepihov@gmail.com>
To: Lincoln Swaine-Moore <lswainemoore@gmail.com>,
pgsql-performance@lists.postgresql.org
Date: 2025-02-22T08:37:40Z
Lists: pgsql-performance
On 22/2/2025 00:46, Lincoln Swaine-Moore wrote: > So, obviously there's a statistics problem, which led me to realize that > actually these tables have *never* been autovacuumed/analyzed according > to pg_stat_user_tables. > I'm using a managed database which makes it a little tricky to debug, > but all my settings > (autovacuum/autovacuum_vacuum_threshold/autovacuum_analyze_threshold/ > autovacuum_vacuum_insert_threshold) are default, > and I can see that other tables have been vacuumed recently. I know a couple of reports related to this kind of behaviour and different solutions to resolve it. But first, if you execute the ANALYZE command on these problematic tables, does it fix your issue? May you live with manual vacuum analysis each time after batch insertion? If not, may you provide a synthetic reproduction of the case? -- regards, Andrei Lepikhov