Thu Feb 14 11:41:36 PST 2013
- Previous message: [Slony1-general] Is there a way to cap the file size of slony log shipping files?
- Next message: [Slony1-general] Slony 2.2.0 beta 3 released
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
The Slony team has released a bug fix release for Slony 2.1. Slony 2.1.3 is the next release in the 2.1 series. This release includes the following changes from 2.1.2 - Bug #285 :: Fix race condition with MOVE SET where a third node could get updated to the wrong SYNC number - Bug #276 :: Fixed duplicate key detection on sl_nodelock - Bug #278 :: assorted spelling fixes - Add in explicit support to recognise PostgreSQL 9.2, rather than warning that it may not be supported - Add --with-pgport option to configure and when set to yes let slonik use these functions to determine the PGSHARE directory at runtime. This defaults to no Users of 2.1.1 or 2.1.2 that make use of the MOVE SET command and have three or more nodes in the cluster are encouraged to update to 2.1.3 as soon as possible.
- Previous message: [Slony1-general] Is there a way to cap the file size of slony log shipping files?
- Next message: [Slony1-general] Slony 2.2.0 beta 3 released
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list