From: | "Sokolov Yura" <falcon(at)intercable(dot)ru> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | BUG #2720: plpythonu with Python 2.5 crashes |
Date: | 2006-10-25 14:33:23 |
Message-ID: | 200610251433.k9PEXNXC095357@wwwmaster.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The following bug has been logged online:
Bug reference: 2720
Logged by: Sokolov Yura
Email address: falcon(at)intercable(dot)ru
PostgreSQL version: 8.2beta1
Operating system: Slackware linux 10.2
Description: plpythonu with Python 2.5 crashes
Details:
I don't know is this plpythonu problem or python 2.5 itself. With Python
2.4.3 all seems to be fine.
There was already message about this bug, but in other thread:
http://archives.postgresql.org/pgsql-hackers/2006-10/msg00872.php
Function to reproduce:
create or replace function testplpy() returns void
language plpythonu
as $$
plan = plpy.prepare('select $1::timestamptz', ['text'])
a = plpy.execute(plan, ['2006-10-01'])
$$;
select testplpy();
after this server connection process stops and whole server restarts with
message in a log like:
*** glibc detected *** free(): invalid pointer: 0xXXXXXXXX ***
LOG: server process (PID 1720) was terminated by signal 6
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2006-10-25 14:50:05 | Re: BUG #2712: could not fsync segment: Permission |
Previous Message | Dave Page | 2006-10-25 11:48:34 | Re: 8.2b2: update.bad in windows release points to wrong .msi |