On Sat, Aug 20, 2005 at 03:30:07PM -0400, Andrew Dunstan wrote:
> How far back has this bug been verified? Was it in 7.4 before we made
> some large changes to plperl?
Not sure -- the problem showed up with SPI, which wasn't in the
stock PL/Perl until 8.0. I haven't done tests with earlier versi
Tom Lane wrote:
Michael Fuhr <[EMAIL PROTECTED]> writes:
The attached patch appears to fix the problem discussed in the
"plperl gives error after reconnect" thread in pgsql-bugs:
I think this patch is a good idea just on grounds of namespace
safety, so I'll go ahead and apply it. B
Michael Fuhr <[EMAIL PROTECTED]> writes:
> The attached patch appears to fix the problem discussed in the
> "plperl gives error after reconnect" thread in pgsql-bugs:
I think this patch is a good idea just on grounds of namespace
safety, so I'll go ahead and apply it. But like you, I have no
idea
The attached patch appears to fix the problem discussed in the
"plperl gives error after reconnect" thread in pgsql-bugs:
http://archives.postgresql.org/pgsql-bugs/2005-08/msg00133.php
Unfortunately I don't understand *why* it fixes the problem, which
means I'm not sure that it's the correct fix.
