From: | "Ted Petrosky" <tedpet5(at)yahoo(dot)com> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | BUG #3713: problem with thread safety??? |
Date: | 2007-11-02 16:11:42 |
Message-ID: | 200711021611.lA2GBgRU013907@wwwmaster.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The following bug has been logged online:
Bug reference: 3713
Logged by: Ted Petrosky
Email address: tedpet5(at)yahoo(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-11-02 16:21:30 | Re: BUG #3713: problem with thread safety??? |
Previous Message | Felipe Amezquita | 2007-11-02 16:09:23 | could not open relation |