Tom Lane wrote:
> "David E. Wheeler" <david@kineticode.com> writes:
>
>> On Jan 27, 2010, at 3:33 PM, Tom Lane wrote:
>>
>>> I don't have to read any further than the place where it says "doesn't
>>> work if you call both plperl and plperlu" to realize that that's quite
>>> false. Maybe we have different definitions of what a software
>>> interaction is...
>>>
>
>
>> I think that dates from when plperl and plperlu couldn't co-exists, which was fixed a few months ago, n'est pas?
>>
>
> No, that was fixed years ago, at least if you have a modern Perl build
> that supports multiplicity at all.
>
>
To be strictly accurate, what we fixed years ago was that we used to run
plperl and plperlu in the same interpreter, and that caused all sorts of
information leaks, so we switched to running in two interpreters, which
in turn became a problem for perl builds that didn't define multiplicity.
The problem here is that NYTprof is apparently not multiplicity safe. I
guess the question is what would happen if you tried to load it with
both plperl and plperlu. In any case, it's a known and documented issue,
so it's not one I'd be terribly worried about.
cheers
andrew