| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Sergey Konoplev <gray(dot)ru(at)gmail(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:17:32 |
| Message-ID: | 20131210211732.GS6777@eldon.alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Sergey Konoplev escribió:
> 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?
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sergey Konoplev | 2013-12-10 21:19:35 | Re: [BUG] Segmentation fault in pfree in PLy_output_tuple_funcs |
| Previous Message | Sergey Konoplev | 2013-12-10 21:10:42 | [BUG] Segmentation fault in pfree in PLy_output_tuple_funcs |