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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
