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

From Tom Lane
Subject Re: BUG #1831: plperl gives error after reconnect.
Date
Msg-id 10927.1124514842@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #1831: plperl gives error after reconnect.  (Michael Fuhr <mike@fuhr.org>)
Responses Re: BUG #1831: plperl gives error after reconnect.  (Michael Fuhr <mike@fuhr.org>)
List pgsql-bugs
Michael Fuhr <mike@fuhr.org> writes:
> I see that both of your Perl version strings have "thread-multi"
> whereas neither of mine do.  I don't know if that's relevant, but
> it's something different about the Perl builds.

Hm.  I also have a 5.8.7-no-threads Perl build on HPPA.  I hadn't
tried that because that platform sucks at debugging shared libraries.
But building there now to see if I can reproduce the problem.

> You're doing the reconnect, right?

Sure.  It seems perfectly clear that this has something to do with
being the first call in a session.  (The validator function would
also count as the first call, which explains your previous Solaris
results.)

One thing I was kind of wondering about (this will betray the fact
that I haven't really studied Perl since it was Perl 4) is what are
the namespace issues for ::mksafefunc?  In particular, could the
inner invocation of foo() be executing in some context that makes
the original definition of mksafefunc inaccessible?  And why, if
we are careful to declare mksafefunc with ::, don't we call it
with :: too?

            regards, tom lane

pgsql-bugs by date:

Previous
From: Michael Fuhr
Date:
Subject: Re: BUG #1831: plperl gives error after reconnect.
Next
From: Michael Fuhr
Date:
Subject: Re: BUG #1831: plperl gives error after reconnect.