Re: Auto-tuning work_mem and maintenance_work_mem

On 10/17/2013 10:33 AM, Jeff Janes wrote:

>     A lot. A whole lot, more than what most people have in production
>     with more than that. You are forgetting a very large segment of the
>     population who run... VMs.
>
>     Why don't we just have 3 default config files:
>
>     2GB memory
>     4GB memory
>     8GB memory
>
>
> But what would go in each of those files?  Once we agree on what would
> be in them, why not just have a continuous knob that does that same thing?

Because we should set defaults, not optimized parameters. Workloads vary 
and we can reasonably say this is what we want BY DEFAULT for something 
but we can not reasonably say, "this is what will suit your needs".

Once you get above 8GB of memory you are dealing with workloads that 
vary widely and will almost always need some kind of indvidual 
attention. However, 8GB and below, we can set reasonable defaults that 
allow a user to likely but possibly not worry about changing the conf.

Joshua D. Drake

-- 
Command Prompt, Inc. - http://www.commandprompt.com/  509-416-6579
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, Postgres-XC, @cmdpromptinc
For my dreams of your image that blossoms   a rose in the deeps of my heart. - W.B. Yeats