Re: [HACKERS] proposal: only superuser can change customized_options
Pavel Stehule wrote: From: Tom Lane <[EMAIL PROTECTED]> To: "Pavel Stehule" <[EMAIL PROTECTED]> 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" <[EMAIL PROTECTED]> 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. Pavel, Is there any chance you can work on this? I suspect I won't have time. You can see the original thread here: http://groups.google.com/group/pgsql.hackers/browse_thread/thread/3b7d67e56b83f327/baf344e221116f6e?lnk=gst&q=custom+variable+classes&rnum=1#baf344e221116f6e cheers andrew ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [HACKERS] proposal: only superuser can change customized_options
From: Tom Lane <[EMAIL PROTECTED]> To: "Pavel Stehule" <[EMAIL PROTECTED]> 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" <[EMAIL PROTECTED]> 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/ ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [HACKERS] proposal: only superuser can change customized_options
"Pavel Stehule" <[EMAIL PROTECTED]> 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 ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
