ML mail <[EMAIL PROTECTED]> writes:

> Hello,
> I am currently installing Slony1 1.1.2 with PostgreSQL 8.1.2 and read in the 
> INSTALL file that I should compile PostgreSQL with the
> --enable-thread-safety option because I am using Solaris 9 on SPARC Platform 
> (Sun Netra X1). That's what I did but at the end of the
> configure I get the following error message:
> *** Thread test program failed.  Your 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.  However, you must then run
> *** the program in src/tools/thread and add locking function calls
> *** to your applications to guarantee thread safety.             
> Does anyone know what's the problem here and what should I do ? Shall I 
> simply ignore this error and compile ? Or can I use PostgreSQL with
> Slony1 without this option ?
> Many thanks in advance for any hints or advices.
> Best regards

Hmm.  We're not using Solaris anymore so wisdom available may be
limited.

The thing that you need is for libpq to be compiled with thread safety
turned on, as otherwise, the multiple Slony-I threads that call libpq
will trample over one another.

What I'd suggest is that you look in config.log; the last program that
configure compiled should be listed there, and there should be some
indication as to what failed.  (Sometimes error messages are
deceiving, of course.)

You can always *try* to proceed, and see what you get.

If libpq isn't suitably thread safe, you can expect that slon queries
looking for events will fail; there are a couple of typical error
messages.

See the FAQ for more details...

<http://linuxdatabases.info/info/faq.html>
-- 
select 'cbbrowne' || '@' || 'ca.afilias.info';
<http://dba2.int.libertyrms.com/>
Christopher Browne
(416) 673-4124 (land)
_______________________________________________
Slony1-general mailing list
[email protected]
http://gborg.postgresql.org/mailman/listinfo/slony1-general

Reply via email to