Re: Auto-tuning work_mem and maintenance_work_mem

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Kevin Grittner <kgrittn(at)ymail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Bruce Momjian <bruce(at)momjian(dot)us>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Auto-tuning work_mem and maintenance_work_mem
Date: 2013-10-17 17:03:13
Message-ID: 52601851.4010909@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 10/17/2013 09:49 AM, Robert Haas 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.
>
> That's true, but are you actually arguing for keeping work_mem at 1MB?
>
> Even on a VM with only 1GB of RAM, work_mem=4MB is not going to cause
> any problems unless you're also trying to service a large number of
> simultaneous connections. And if you're doing that, you probably need
> to rethink something anyway.

No. I am arguing for the multiple config file option.

JD

--
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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2013-10-17 17:10:09 Re: [PATCH] pg_sleep(interval)
Previous Message Robert Haas 2013-10-17 17:01:36 Re: [PATCH] pg_sleep(interval)