Re: BUG #7516: PL/Perl crash

From: Marko Tiikkaja <pgmail(at)joh(dot)to>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #7516: PL/Perl crash
Date: 2012-09-05 20:48:28
Message-ID: 5047BA9C.2040405@joh.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

On 03/09/2012 18:06, Tom Lane wrote:
> pgmail(at)joh(dot)to writes:
>> We had a segmentation fault in PostgreSQL 9.1.5 with PL/PerlU.
>> ...
>> It seems to have happened when a PL/PerlU executed a prepared statement
>> which calls another PL/PerlU function.
>
> Hm. Is it possible that the prepared statement recursively called the
> *same* plperl function? And that somebody did a CREATE OR REPLACE on
> that function meanwhile?

No, that doesn't seem possible in this case. The function calls some
prepared statements repeatedly, but no recursion should occur.

> This
> might be the wrong theory. You seem to have debug symbols for that
> core dump --- can you tell which of the dereferences in line 3373
> caused the crash?

The current_call_data->prodesc->fn_readonly one.

Please let me know if I can be of more assistance.

Regards,
Marko Tiikkaja

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Eisentraut 2012-09-05 22:57:05 Re: BUG #7514: postgres -k no longer works with spaces in the path
Previous Message Kevin Grittner 2012-09-05 15:00:45 Re: BUG #7519: incresed data base size and query performance lost