Re: BUG #1473: Backend bus error, possibly due to ANALYZE - Mailing list pgsql-bugs

From Brian B.
Subject Re: BUG #1473: Backend bus error, possibly due to ANALYZE
Date
Msg-id 20050212032446.GA25933@bbdab.org
Whole thread Raw
In response to Re: BUG #1473: Backend bus error, possibly due to ANALYZE  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #1473: Backend bus error, possibly due to ANALYZE  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Fri, Feb 11, 2005 at 10:05:36PM -0500, Tom Lane wrote:
> "Brian B." <brian-pgsql@bbdab.org> writes:
> > When setting the "LIBC_R" option, the FreeBSD port essentially sets CFLAGS to
> > -D_THREAD_SAFE and LDFLAGS to -pthread. This is probably due to the Python
> > procedural handler not being able to link with PostgreSQL until PostgreSQL
> > is built pthread-aware.
>
> Hmm, is that a FreeBSD-specific restriction?  I've not had any such
> trouble on Linux or Mac OS X.

I was citing that behavior from memory. It actually builds/installs OK until
one decides to add the handler to a database:

$ createlang plpythonu
createlang: language installation failed: ERROR:  could not load library
"/usr/local/lib/postgresql/plpython.so": dlopen
'/usr/local/lib/postgresql/plpython.so' failed.
(/usr/local/lib/python2.4/config/libpython2.4.so: Undefined symbol
"pthread_attr_destroy")

If I build the backend with the pthread stuff, this step succeeds.


Thanks,

Brian B.

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #1473: Backend bus error, possibly due to ANALYZE
Next
From: Tom Lane
Date:
Subject: Re: BUG #1473: Backend bus error, possibly due to ANALYZE