| From: | Amit Kapila <amit(dot)kapila(at)huawei(dot)com> |
|---|---|
| To: | "'Alvaro Herrera'" <alvherre(at)2ndquadrant(dot)com> |
| Cc: | "'Greg Smith'" <greg(at)2ndQuadrant(dot)com>, "'Robert Haas'" <robertmhaas(at)gmail(dot)com>, "'Greg Stark'" <stark(at)mit(dot)edu>, "'Andres Freund'" <andres(at)2ndquadrant(dot)com>, "'Boszormenyi Zoltan'" <zb(at)cybertec(dot)at>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal for Allow postgresql.conf values to be changed via SQL [review] |
| Date: | 2013-03-22 04:47:10 |
| Message-ID: | 005e01ce26b8$51036ce0$f30a46a0$@kapila@huawei.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Atri Sharma | 2013-03-22 04:51:59 | Page replacement algorithm in buffer cache |
| Previous Message | Greg Smith | 2013-03-22 04:43:28 | Re: Proposal for Allow postgresql.conf values to be changed via SQL [review] |