Loading feed…
Planet PostgreSQL0 Hot0 comments6 min read
All Your GUCs in a Row: maintenance_work_mem
maintenance_work_mem is explained as PostgreSQL's genuine one-allocation-per-operation memory ceiling, unlike the multiplying work_mem. It covers what actually consumes this budget in source code (vacuum's dead-TID store, index builds, CLUSTER sorts, foreign-key validation, pgvector's HNSW graph build), where the ceiling holds (parallel CREATE INDEX splits one budget across workers) versus breaks (autovacuum gives every worker its own copy, pg_restore -j multiplies per job), and what raising it actually buys: little for serial B-tree sorts, but decisive gains for memory-bound structures like HNSW graphs and foreign-key hash joins. Ends with concrete tuning advice: set the global modestly (256MB-1GB), set autovacuum_work_mem explicitly, and raise maintenance_work_mem per-session for big builds or restores.
Source: https://postgr.es/p/9u9. 8 Sync News only summarizes and links out; content copyright belongs to the authors and original sources.
Recommended for you
Bình luận
Đang tải bình luận…
