The Slony team is pleased to announce the release a release candidate 
for Slony 2.2.0.

Slony 2.2.0 will be the next major release of the Slony-I replication 
system for PostgreSQL.

Key features of the 2.2.0 release include:

* The storage and transport and application of the slony log 
(sl_log_1/sl_log_2) has changed providing performance improvements. Data 
is now stored in a different format and the postgresql COPY protocol and 
triggers are used to replicate and apply changes to replicas.

* DDL handling with the EXECUTE SCRIPT command has changed.  The DDL is 
no longer stored as a special event in sl_event but is instead stored in 
sl_log_script and is processed as part of a SYNC event inline with data 
changes. DDL can also be specified inline

* FAILOVER has been reworked to be more reliable but not all nodes can 
be used as failover targets.

* A RESUBSCRIBE NODE command was added because the provider of a 
subscribed set can no longer be changed with the SUBSCRIBE SET command 
in some cases.  All sets from a particular origin must send data to 
receivers through the same path/forwarder nodes. This must remain  true 
during cluster reshaping.


Fixes from Slony 2.2.0 beta 5 included;

*  Set session_replication_role to local when applying EXECUTE SCRIPT 
commands on a replica(Bug 305)

* Record the sequence values as part of EXECUTE SCRIPT (Bug 304)

* Fixes to failover (Bug 310) and UPDATE FUNCTIONS (Bug 309)



See the complete release notes at
http://git.postgresql.org/gitweb/?p=slony1-engine.git;a=blob_plain;f=RELEASE;h=adb7c4c9096010189c5d8c91222ad040393093eb



You can download slony 2.2.0 release candidate 1 with the links below

http://www.slony.info/downloads/2.2/source/slony1-2.2.0.rc1.tar.bz2
http://www.slony.info/downloads/2.2/source/slony1-2.2.0.rc1-docs.tar.bz2