hard20 pts · first answer countspostgresqlperformancedebugging

Table bloat that VACUUM will not fix

A PostgreSQL table keeps growing and queries get slower. Autovacuum runs often, but the number of dead rows does not go down. What is the most likely cause?

A.Autovacuum is turned off by default and must be enabledB.The table has too many indexes, so autovacuum gives up before finishing each run and leaves dead rows behindC.The table has no primary keyD.An old open transaction (e.g. "idle in transaction") or replication slot holds back cleanup

← Sharding orders by creation date Stale value returns after cache delete →