> Well, Magnus' proposed implementation supposed that the existing values
> *have* been loaded into the current session. I agree that with some
> locking and yet more code you could implement it without that. But this
> still doesn't seem to offer any detectable benefit over value-per-file.
Well, value-per-file is ugly (imagine you've set 40 different variables
that way) but dodges a lot of complicated issues. And I suppose "ugly"
doesn't matter, because the whole idea of the auto-generated files is
that users aren't supposed to look at them anyway.
PostgreSQL Experts Inc.
In response to
pgsql-hackers by date
|Next:||From: Robert Haas||Date: 2012-11-07 20:15:07|
|Subject: Re: Proposal for Allow postgresql.conf values to be changed
|Previous:||From: Josh Berkus||Date: 2012-11-07 19:45:25|
|Subject: Re: RFC: Timing Events|