| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Dawid Kuroczko <qnex42(at)gmail(dot)com>, josh(at)agliodbs(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Permanent settings |
| Date: | 2008-02-20 13:20:55 |
| Message-ID: | 20080220132055.GD7773@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Magnus Hagander escribió:
> On Wed, Feb 20, 2008 at 09:36:43AM -0300, Alvaro Herrera wrote:
> > IMO restart-only settings should not be changeable via the new SQL
> > command. It's just too messy to deal with that.
>
> I respectfully disagree. It should be settable. You need a restart, sure,
> and the GUI app should tell you that. But you shuld be able to change them.
> (for example, pgadmin can restart the server just fine for you if you're on
> Windows)
What if the server doesn't come back up? Say, because you increased
shared_buffers and now it doesn't fit on the kernel limits. If you
haven't made arrangements to be able to edit the postgresql.conf file
beforehand, you're hosed.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2008-02-20 13:23:11 | Re: More char()/ascii() |
| Previous Message | Sergey E. Koposov | 2008-02-20 13:05:47 | Re: failed assertion in toasting code |