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>
From: Dimitri Fontaine <dimitri@2ndQuadrant.fr>
To: Stephen Frost <sfrost@snowman.net>
Cc: Andres Freund <andres@2ndquadrant.com>,
Robert Haas <robertmhaas@gmail.com>,
Tom Lane <tgl@sss.pgh.pa.us>, Bruce Momjian <bruce@momjian.us>,
Amit Kapila <amit.kapila16@gmail.com>,
Martijn van Oosterhout <kleptog@svana.org>,
Alvaro Herrera <alvherre@2ndquadrant.com>, Josh Berkus <josh@agliodbs.com>,
Fujii Masao <masao.fujii@gmail.com>,
"pgsql-hackers\@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2013-08-30T10:43:14Z
Lists: pgsql-hackers
Stephen Frost <sfrost@snowman.net> writes: > The OPs people are the ones that will be upset with this because the DBAs > will be modifying configs which OPs rightfully claim as theirs. If that's the problem you want to solve, there's no technical solution that will put you at ease. That's a people and trust problem. I don't think typical (or less typical) organisation should drive our technical choices too much, and I'm pretty confident they didn't in the past: pg_hba.conf is a file not because it's meant for this or that team but because it makes sense technically to manage the settings to allow using some resources *outside* of said resources. We currently have no way that I know of to disable ALTER ROLE SET and ALTER DATABASE SET effects, why do we need to provide that feature for ALTER SYSTEM SET so much? Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support