Horton

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

Amit Kapila <amit.kapila@huawei.com>

View thread View on postgr.es
From: Amit Kapila <amit.kapila@huawei.com>
To: "'Alvaro Herrera'" <alvherre@2ndquadrant.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-22T04:47:10Z
Lists: pgsql-hackers 
On Friday, March 22, 2013 8:57 AM Alvaro Herrera wrote:
> 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.

Sorry, I don't get your point. 
Do you mean to say that you don't agree with me and want new syntax as
proposed by you to be implemented?

With Regards,
Amit Kapila.