From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Geoghegan <pg(at)heroku(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Josh Berkus <josh(at)agliodbs(dot)com> |
Subject: | Re: Auto-tuning work_mem and maintenance_work_mem |
Date: | 2013-10-10 14:59:58 |
Message-ID: | 20131010145958.GM7092@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Oct 10, 2013 at 07:24:26AM -0700, Kevin Grittner wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
> > I actually had the thought that it might be something we'd integrate
> > *into* initdb. So you'd do initdb --system-memory 8GB or something
> > like that and it would do the rest. That'd be slick, at least IMHO.
>
> How would you handle the case that the machine (whether physical or
> a VM) later gets more RAM? That's certainly not unheard of with
> physical servers, and with VMs I'm not sure that the database
> server would necessarily go through a stop/start cycle for it.
Yes, going from a non-dedicated to a dedicated database server, adding
RAM, or moving the cluster to another server could all require an initdb
to change auto-tuned values. This is why I think we will need to
auto-tune in the backend, rather than via initdb. I do think an
available_mem parameter for initdb would help though, to be set in
postgresql.conf.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2013-10-10 15:18:46 | Re: Auto-tuning work_mem and maintenance_work_mem |
Previous Message | Dimitri Fontaine | 2013-10-10 14:52:19 | Re: Auto-tuning work_mem and maintenance_work_mem |