Hi, There was no follow up to my message below so I'm raising it again.
I can see in src/backend/access/heap/vacuumlazy.c that compute_max_dead_tuples uses autovacuum_work_mem when it is given. > The "vacuuming indexes" documentation has: > > "If a table has any indexes, this will happen at least once per vacuum, > after the heap has been completely scanned. It may happen multiple times per > vacuum if maintenance_work_mem is insufficient to store the number of dead > tuples found." > > should be something like > (I've changed this slightly and removed maximum as it seems redundant) "If a table has any indexes, this will happen at least once per vacuum, after the heap has been completely scanned. It may happen multiple times per vacuum if the memory is insufficient to store the number of dead tuples found. The memory is set via the maintenance_work_mem unless it is an autovacuum then autovacuum_work_mem will be used."
publickey - nikolai.berkoff@pm.me - 0xD189792D.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
