| From: | Michael Fuhr <mike(at)fuhr(dot)org> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | PL/Perl list value return causes segfault |
| Date: | 2005-07-12 13:04:52 |
| Message-ID: | 20050712130452.GA84564@winnie.fuhr.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers pgsql-patches |
In the latest HEAD, a PL/Perl function that returns a list value
instead of a reference causes a segmentation fault:
CREATE FUNCTION foo() RETURNS integer[] AS $$
return (1, 2, 3, 4);
$$ LANGUAGE plperl;
SELECT foo();
server closed the connection unexpectedly
Here's the stack trace:
#0 0xfed45bcc in plperl_call_handler (fcinfo=0xffbfe230) at plperl.c:1031
#1 0x0010e7d4 in ExecMakeFunctionResult (fcache=0x44af00, econtext=0x44ae58,
isNull=0x44b470 "\177~\177\177\177\177\177\177", isDone=0x44b4d8) at execQual.c:1031
#2 0x001122b0 in ExecProject (projInfo=0x44af00, isDone=0x44ae58) at execQual.c:3607
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2005-07-12 18:59:37 | Re: PL/Perl list value return causes segfault |
| Previous Message | Euler Taveira de Oliveira | 2005-07-11 12:28:52 | Re: PostgreSQL Documentation - New Appearance |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2005-07-12 13:30:04 | Where is the decision about placement of new tuple made ? |
| Previous Message | Marko Kreen | 2005-07-12 09:51:44 | Re: 4 pgcrypto regressions failures - 1 unsolved |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-07-12 14:48:40 | Re: [PATCHES] thousands comma numeric formatting in psql |
| Previous Message | Marko Kreen | 2005-07-12 09:51:44 | Re: 4 pgcrypto regressions failures - 1 unsolved |