Michael Fuhr <mike(at)fuhr(dot)org> writes:
> Hmmm...even if the "plperl" custom variable class isn't defined in
> postgresql.conf, plperl.use_strict springs into existence when the
> interpreter is initialized:
Yes, this is per spec. The "custom class" concept is only intended
to allow you to put things into postgresql.conf before the associated
shared library is loaded; it is not intended to stop the shared library
from defining GUC variables that you didn't see fit to put values into
postgresql.conf for.
regards, tom lane