Tue Aug 30 06:53:32 PDT 2011
- Previous message: [Slony1-general] how to fix replication after column added to origin outside Slony?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
The Slony team is pleased to announce the first release candidate for the next major version of Slony. 2.1.0. 2.1.0 adds the following key features to the Slony replication system: -Improvements to the performance of replication when a node is significantly behind (Bug # 167) -A component status table that monitors the state of each thread in the slon process (Bug # 175) -Multiple tables to a replication set can be added with a single command using regular expressions (Bug # 181) -Slonik will now automatically wait for event confirmations when required (Bug # 179) -Support for TRUNCATE triggers with PostgreSQL 8.4 or higher (Bug # 134) 2.1.0 also includes many bug fixes and minor features. See the release notes at http://git.postgresql.org/gitweb/?p=slony1-engine.git;a=blob_plain; f=RELEASE;hb=ffbb956db71e2638f19132149131c6c7773384db for a complete list of changes. Please try out this release candidate and report success & failures to the Slony mailing list. Users should monitor the slony mailing list and bug tracker (http://bugs.slony.info/bugzilla/) to stay informed of known issues encountered during the release candidate process.
- Previous message: [Slony1-general] how to fix replication after column added to origin outside Slony?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list