Re: segmentation fault postgres 9.3.5 core dump perlu related ?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Day, David" <dday(at)redcom(dot)com>
Cc: Alex Hunsaker <badalex(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: segmentation fault postgres 9.3.5 core dump perlu related ?
Date: 2015-01-29 15:40:07
Message-ID: 5285.1422546007@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Day, David" <dday(at)redcom(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Roger Pack 2015-01-29 17:51:00 4B row limit for CLOB tables
Previous Message Day, David 2015-01-29 14:54:23 Re: segmentation fault postgres 9.3.5 core dump perlu related ?