Horton

Re: Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])

Dimitri Fontaine <dimitri@2ndquadrant.fr>

View thread View on postgr.es
From: Dimitri Fontaine <dimitri@2ndQuadrant.fr>
To: Greg Stark <stark@mit.edu>
Cc: Josh Berkus <josh@agliodbs.com>, Alvaro Herrera <alvherre@2ndquadrant.com>, Amit Kapila <amit.kapila@huawei.com>, Tom Lane <tgl@sss.pgh.pa.us>, Robert Haas <robertmhaas@gmail.com>, Fujii Masao <masao.fujii@gmail.com>, pgsql-hackers@postgresql.org
Date: 2013-08-01T13:55:25Z
Lists: pgsql-hackers 
Greg Stark <stark@mit.edu> writes:
> I think people are going to laugh at us if an open source database
> software can't manage a simple flat file database of settings,
> especially one that is purely write-only and can be a simple dump of
> settings that are set by alter system.

So you say it's easier to implement per-GUC locking semantics correctly
when using a single file with multiple units of information that all are
of the same type? Interesting.

Maybe the storage should actually be a shared catalog, in fact.

Regards,
-- 
Dimitri Fontaine
http://2ndQuadrant.fr     PostgreSQL : Expertise, Formation et Support