Skip site navigation (1) Skip section navigation (2)

Re: proposal: only superuser can change customized_options

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Pavel Stehule" <pavel(dot)stehule(at)hotmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: proposal: only superuser can change customized_options
Date: 2007-02-02 16:40:10
Message-ID: 6976.1170434410@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
"Pavel Stehule" <pavel(dot)stehule(at)hotmail(dot)com> writes:
> I want to use custmized option for security configuration one contrib 
> library. Currently customized options are usable only for default 
> configuration, because everybody can change it. It is substitution of global 
> variables.
> Decision if option is protected or not can be based on name of option.

I dislike making it depend on spelling.  There was discussion of this
problem before, and we had a much saner answer: when the module that
defines the variable gets loaded, discard any local setting if the
correct protection level of the variable is SUSET or higher.  See the
archives.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Andrew SullivanDate: 2007-02-02 16:46:38
Subject: Re: "May", "can", "might"
Previous:From: Tom LaneDate: 2007-02-02 16:37:13
Subject: Re: Function proposal to find the type of a datum

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group