Re: [BUG] Segmentation fault in pfree in PLy_output_tuple_funcs - Mailing list pgsql-bugs

From Sergey Konoplev
Subject Re: [BUG] Segmentation fault in pfree in PLy_output_tuple_funcs
Date
Msg-id CAL_0b1t8VLnPW-5D-FcTozhK=DDcNDU2vZehOM5U2n=HjF-Yag@mail.gmail.com
Whole thread Raw
In response to Re: [BUG] Segmentation fault in pfree in PLy_output_tuple_funcs  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: [BUG] Segmentation fault in pfree in PLy_output_tuple_funcs  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Tue, Dec 10, 2013 at 1:17 PM, Alvaro Herrera
<alvherre@2ndquadrant.com> wrote:
>> Yesterday we faced a segfault on a simple PL/Python function's call:
>>
>> CREATE OR REPLACE FUNCTION test_test()
>> RETURNS TABLE("=E9=C4=C5=CE=D4=C9=C6=C9=CB=D4=CF=D2" int, "=E7=CF=D3. =
=CE=CF=CD=C5=D2" varchar) AS
>> $BODY$
>> import time
>> cars =3D plpy.prepare("""
>>     select id, ident_code from cars limit 100
>> """)
>
> What's the likelihood that table "cars" was being modified concurrently?

It is rather high. Probably even very high.

--=20
Kind regards,
Sergey Konoplev
PostgreSQL Consultant and DBA

http://www.linkedin.com/in/grayhemp
+1 (415) 867-9984, +7 (901) 903-0499, +7 (988) 888-1979
gray.ru@gmail.com

pgsql-bugs by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [BUG] Segmentation fault in pfree in PLy_output_tuple_funcs
Next
From: Tom Lane
Date:
Subject: Re: [BUG] Segmentation fault in pfree in PLy_output_tuple_funcs