BUG #3713: problem with thread safety??? - Mailing list pgsql-bugs

From Ted Petrosky
Subject BUG #3713: problem with thread safety???
Date
Msg-id 200711021611.lA2GBgRU013907@wwwmaster.postgresql.org
Whole thread Raw
Responses Re: BUG #3713: problem with thread safety???  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
The following bug has been logged online:

Bug reference:      3713
Logged by:          Ted  Petrosky
Email address:      tedpet5@yahoo.com
PostgreSQL version: 8.3 beta 2
Operating system:   OS X 10.5
Description:        problem with thread safety???
Details:

whilst configuring on a new Leopard install with this config line:

./configure --with-bonjour --enable-thread-safety --with-perl --with-python
--with-libedit-preferred


checking for sgmlspl... no
checking thread safety of required library functions... no
configure: error: thread test program failed
This platform is not thread-safe.  Check the file 'config.log'for the
exact reason.

You can use the configure option --enable-thread-safety-force to force
threads to be enabled.  But you must then run the program in
src/test/thread and add locking function calls to your applications to
guarantee thread safety.


I have never seen this before on OS X and I don't really know if it is a
limitation or a bug.

Ted

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: I have a question about using index in order statement.
Next
From: Tom Lane
Date:
Subject: Re: BUG #3713: problem with thread safety???