Skip site navigation (1) Skip section navigation (2)

Re: BUG #1473: Backend bus error, possibly due to ANALYZE

From: "Brian B(dot)" <brian-pgsql(at)bbdab(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #1473: Backend bus error, possibly due to ANALYZE
Date: 2005-02-12 03:24:46
Message-ID: 20050212032446.GA25933@bbdab.org (view raw or flat)
Thread:
Lists: pgsql-bugs
On Fri, Feb 11, 2005 at 10:05:36PM -0500, Tom Lane wrote:
> "Brian B." <brian-pgsql(at)bbdab(dot)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.

In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2005-02-12 03:33:00
Subject: Re: BUG #1473: Backend bus error, possibly due to ANALYZE
Previous:From: Tom LaneDate: 2005-02-12 03:05:36
Subject: Re: BUG #1473: Backend bus error, possibly due to ANALYZE

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group