Re: BUG #5323: plperl and plperlu interaction segfaults - Mailing list pgsql-bugs

From Robert Haas
Subject Re: BUG #5323: plperl and plperlu interaction segfaults
Date
Msg-id 603c8f071002111202o391087fen53b9ed2a500029d9@mail.gmail.com
Whole thread Raw
In response to BUG #5323: plperl and plperlu interaction segfaults  ("Dave Olszewski" <cxreg@pobox.com>)
Responses Re: BUG #5323: plperl and plperlu interaction segfaults  (Alexey Klyukin <alexk@commandprompt.com>)
List pgsql-bugs
On Thu, Feb 11, 2010 at 1:44 PM, Dave Olszewski <cxreg@pobox.com> wrote:
>
> The following bug has been logged online:
>
> Bug reference: =A0 =A0 =A05323
> Logged by: =A0 =A0 =A0 =A0 =A0Dave Olszewski
> Email address: =A0 =A0 =A0cxreg@pobox.com
> PostgreSQL version: 8.3.9
> Operating system: =A0 Linux
> Description: =A0 =A0 =A0 =A0plperl and plperlu interaction segfaults
> Details:
>
> Creating the following functions reliably segfaults Postgres for me:
>
> CREATE LANGUAGE 'plperl';
> CREATE LANGUAGE 'plperlu';
> CREATE OR REPLACE FUNCTION test_one() RETURNS TRIGGER AS $$ $$ language
> 'plperlu';
> CREATE OR REPLACE FUNCTION test_two() RETURNS TRIGGER AS $$ $$ language
> 'plperl';
> CREATE OR REPLACE FUNCTION test_two() RETURNS TRIGGER AS $$ $$ language
> 'plperl';
>
> A possibly interesting note is that if I create "two, one, two two" it wi=
ll
> not crash, but just 'one, two two" will.

I think this might be the same problem previously discussed here:

http://archives.postgresql.org/pgsql-bugs/2010-01/msg00224.php

Does that patch fix it?

...Robert

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #5314: Error in nested composite types in plpgsql.
Next
From: Alexey Klyukin
Date:
Subject: Re: BUG #5323: plperl and plperlu interaction segfaults