On Fri, Nov 23, 2012 at 4:56 AM, Amit Kapila <amit(dot)kapila(at)huawei(dot)com> wrote:
> On Thursday, November 22, 2012 10:09 PM Fujii Masao wrote:
>> Is it helpful to output the notice message like 'Run pg_reload_conf() or
>> restart the server if you want new settings to take effect' always after
>> SET PERSISTENT command?
> Not sure because if someone uses SET PERSISTENT command, he should know the
> effect or behavior of same.
> I think it's good to put this in UM along with "PERSISTENT" option
can we at least send the source file in the error message when a
parameter has a wrong value?
suppose you do: SET PERSISTENT shared_preload_libraries TO
when you restart postgres and that lib doesn't exist you can get
confused when looking at postgresql.conf and find an empty string
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
Phone: +593 4 5107566 Cell: +593 987171157
In response to
pgsql-hackers by date
|Next:||From: Noah Misch||Date: 2012-12-10 23:57:23|
|Subject: Re: Commits 8de72b and 5457a1 (COPY FREEZE)|
|Previous:||From: Tom Lane||Date: 2012-12-10 23:54:26|
|Subject: Re: Failing SSL connection due to weird interaction with openssl|