| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila(at)huawei(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 12:39:41 |
| Message-ID: | 20130313123941.GA15233@alap2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
The reason its not executed directly is that it is normally called
during query execution and it wouldn't be nice changing stuff after half
of a query has been processed.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2013-03-13 12:45:24 | Re: Re: Proposal for Allow postgresql.conf values to be changed via SQL [review] |
| Previous Message | Robert Haas | 2013-03-13 12:34:44 | Re: Writable foreign tables: how to identify rows |