Horton

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

Greg Stark <stark@mit.edu>

View thread View on postgr.es
From: Greg Stark <stark@mit.edu>
To: Dimitri Fontaine <dimitri@2ndquadrant.fr>
Cc: Fujii Masao <masao.fujii@gmail.com>, Alvaro Herrera <alvherre@2ndquadrant.com>, Robert Haas <robertmhaas@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, Josh Berkus <josh@agliodbs.com>, Amit Kapila <amit.kapila@huawei.com>, pgsql-hackers@postgresql.org
Date: 2013-08-01T14:17:04Z
Lists: pgsql-hackers 
We don't need per guc locking. This is the whole objection Tom had about
this patch being more complex than it has to be.

-- 
greg
On 1 Aug 2013 14:55, "Dimitri Fontaine" <dimitri@2ndquadrant.fr> wrote:

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