Re: plperl/plperlu interaction - Mailing list pgsql-hackers

From Tom Lane
Subject Re: plperl/plperlu interaction
Date
Msg-id 25670.1161897877@sss.pgh.pa.us
Whole thread Raw
In response to Re: plperl/plperlu interaction  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: plperl/plperlu interaction  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> You can also examine the output from perl -V

I think we've already established that we won't be able to ignore the
case of not having support for multiple perl interpreters :-(

So it seems we have these choices:

1. Do nothing (document it as a feature not a bug)

2. Support separate interpreters if possible, do nothing if not  (still needs documentation)

3. Support separate interpreters if possible, refuse to run both plperl  and plperlu functions in the same backend if
not.

Any other compromises possible?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Deadlock with pg_dump?
Next
From: Tom Lane
Date:
Subject: Re: [PATCHES] GUC description cleanup