| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | decibel <decibel(at)decibel(dot)org>, Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Testing plperl<->plperlu interaction |
| Date: | 2010-01-07 00:07:12 |
| Message-ID: | 4B4525B0.7090106@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera wrote:
> decibel wrote:
>
>
>> We've actually run into similar issues. Alvaro came up with a patch
>> that fixes our specific issue, but I think he said there were some
>> other cases that needed to be fixed as well. Anyone looking to fix
>> this should ping Alvaro first.
>>
>
> No, what I fixed was the contrib/xml2 crasher that I still haven't
> submitted here (sorry). The plperl fix came from Alexey Klyukin, and
> AFAIK the fix is in 8.4.2.
>
Yes.
[thinks]
Could we have a regression test for it with an alternative result file
for the case where plperl and plperlu are not allowed to run together?
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Bailey | 2010-01-07 00:32:41 | Re: xpath improvement suggestion |
| Previous Message | Alvaro Herrera | 2010-01-07 00:00:04 | Re: Testing plperl<->plperlu interaction |