| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila(at)huawei(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 03:27:23 |
| Message-ID: | 20130322032723.GF3685@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Smith | 2013-03-22 04:43:28 | Re: Proposal for Allow postgresql.conf values to be changed via SQL [review] |
| Previous Message | Amit Kapila | 2013-03-22 02:39:20 | Re: Proposal for Allow postgresql.conf values to be changed via SQL [review] |