| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Dawid Kuroczko <qnex42(at)gmail(dot)com> |
| Cc: | josh(at)agliodbs(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Permanent settings |
| Date: | 2008-02-20 12:36:43 |
| Message-ID: | 20080220123643.GC7773@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dawid Kuroczko escribió:
> 1) changes that cannot be done to live server:
>
> SET PERMANENT shared_buffers = '1GB';
>
> Now, this is a setting that cannot be changed "live", but it should be
> changeable. And we need a command to query what's permanent
> and what's current.
IMO restart-only settings should not be changeable via the new SQL
command. It's just too messy to deal with that.
Also, this SQL command should reject being used in a transaction block
(BEGIN/COMMIT), because rolling it back seems fragile.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2008-02-20 12:47:16 | Re: failed assertion in toasting code |
| Previous Message | Dmitry Turin | 2008-02-20 12:28:53 | Re: distibuted transactions, SQL+XPath+XTree |