Re: BUG #7516: PL/Perl crash

Поиск
Список
Период
Сортировка
От Marko Tiikkaja
Тема Re: BUG #7516: PL/Perl crash
Дата
Msg-id 5047BA9C.2040405@joh.to
обсуждение исходный текст
Ответ на Re: BUG #7516: PL/Perl crash  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: BUG #7516: PL/Perl crash  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: BUG #7516: PL/Perl crash  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-bugs
Hi,

On 03/09/2012 18:06, Tom Lane wrote:
> pgmail@joh.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

В списке pgsql-bugs по дате отправления:

Предыдущее
От: boy@atsc.nl
Дата:
Сообщение: BUG #7521: Cannot disable WAL log while using pg_dump
Следующее
От: Peter Eisentraut
Дата:
Сообщение: Re: BUG #7514: postgres -k no longer works with spaces in the path