| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Amit Kapila <amit(dot)kapila(at)huawei(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal for Allow postgresql.conf values to be changed via SQL [review] |
| Date: | 2013-04-03 17:24:55 |
| Message-ID: | CA+Tgmoa+t2V7yUJLvkTc7a566bqDqSouz=HbEYAUd13wuV8Bug@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Apr 2, 2013 at 12:19 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> It's weird that SET LOCAL and SET SESSION actually *set* the value, and
> the second key word determines how long the setting will last. SET
> PERSISTENT doesn't actually set the value. I predict that this will be
> a new favorite help-it-doesn't-work FAQ.
I think this is another argument against this particular syntax. I
have always thought that something along the lines of ALTER SYSTEM
would be more appropriate. ALTER DATABASE .. SET and ALTER ROLE ..
SET don't change the value immediately either, and nobody gets
confused about that to my knowledge. But I can see where SET
PERSISTENT could cause that sort of confusion.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2013-04-03 17:27:57 | Re: c language functions |
| Previous Message | Heikki Linnakangas | 2013-04-03 17:09:15 | Re: Regex with > 32k different chars causes a backend crash |