On Wed, Sep 7, 2011 at 1:55 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Pavel Stehule <pavel.steh...@gmail.com> writes: >> When we have a custom SUSET variable, like plpgsql.variable_conflikt, >> then setting this variable before plpgsql initalisation raises a >> exception, but it raise a exception when some plpgsql function is >> created. Try to execute a attached script - a set statement is ok, but >> CREATE FUNCTION fails. > > You can't set a custom SUSET variable in advance of loading the module, > because the system has no way to know it should enforce superuser > restrictions on setting it. For the most part, this is a good reason to > avoid custom SUSET variables.
Apparently we haven't taken that advice ourselves? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers