Quoting Gianni Mariani <gianni@mariani.ws>:
> Keith C. Perry wrote:
>
> >I had this same issue as well but now I'm *slightly* concerned since most of
> my
> >code is perl. How soon would issue be reviewed? (not that I'm NOT going to
> use
> >your patch for right now).
> >
>
> I suspect that this is only an issue when you use
> "--enable-thread-safety" which according to the release notes is only
> for libpq and only fixes MT issues on connection start-up. So
> theoretically, if you're using plperl in V7.3.4 or earlier, you simply
> don't need "--enable-thread-safety" and so you may compile happily
> without it. (That's the theory anyway).
>
> This certainly needs to be addressed (patch or document) but it's not at
> all an issue for someone migrating from an earlier release (not a
> regression). I hope that you're slightly concerned *no more*.
>
> G
I figured that much and yes I'm not concerned anymore but it does seem like it
might be version issue as well with perl and/or gcc since I did have a
successful compilation. I've got a project to move all my servers to Slackware
9.1 which will make this non-issue for me but for the original poster your patch
or omitting the "--enable-thread-safety" option look like equally good resolutions.
Thanks
--
Keith C. Perry, MS E.E.
Director of Networks & Applications
VCSN, Inc.
http://vcsn.com
____________________________________
This email account is being host by:
VCSN, Inc : http://vcsn.com