Horton

Re: Proposal for Allow postgresql.conf values to be changed via SQL [review]

Alvaro Herrera <alvherre@2ndquadrant.com>

View thread View on postgr.es
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Amit Kapila <amit.kapila@huawei.com>
Cc: 'Greg Smith' <greg@2ndQuadrant.com>, 'Robert Haas' <robertmhaas@gmail.com>, 'Greg Stark' <stark@mit.edu>, 'Andres Freund' <andres@2ndquadrant.com>, 'Boszormenyi Zoltan' <zb@cybertec.at>, pgsql-hackers@postgresql.org
Date: 2013-03-22T03:27:23Z
Lists: pgsql-hackers 
Amit Kapila escribió:
> On Friday, March 22, 2013 12:48 AM Alvaro Herrera wrote:

> > Maybe add some syntax to prevent the SIGHUP for the rare case where
> > that
> > is wanted, say
> > 
> > SET PERSISTENT (reload=off) var=val;
> > 
> > (perhaps WITH at the end, dunno)
> 
> I think adding new syntax change is little scary for me, not for the matter
> of implementation but for building consensus on syntax.

I cannot but agree on that point.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services