Plpython bug with int8?
От | Bradley McLean |
---|---|
Тема | Plpython bug with int8? |
Дата | |
Msg-id | 20010928120519.A32704@bradm.net обсуждение исходный текст |
Ответы |
Re: Plpython bug with int8 - Found, need advice
|
Список | pgsql-hackers |
Can someone else run this and confirm the results against the tip of the CVS repository? I'm trying to trace this bug (help welcome too). (it was hidden in a trigger and a pain to narrow to this point) -Brad ----- drop function mul1(int4,int4); drop function mul2(int4,int4); drop function callmul1(); drop function callmul2a(); drop function callmul2b(); create function mul1(int4,int4) returns int8 as 'select int8($1) * int8($2)' language 'sql'; create function mul2(int4,int4) returns int8 as 'select int8($1) * 4294967296::int8 + int8($2)' language 'sql'; create function callmul1() returns int8 as 'return plpy.execute("select mul1(6,7) as x")[0]["x"]' language 'plpython'; create function callmul2a() returns int8 as 'select mul2(7,8)' language 'sql'; create function callmul2b() returns int8 as 'return plpy.execute("select mul2(7,8) as x")[0]["x"]' language 'plpython'; select mul1(3,4); select callmul1(); select mul2(5,6); select callmul2a(); select callmul2b(); Results: ...callmul1 ---------- 42 (1 row) mul2 -------------21474836486 (1 row) callmul2a -------------30064771080 (1 row) psql:bug:14: pqReadData() -- backend closed the channel unexpectedly.This probably means the backend terminated abnormallybeforeor while processing the request. psql:bug:14: connection to server was lost
В списке pgsql-hackers по дате отправления: