On Wed, Oct 9, 2013 at 10:21 PM, Magnus Hagander <mag...@hagander.net> wrote: >> Well, the Postgres defaults won't really change, because the default >> vacuum_work_mem will be -1, which will have vacuum defer to >> maintenance_work_mem. Under this scheme, vacuum only *prefers* to get >> bound working memory size from vacuum_work_mem. If you don't like >> vacuum_work_mem, you can just ignore it.
> While unrelated to the main topic of this thread, I think this is very > important as well. I often have to advice people to remember to cap > their maintenance_work_mem because of autovacuum, and to remember to > re-tune maintenance_wokr_mem when they change the number of autovacuum > workers. I'll code that up at some point, then. -- Peter Geoghegan -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
