Specifies the maximum amount of memory to be used by maintenance operations, such as VACUUM, CREATE INDEX, and ALTER TABLE ADD FOREIGN KEY. If this value is specified without units, it is taken as kilobytes. It defaults to 64 megabytes (
64MB). Since only one of these operations can be executed at a time by a database session, and an installation normally doesn't have many of them running concurrently, it's safe to set this value significantly larger than work_mem. Larger settings might improve performance for vacuuming and for restoring database dumps.
Note that when autovacuum runs, up to autovacuum_max_workers times this memory may be allocated, so be careful not to set the default value too high. It may be useful to control for this by separately setting autovacuum_work_mem.
- Re: Zedstore - compressed in-core columnar storage
- Re: Resume vacuum and autovacuum from interruption and cancellation
- Re: [Proposal] Global temporary tables
- Re: pg_stat_statements issue with parallel maintenance (Was Re: WAL usage calculation patch)
- Re: Connections dropping while using Postgres backend DB with Ejabberd