| From: | Sergey Konoplev <gray(dot)ru(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>, Maxim Boguk <maxim(dot)boguk(at)gmail(dot)com>, Максим Панченко <Panchenko(at)gw(dot)tander(dot)ru>, Соболев Виталий Анатольевич <sobolev_va(at)gw(dot)tander(dot)ru>, Сизов Сергей Павлович <sizov_sp(at)gw(dot)tander(dot)ru>, Мельковский Владимир Ярославович <Melkovskiy(at)gw(dot)tander(dot)ru> |
| Subject: | Re: [BUG] Segmentation fault in pfree in PLy_output_tuple_funcs |
| Date: | 2013-12-10 21:19:35 |
| Message-ID: | CAL_0b1t8VLnPW-5D-FcTozhK=DDcNDU2vZehOM5U2n=HjF-Yag@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Dec 10, 2013 at 1:17 PM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
>> Yesterday we faced a segfault on a simple PL/Python function's call:
>>
>> CREATE OR REPLACE FUNCTION test_test()
>> RETURNS TABLE("Идентификтор" int, "Гос. номер" varchar) AS
>> $BODY$
>> import time
>> cars = 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.
--
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(dot)ru(at)gmail(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-12-10 22:36:47 | Re: [BUG] Segmentation fault in pfree in PLy_output_tuple_funcs |
| Previous Message | Alvaro Herrera | 2013-12-10 21:17:32 | Re: [BUG] Segmentation fault in pfree in PLy_output_tuple_funcs |