From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Michael Fuhr <mike(at)fuhr(dot)org> |
Cc: | Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #1831: plperl gives error after reconnect. |
Date: | 2005-08-20 05:14:02 |
Message-ID: | 10927.1124514842@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Michael Fuhr <mike(at)fuhr(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Fuhr | 2005-08-20 05:16:25 | Re: BUG #1831: plperl gives error after reconnect. |
Previous Message | Michael Fuhr | 2005-08-20 04:57:17 | Re: BUG #1831: plperl gives error after reconnect. |