Re: proposal: only superuser can change customized_options

Поиск
Список
Период
Сортировка
От Pavel Stehule
Тема Re: proposal: only superuser can change customized_options
Дата
Msg-id BAY20-F144D4031A42084E4B8C260F99B0@phx.gbl
обсуждение исходный текст
Ответ на Re: proposal: only superuser can change customized_options  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: proposal: only superuser can change customized_options  (Andrew Dunstan <andrew@dunslane.net>)
Список pgsql-hackers


>From: Tom Lane <tgl@sss.pgh.pa.us>
>To: "Pavel Stehule" <pavel.stehule@hotmail.com>
>CC: pgsql-hackers@postgresql.org
>Subject: Re: [HACKERS] proposal: only superuser can change 
>customized_options Date: Fri, 02 Feb 2007 11:40:10 -0500
>
>"Pavel Stehule" <pavel.stehule@hotmail.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/



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Andrew Sullivan
Дата:
Сообщение: Re: "May", "can", "might"
Следующее
От: "Pavel Stehule"
Дата:
Сообщение: Re: PL/pgSQL RENAME functionality in TODOs