| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Greg Smith <greg(at)2ndQuadrant(dot)com> |
| Cc: | Amit Kapila <amit(dot)kapila(at)huawei(dot)com>, "'Andres Freund'" <andres(at)2ndquadrant(dot)com>, "'Boszormenyi Zoltan'" <zb(at)cybertec(dot)at>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Re: Proposal for Allow postgresql.conf values to be changed via SQL [review] |
| Date: | 2013-03-11 00:02:13 |
| Message-ID: | 513D1F05.40600@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 03/10/2013 11:12 PM, Greg Smith wrote:
>
> 5) An error message appears every time you reload configuration, if
> some part of the SET PERSISTENT mechanism isn't functional. This is
> going to be too much for some people. And it's confusing when it
> happens as part an interactive psql session. I have an example way
> down at the very end of this message.
An error when `SET PERSISTENT` is actually run seems sufficient to me if
the `config` dir is absent.
If the config dir or auto config file exist but are not included, that
probably deserves a warning during startup.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robins | 2013-03-11 01:52:13 | Increasing code-coverage of 'make check' |
| Previous Message | Erikjan Rijkers | 2013-03-10 22:51:57 | matview join view error |