On 7/16/16 5:03 PM, Jeff Janes wrote: > If you really want to suppress this per-backend activity, you can > pre-emptively load the modules yourself with something like: > > plperl.on_init ='require Carp; require Carp::Heavy; require feature;' > > But, I don't see why that should be necessary. I'd like to just put > plperl into shared_preload_libraries and be done with it. > > Am I missing something here?
I don't think there is any particular reason for this. Changes can probably be made, but backward compatibility needs to be taken into account. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
