Josh Berkus <j...@agliodbs.com> writes:
> On 07/08/2014 10:07 AM, Robert Haas wrote:
>> I haven't looked at the code in this area too carefully, but it seems
>> to me like the flow ought to be:
>>
>> 1. Read all of the config files and determine what the final value
>> present in each config file is.
AFAICS we only care about the final value, not the final-value-in-each-
config-file.
>> 2. *Then*, in a second pass, enforce requirements like "can't be
>> changed except at server start".
> +1
> This would also make conf.d much more useful; I wouldn't have to worry
> as much about overlapping config settings.
> Sounds like a 9.5 feature, though.
No, ALTER SYSTEM is there now and it needs to work right in its first
release. I will go fix this if nobody else does.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
