Horton

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

Amit Kapila <amit.kapila@huawei.com>

View thread View on postgr.es
From: Amit Kapila <amit.kapila@huawei.com>
To: "'Dimitri Fontaine'" <dimitri@2ndQuadrant.fr>, "'Andres Freund'" <andres@2ndquadrant.com>
Cc: "'Josh Berkus'" <josh@agliodbs.com>, "'Stephen Frost'" <sfrost@snowman.net>, "'Tom Lane'" <tgl@sss.pgh.pa.us>, "'Alvaro Herrera'" <alvherre@2ndquadrant.com>, "'Robert Haas'" <robertmhaas@gmail.com>, "'Fujii Masao'" <masao.fujii@gmail.com>, <pgsql-hackers@postgresql.org>
Date: 2013-08-02T05:58:47Z
Lists: pgsql-hackers 
On Friday, August 02, 2013 4:34 AM Dimitri Fontaine wrote:
> Andres Freund <andres@2ndquadrant.com> writes:
> > They would need a setting that disables ALTER (DATABASE|USER) ... SET
> > ... as well though. At least for some settings.
> >
> > I don't think enforcing things on that level makes much sense.
> 
> If only we could trigger some actions when a command is about to be
> executed, in a way that it's easy for the user to implement whatever
> policy he fancies…
> 
> Oh, maybe I should finish preparing those patches for Event Triggers to
> be fully usable in 9.4 then ;)

I think this can be one useful way to disable.

With Regards,
Amit Kapila.