| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: plperl loading files |
| Date: | 2016-07-20 02:44:00 |
| Message-ID: | ea154b4f-8ab5-60f2-34fe-5fe6b7635989@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2016-07-20 03:01:42 | Re: (re)start in our init scripts seems broken |
| Previous Message | Amit Kapila | 2016-07-20 02:43:05 | Re: Re: [COMMITTERS] pgsql: Avoid extra locks in GetSnapshotData if old_snapshot_threshold < |