From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Michael Fuhr <mike(at)fuhr(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: PL/Perl list value return causes segfault |
Date: | 2005-07-12 19:33:04 |
Message-ID: | 20050712193303.GA14060@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-hackers pgsql-patches |
On Tue, Jul 12, 2005 at 02:59:37PM -0400, Andrew Dunstan wrote:
> Note that all plperl functions are called in scalar context, and it is
> always wrong to return a list (as opposed to a listref). In fact, the
> value received might surprise you even if it worked (it would be the
> value of the last member of the list).
Hmm, I don't know if it's feasible to do in Perl, but maybe check
whether the function wants to return something in list context and throw
an appropiate error message?
--
Alvaro Herrera (<alvherre[a]alvh.no-ip.org>)
"Nunca se desea ardientemente lo que solo se desea por razón" (F. Alexandre)
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2005-07-12 19:45:55 | Re: PL/Perl list value return causes segfault |
Previous Message | David Fetter | 2005-07-12 19:21:29 | Doc patch: New PL/Perl Features |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2005-07-12 19:45:55 | Re: PL/Perl list value return causes segfault |
Previous Message | Tom Lane | 2005-07-12 19:06:45 | Re: pg_dump schema search_path; selectSourceSchema() |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2005-07-12 19:45:55 | Re: PL/Perl list value return causes segfault |
Previous Message | David Fetter | 2005-07-12 19:21:29 | Doc patch: New PL/Perl Features |