Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> 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?

How would we decide which wins in the third case? "first in" seems rather arbitrary. If we went that way I'd probably plump for just plperlu to be allowed. The the worst effect would be that the functions would have to be created by the superuser. It would be a great pity, of course - this threatens to do horrible things to portability ;-(

I guess another possibility would be to allow 3 to be overridden by a switch to become 2.



---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

Reply via email to