From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Testing plperl<->plperlu interaction |
Date: | 2010-01-06 23:46:53 |
Message-ID: | 4B4520ED.5000602@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tim Bunce wrote:
> I was investigating a bug in an 8.4.1 production system and distilled a
> test case down to this:
>
> CREATE OR REPLACE FUNCTION bar() RETURNS integer AS $$
> #die 'BANG!'; # causes server process to exit(2)
> # alternative - causes server process to exit(255)
> spi_exec_query("invalid sql statement");
> $$ language plperl; -- plperl or plperlu
>
> CREATE OR REPLACE FUNCTION foo() RETURNS integer AS $$
> spi_exec_query("SELECT * FROM bar()");
> return 1;
> $$ LANGUAGE plperlu; -- must be opposite to language of bar
>
> SELECT * FROM bar(); -- throws exception normally
> SELECT * FROM foo(); -- causes the server to exit abnormaly
>
> before then rereading the 8.4.2 release notes and seeing that the bug
> was already fixed. D'oh!
>
> I see the test suite doesn't have any plperlu tests at all.
> Is there any reason for that?
>
>
>
Just that we haven't bothered. But we can't run tests for both in the
same session because that doesn't work on all platforms. I actually
played a bit with it the other day. Setting up some plperlu tests would
be very simple.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | decibel | 2010-01-06 23:54:57 | Re: Testing plperl<->plperlu interaction |
Previous Message | Tim Bunce | 2010-01-06 23:38:52 | Testing plperl<->plperlu interaction |