Andrew Dunstan <[email protected]> writes:
> Tom Lane wrote:
>> As an example, if people were using such functionality then the DBA
>> couldn't start preloading plperl for performance without breaking
>> behavior that some of his users might be depending on.
> If we made plperl.on_perl_init PGC_POSTMASTER and the other two
> PGC_SUSET would that alloy your concerns?
No, they have to all be PGC_POSTMASTER to answer that concern. Only
breaking things for superusers isn't really that big an improvement
over breaking them for everybody.
regards, tom lane
--
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
