Permalink
Browse files

Indicate in release notes that PG 8.2 is now supported, and 7.3 is NOT.

  • Loading branch information...
1 parent 1ce6486 commit 606c9159934a48ba9d1f2a1f70a0d73352f8472d Christopher Browne committed Oct 6, 2006
Showing with 14 additions and 2 deletions.
  1. +14 −2 RELEASE-1.2.0
View
@@ -1,4 +1,4 @@
-$Id: RELEASE-1.2.0,v 1.11 2006-09-29 17:27:21 cbbrowne Exp $
+$Id: RELEASE-1.2.0,v 1.12 2006-10-06 20:21:35 cbbrowne Exp $
Release 1.2 of Slony-I has numerous improvements over previous
versions.
@@ -57,7 +57,7 @@ how Slony-I manages replication configuration. These include:
- When possible (based on log switching functionality), partial
indexes on sl_log_1 and sl_log_2 are created on a per-origin-node
basis. This provides the performance boost of having an easily
- recognizable index, but without the risk of having XIDs from
+ recognisable index, but without the risk of having XIDs from
different nodes mixed together in one index, where roll-over could
Cause Problems...
@@ -71,6 +71,18 @@ There are also numerous enhancements that are more directly visible:
A group of developers has contributed changes to allow running
Slony-I as a Windows service.
+- PostgreSQL Version Compatibility Changes
+
+ Slony-I developers have been following the 8.2 release expected in
+ fall 2006; Slony-I 1.2 can be expected to work with it without
+ problems.
+
+ Compatibility with version 7.3 has been dropped; version 1.2 notably
+ makes use of some array functionality that didn't exist in 7.3. If
+ you are on 7.3, you're on a REALLY OLD version of PostgreSQL, and
+ really ought to upgrade. You may use Slony-I 1.1.5 to get to a more
+ modern version, and then upgrade to 1.2 as needed.
+
- Process structure is revised considerably; in 1.1.0, an attempt was
made to create an internal 'watchdog' that would restart threads
that fell over for whatever reason.

0 comments on commit 606c915

Please sign in to comment.