Re: Testing plperl<->plperlu interaction

From: Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, 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 10:30:18
Message-ID: 20100107103018.GY2505@timac.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jan 06, 2010 at 07:07:12PM -0500, Andrew Dunstan wrote:
>
> 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?

Or perhaps put the tests that require multiplicity into a plperl_multi.sql
file and add logic to the GNUmakefile to add that file to REGRESS
if "perl -V:usemultiplicity" returns "usemultiplicity='define';"

Tim.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2010-01-07 10:38:24 Github mirror
Previous Message Magnus Hagander 2010-01-07 10:26:13 Re: Bug with PATHs having non-ASCII characters