pg.ddx.io pgsql-committers@postgresql.org mailing list archivehelp / color / mirror / Atom feed
pgsql: Lower minimum maintenance_work_mem to 64kB 2+ messages / 1 participants [nested] [flat]
* pgsql: Lower minimum maintenance_work_mem to 64kB @ 2024-08-10 08:19 John Naylor <john.naylor@postgresql.org> 0 siblings, 0 replies; 2+ messages in thread From: John Naylor @ 2024-08-10 08:19 UTC (permalink / raw) To: pgsql-committers@lists.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 Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/bbf668d66fbf61d45f1c187b08a5f51537bfb7c7 Modified Files -------------- src/backend/postmaster/autovacuum.c | 6 +++--- src/backend/utils/misc/guc_tables.c | 7 ++++++- src/backend/utils/misc/postgresql.conf.sample | 4 ++-- 3 files changed, 11 insertions(+), 6 deletions(-) ^ permalink raw reply [nested|flat] 2+ messages in thread
* pgsql: Lower minimum maintenance_work_mem to 64kB @ 2024-08-10 08:19 John Naylor <john.naylor@postgresql.org> 0 siblings, 0 replies; 2+ messages in thread From: John Naylor @ 2024-08-10 08:19 UTC (permalink / raw) To: pgsql-committers@lists.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 Branch ------ REL_17_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/2eda3df9ad532a051976937cfc17d6c52bbdacd6 Modified Files -------------- src/backend/postmaster/autovacuum.c | 6 +++--- src/backend/utils/misc/guc_tables.c | 7 ++++++- src/backend/utils/misc/postgresql.conf.sample | 4 ++-- 3 files changed, 11 insertions(+), 6 deletions(-) ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2024-08-10 08:19 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2024-08-10 08:19 pgsql: Lower minimum maintenance_work_mem to 64kB John Naylor <john.naylor@postgresql.org> 2024-08-10 08:19 pgsql: Lower minimum maintenance_work_mem to 64kB John Naylor <john.naylor@postgresql.org>
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox