Re: slony question

Thanks. Im testing slony1-1.2.12 in postgres 8.3beta3 version. I tried to
configure slony but I keep getting this error.

./configure --with-pgconfigdir=/export/home/sjothirajah/postgres8.3/bin
--with-enable-thread-safety
or
./configure --with-pgconfigdir=/export/home/sjothirajah/postgres8.3/bin
--enable-thread-safety

........
........
checking for correct version of PostgreSQL... 8.3
pg_config says pg_sharedir is /usr4/postgres8.3/share/postgresql/
checking PostgreSQL for enable-thread-safety as required on solaris2.10...
no
configure: error: PostgreSQL needs to be compiled with
--enable-thread-safety on solaris2.10

Can you help
Thanks
josh

On Dec 10, 2007 8:19 PM, Geoffrey <lists(at)serioustechnology(dot)com> wrote:

> Scott Marlowe wrote:
> > On Dec 10, 2007 2:19 PM, Chris Browne <cbbrowne(at)acm(dot)org> wrote:
> >> joshques(at)gmail(dot)com ("Josh Harrison") writes:
> >>> Does slony support postgres major version upgrade ? ie., will it
> >>> replicate between different major versions?
> >> Yes, that's one of the major "use cases" for Slony-I.
> >>
> >> Version 1.0 and 1.1 support (loosely) from PostgreSQL 7.3 to 8.1-ish.
> >>
> >> Version 1.2 dropped 7.3 support, but supports up to (just about;
> >> there's a patch not in a 1.2 release that is needed for late-breaking
> >> 8.3 changes) 8.3.
> >
> > Didn't 1.2 drop support for pg 7.4 as well? I thought I remembered
> > reading that some time ago.
>
> Not according to the docs:
>
> http://slony.info/documentation/requirements.html
> Section 3.1, 3rd bullet:
>
> You also need a recent version of PostgreSQL source. Slony-I depends on
> namespace support so you must have PostgreSQL version 7.3.3 or newer to
> be able to build and use Slony-I.
>
> It says the same thing in the Slony 1.2.12 docs rpm.
>
> --
> Until later, Geoffrey
>
> Those who would give up essential Liberty, to purchase a little
> temporary Safety, deserve neither Liberty nor Safety.
> - Benjamin Franklin
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq
>