Lower minimum maintenance_work_mem to 64kB
John Naylor <john.naylor@postgresql.org>
Lower minimum maintenance_work_mem to 64kB Since the introduction of TID store, vacuum uses far less memory in the common case than in versions 16 and earlier. Invoking multiple rounds of index vacuuming in turn requires a much larger table. It'd be a good idea anyway to cover this case in regression testing, and a lower limit is less painful for slow buildfarm animals. The reason to do it now is to re-enable coverage of the bugfix in commit 83c39a1f7f. For consistency, give autovacuum_work_mem the same treatment. Suggested by Andres Freund Tested by Melanie Plageman Backpatch to v17, where TID store was introduced Discussion: https://postgr.es/m/20240516205458.ohvlzis5b5tvejru@awork3.anarazel.de Discussion: https://postgr.es/m/20240722164745.fvaoh6g6zprisqgp%40awork3.anarazel.de
Files
| Path | Change | +/− |
|---|---|---|
| src/backend/postmaster/autovacuum.c | modified | +3 −3 |
| src/backend/utils/misc/guc_tables.c | modified | +6 −1 |
| src/backend/utils/misc/postgresql.conf.sample | modified | +2 −2 |
Discussion
- Vacuum ERRORs out considering freezing dead tuples from before OldestXmin 92 messages · 2024-06-20 → 2025-06-24
- Lowering the minimum value for maintenance_work_mem 3 messages · 2024-05-16 → 2024-05-20