Re: Auto-tuning work_mem and maintenance_work_mem

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Auto-tuning work_mem and maintenance_work_mem
Date: 2013-10-11 20:23:07
Message-ID: 52585E2B.7010206@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 10/11/2013 01:11 PM, Bruce Momjian wrote:
> In summary, I think we need to:
>
> * decide on new defaults for work_mem and maintenance_work_mem
> * add an initdb flag to allow users/packagers to set shared_bufffers?
> * add an autovacuum_work_mem setting?
> * change the default for temp_buffers?

If we're changing defaults, bgwriter_lru_maxpages and vacuum_cost_limit
could also use a bump; those thresholds were set for servers with < 1GB
of RAM.

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2013-10-11 20:58:50 Re: [SQL] Comparison semantics of CHAR data type
Previous Message Andres Freund 2013-10-11 20:12:58 Re: drop-index-concurrently-1 on master fails at serializable