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

Re: proposal: only superuser can change customized_options

From: "Pavel Stehule" <pavel(dot)stehule(at)hotmail(dot)com>
To: tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: proposal: only superuser can change customized_options
Date: 2007-02-02 16:53:26
Message-ID: BAY20-F144D4031A42084E4B8C260F99B0@phx.gbl (view raw or flat)
Thread:
Lists: pgsql-hackers


>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: [HACKERS] proposal: only superuser can change 
>customized_options Date: Fri, 02 Feb 2007 11:40:10 -0500
>
>"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

I am finding it.

Thank You

Pavel Stehule

_________________________________________________________________
Citite se osamele? Poznejte nekoho vyjmecneho diky Match.com. 
http://www.msn.cz/


In response to

Responses

pgsql-hackers by date

Next:From: Pavel StehuleDate: 2007-02-02 17:03:47
Subject: Re: PL/pgSQL RENAME functionality in TODOs
Previous:From: Andrew SullivanDate: 2007-02-02 16:46:38
Subject: Re: "May", "can", "might"

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