Re: dynamic shared memory: wherein I am punished for good intentions - Mailing list pgsql-hackers

From Robert Haas
Subject Re: dynamic shared memory: wherein I am punished for good intentions
Date
Msg-id CA+TgmoZBSt-8cDAQpT5tV6d9jfEW=VTOomvX+iHFLE2UFpwx8w@mail.gmail.com
Whole thread Raw
In response to Re: dynamic shared memory: wherein I am punished for good intentions  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: dynamic shared memory: wherein I am punished for good intentions  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
On Thu, Oct 10, 2013 at 2:21 PM, Andrew Dunstan <andrew@dunslane.net> wrote:
>> Other votes?  Other ideas?
>
> 5) test and set it in initdb.

Are you advocating for that option, or just calling out that it's
possible?  I'd say that's closely related to option #3, except at
initdb time rather than run-time - and it might be preferable to #3
for some of the same reasons discussed on the thread about tuning
work_mem, namely, that having it change from one postmaster lifetime
to the next might lead to user astonishment.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Auto-tuning work_mem and maintenance_work_mem
Next
From: Peter Geoghegan
Date:
Subject: Re: dynamic shared memory: wherein I am punished for good intentions