We're trying to upgrade a Slony instance from 1.2.x to 2.0.6 on a postgres
8.3.11 instance and in the process of configuring the new slony install, the
configure script errors out saying that thread safety isn't enabled.
I went and re-configured postgres, using the --enable-thread-safety flag,
then ran make and make install. I then restarted the postgres instance with
pg_ctl -D <dir> restart -m fast. The slony config script still complained
about thready safety not being enabled
My questions:
1. Should this have worked?
1. If not, which steps did I miss? Re-initializing the cluster?
2. Does anyone know whether or not the RPMs and other various binaries
are compiled with thread safety enabled?
---
===========================
Samuel Nelson
Consistent State
www.consistentstate.com
303-955-0509
===========================
_______________________________________________
Slony1-general mailing list
[email protected]
http://lists.slony.info/mailman/listinfo/slony1-general