Re: Termination When Switching between PL/Perl and PL/PerlU - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Termination When Switching between PL/Perl and PL/PerlU
Date
Msg-id 15561.1263447421@sss.pgh.pa.us
Whole thread Raw
In response to Re: Termination When Switching between PL/Perl and PL/PerlU  (Craig Ringer <craig@postnewspapers.com.au>)
Responses Re: Termination When Switching between PL/Perl and PL/PerlU  (Tim Bunce <Tim.Bunce@pobox.com>)
List pgsql-bugs
Craig Ringer <craig@postnewspapers.com.au> writes:
> David E. Wheeler wrote:
>> Found in 8.4.2, replicated in HEAD. Steps:
>>
>> 1. Create PL/Perl function.
>> 2. Run it.
>> 3. Create same function with PL/PerlU
>> 4. Run it.
>> 5. Create same function again with PL/Perl
>> 6. Boom.

> This was just discussed in -HACKERS. Have a look at the archives.

No, this is something different, because it still crashes even with the
fix for that other issue.  I see this in the postmaster log:

panic: free from wrong pool.
LOG:  server process (PID 15697) exited with exit code 255

There's no core dump (thank you, perl).  The lower-case panic message
must be from libperl because PG has no such message.  I guess that we
probably need to fix this by changing the timing of interpreter
switching relative to throwing away the old compiled function ...

            regards, tom lane

pgsql-bugs by date:

Previous
From: Craig Ringer
Date:
Subject: Re: Termination When Switching between PL/Perl and PL/PerlU
Next
From: Pavel Stehule
Date:
Subject: Re: BUG #5274: [PL/PgSQL] EXECUTE ... USING variable expansion