From: | Michael Fuhr <mike(at)fuhr(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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:29:57 |
Message-ID: | 20050820052957.GA48423@winnie.fuhr.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Sat, Aug 20, 2005 at 01:14:02AM -0400, Tom Lane wrote:
> 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?
You might be on to something there. I just changed line 683 in
plperl.c to the following:
count = perl_call_pv((trusted ? "::mksafefunc" : "::mkunsafefunc"),
My test cases now succeed where they had been failing. But if
that's the problem, why are your systems behaving differently?
--
Michael Fuhr
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Fuhr | 2005-08-20 05:59:07 | Re: BUG #1831: plperl gives error after reconnect. |
Previous Message | Tom Lane | 2005-08-20 05:21:56 | Re: BUG #1831: plperl gives error after reconnect. |