From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
Cc: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net>, Christopher Browne <cbbrowne(at)ca(dot)afilias(dot)info>, slony1-general(at)gborg(dot)postgresql(dot)org, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: [Slony1-general] Thread-safety detection on HP-UX |
Date: | 2004-10-26 22:13:31 |
Message-ID: | 200410262213.i9QMDVf05471@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Jan Wieck wrote:
> On 10/22/2004 3:30 PM, Ed L. wrote:
>
> > Clean build of pgsql 7.4.5 on HPUX B.11.23 on ia64 with
> > --enable-thread-safety fails ... :(
> >
> > $uname -a
> > HP-UX ... B.11.23 U ia64 0144848471 unlimited-user license
> >
> > $cd postgresql-7.4.5
> > $./configure --enable-thread-safety --without-readline --without-zlib
> > ...
> > checking pthread.h usability... yes
> > checking pthread.h presence... yes
> > checking for pthread.h... yes
> > configure: error:
> > Cannot enable threads on your platform.
>
> Unfortunately that doesn't mean that the switch is required to cause
> libpq to behave nicely for the Slony purposes. Can someone please test
> if Slony works on HP-UX even if PostgreSQL is NOT configured with
> --enable-thread-safety ?
I believe Slony always needs threading, it just can be used even if the
OS doesn't fully support all thread-safe functions, so on 8.0 you use
--thread_safety_force. Jan, is that correct?
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | PostgreSQL Bugs List | 2004-10-26 23:28:44 | BUG #1297: Postgres after 7.3.5 does not works on initdb stage |
Previous Message | C. David Wilde | 2004-10-26 19:23:10 | Strange behavior in psql |