Re: Proposal for Allow postgresql.conf values to be changed via SQL [review] - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Proposal for Allow postgresql.conf values to be changed via SQL [review]
Date
Msg-id 005e01ce26b8$51036ce0$f30a46a0$@kapila@huawei.com
Whole thread Raw
In response to Re: Proposal for Allow postgresql.conf values to be changed via SQL [review]  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Proposal for Allow postgresql.conf values to be changed via SQL [review]  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List 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.




pgsql-hackers by date:

Previous
From: Greg Smith
Date:
Subject: Re: Proposal for Allow postgresql.conf values to be changed via SQL [review]
Next
From: Atri Sharma
Date:
Subject: Page replacement algorithm in buffer cache