On Thu, Jan 29, 2015 at 1:54 PM, Day, David <dday@redcom.com> wrote:
Thanks for the inputs, I’ll attempt to apply it and will update when I have some new information.
BTW a quick check would be to attach with gdb right after you connect, check info threads (there should be none), run the plperlu procedure (with the right arguments/calls to hit all the execution paths), check info threads again. If info threads now reports a thread, we are likely looking at the right plperlu code. It should just be a matter of commenting stuff out to deduce what makes the thread. If not, it could be that plperlu is not at fault and its something else like an extension or some other procedure/pl.
