On Wed, Sep 7, 2011 at 2:05 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Robert Haas <robertmh...@gmail.com> writes: >> On Wed, Sep 7, 2011 at 1:55 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: >>> 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? > > The ones in auto_explain and pg_stat_statements aren't too problematic > because those modules are designed to be preloaded by the postmaster. > We've avoided adding such variables in modules that aren't intended > to be used that way.
What about plpgsql.variable_conflict? -- 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
