Thu Aug 20 08:50:17 PDT 2009
- Previous message: [Slony1-general] Slony Compatable with Postgresql 8.4?
- Next message: [Slony1-general] How does it work if has different sets on different nodes?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
We are running 2.0.2 with 2 8.4 nodes and 1 8.3 node. We had to apply patches for 2 issues which reportedly have been fixed in 2.0.3. The issues were not related to locking. One was about vacuuming -- a slony function was trying to query pg_autovacuum, which is gone in 8.4. The other was a bug in the C code, see http://www.nabble.com/How-to-downgrade-from-2.0.2-to-2.0.1-tc24540512.html this thread , and that bug was also in 2.0.1. We've been live now for about a month with no further problems. -Gordon Karl Denninger wrote: > > I am attempting to migrate over to 8.4 using Slony, and am getting some > odd errors relating to locking problems. > > Is Slony (2.0.2) supposed to work with Postgresql 8.4 or am I ahead of > the Slony developers? :) > -- View this message in context: http://www.nabble.com/Slony-Compatable-with-Postgresql-8.4--tp25055873p25064746.html Sent from the Slony-I -- General mailing list archive at Nabble.com.
- Previous message: [Slony1-general] Slony Compatable with Postgresql 8.4?
- Next message: [Slony1-general] How does it work if has different sets on different nodes?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list