Re: BUG #1831: plperl gives error after reconnect. - Mailing list pgsql-bugs

From Greg Sabino Mullane
Subject Re: BUG #1831: plperl gives error after reconnect.
Date
Msg-id c1f765ad819e74bb6b7f471de32fa643@biglumber.com
Whole thread Raw
In response to Re: BUG #1831: plperl gives error after reconnect.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #1831: plperl gives error after reconnect.  (Michael Fuhr <mike@fuhr.org>)
List pgsql-bugs
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Tom Lane asked:
> I could not duplicate this in either 8.0 or HEAD branches.  It looks
> a bit like an old bug that we had in plperl, though.  Are you sure your
> plperl.so is up to date?

Looks like Michael is already far along, but yes, my plperl.so was up to date.
This is on a Red Hat Linux box, using --with-perl and --with-gnu-ld as the
only compile options. It's a very subtle bug: on my box, simply leaving out
the trigger definition, or having the function not do a spi_exec_query will
not raise the error. I've worked around this locally by not using plperlu
(hence the original reason to switch to another user), but I sure miss
being able to do "use strict" :)

- --
Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 200508181050
https://www.biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iEYEARECAAYFAkMEoFkACgkQvJuQZxSWSsjTpwCgmt9kLApba6xDygvgl5qb/vdc
Zh4AoPx1or9LLWSTUZQDcDjxJCfNBb08
=5Jt7
-----END PGP SIGNATURE-----

pgsql-bugs by date:

Previous
From: Robert Treat
Date:
Subject: Re: [GENERAL] pgsql-bugs
Next
From: Tom Lane
Date:
Subject: Re: BUG #1832: Can't create function in plpgsql which has more than 10 parameters