Re: segmentation fault postgres 9.3.5 core dump perlu related ? - Mailing list pgsql-general

From Tom Lane
Subject Re: segmentation fault postgres 9.3.5 core dump perlu related ?
Date
Msg-id 5285.1422546007@sss.pgh.pa.us
Whole thread Raw
In response to Re: segmentation fault postgres 9.3.5 core dump perlu related ?  ("Day, David" <dday@redcom.com>)
Responses Re: segmentation fault postgres 9.3.5 core dump perlu related ?  (Alex Hunsaker <badalex@gmail.com>)
List pgsql-general
"Day, David" <dday@redcom.com> writes:
> I am amending the info threads info there are two threads.

Well, that's your problem right there.  There should never, ever be more
than one thread in a Postgres backend process: none of the code in the
backend is meant for a multithreaded situation, and so there are no
interlocks on global variable access etc.

Presumably what is happening is that your plperlu function is somehow
managing to spawn an additional execution thread and let that return
control as well as the original thread.  You need to prevent that.

            regards, tom lane


pgsql-general by date:

Previous
From: "Day, David"
Date:
Subject: Re: segmentation fault postgres 9.3.5 core dump perlu related ?
Next
From: Roger Pack
Date:
Subject: 4B row limit for CLOB tables