Horton
Menu

Re: Proposal for Allow postgresql.conf values to be changed via SQL

Josh Berkus <josh@agliodbs.com>

View thread
From: Josh Berkus <josh@agliodbs.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Robert Haas <robertmhaas@gmail.com>, Magnus Hagander <magnus@hagander.net>, Amit Kapila <amit.kapila@huawei.com>, Christopher Browne <cbbrowne@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2012-11-07T19:50:14Z
Lists: pgsql-hackers 
> 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.

-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com