| From: | Amit Kapila <amit(dot)kapila(at)huawei(dot)com> |
|---|---|
| To: | "'Andres Freund'" <andres(at)2ndquadrant(dot)com> |
| Cc: | "'Greg Stark'" <stark(at)mit(dot)edu>, "'Greg Smith'" <greg(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-13 13:08:12 |
| Message-ID: | 005601ce1feb$d2008c70$7601a550$@kapila@huawei.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wednesday, March 13, 2013 6:10 PM Andres Freund wrote:
> On 2013-03-12 10:46:53 +0530, Amit Kapila wrote:
> > Do you mean to say that because some variables can only be set after
> restart
> > can lead to
> > inconsistency, or is it because of asynchronous nature of
> pg_reload_conf()?
>
> As long as SET PERSISTENT cannot be executed inside a transaction - or
> only takes effect after its end - there doesn't seem to be any problem
> executing ProcessConfigFile() directly.
Do you mean to say we call directly ProcessConfigFile() at end of SET
PERSISTENT instead
Of pg_reload_conf() but in that case would it load the variables for other
backends?
With Regards,
Amit Kapila.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2013-03-13 13:09:18 | Re: Duplicate JSON Object Keys |
| Previous Message | Andrew Dunstan | 2013-03-13 13:02:25 | Re: Duplicate JSON Object Keys |