On Mar 2, 2010, at 6:00 PM, Andrew Dunstan wrote:
>> Perhaps add a note that some other interface to allow preloaded modules to
>> also be available to plperl may be provided in the future.
>
> No, that's far from a done deal.
Hence the “may.” But either way.
David
--
Sent via pgsql-hacker
David E. Wheeler wrote:
On Mar 2, 2010, at 4:33 PM, Andrew Dunstan wrote:
I propose to add the following note to the docs:
Preloading modules using plperl.on_init does not make them available
for use by plperl. External perl modules can only be used in plperlu.
Perhaps add a no
On Mar 2, 2010, at 4:33 PM, Andrew Dunstan wrote:
> I propose to add the following note to the docs:
>
> Preloading modules using plperl.on_init does not make them available
> for use by plperl. External perl modules can only be used in plperlu.
Perhaps add a note that some other interface t
There appears to be some significant misunderstanding of what can be
done effectively using the various *_init settings for plperl.
In particular, some people have got an expectation that modules loaded
in plperl.on_init will thereby be available for use in trusted plperl.
I propose to add
