Fri Jun 10 23:06:39 PDT 2005
- Previous message: [Slony1-commit] By wieck: Added release notes for 1.0.6
- Next message: [Slony1-commit] By devrim: Add supported platforms list among adminguide directory in
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Log Message:
-----------
Stamped release 1.0.6
Jan
Tags:
----
REL_1_0_STABLE
Modified Files:
--------------
slony1-engine:
HISTORY-1.0 (r1.1.2.11 -> r1.1.2.12)
config.h.in (r1.8.2.4 -> r1.8.2.5)
slony1-engine/src/backend:
slony1_funcs.sql (r1.15.2.16 -> r1.15.2.17)
-------------- next part --------------
Index: HISTORY-1.0
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/Attic/HISTORY-1.0,v
retrieving revision 1.1.2.11
retrieving revision 1.1.2.12
diff -LHISTORY-1.0 -LHISTORY-1.0 -u -w -r1.1.2.11 -r1.1.2.12
--- HISTORY-1.0
+++ HISTORY-1.0
@@ -20,6 +20,43 @@
----------------------------
+ date: 2005/04/13 21:21:24; author: cbbrowne;
+ Address synchronization problem where a MOVE_SET event may
+ get to cascaded subscribers *AFTER* the new origin has started
+ generating SYNCs. The subscriber ignored those syncs since it doesn't
+ yet know the origin has moved; this can lead to data loss.
+
+ The ACCEPT_SET is added as a remedy; upon submitting the MOVE_SET,
+ it also raises, on the new origin, an ACCEPT_SET event. That
+ will necessarily precede any SYNCs coming from the new origin.
+
+ Nodes that get the ACCEPT_SET event will wait until they also get
+ the MOVE_SET event before proceeding, protecting from data loss.
+
+ ----------------------------
+
+ date: 2005/04/13 20:39:32; author: cbbrowne;
+ Address bug #1226
+
+ If a set contains no tables, then warn the user that they may run afoul
+ of bug #1226.
+
+ ----------------------------
+
+ date: 2005/02/16 22:31:19; author: smsimms;
+ Add a missing WHERE clause that causes MOVE SET to fail when:
+ 1. There are three or more nodes
+ 2. Sets originate on at least two nodes
+ 3. A set is being moved from a third node to one of the first two.
+
+ ----------------------------
+
+ date: 2005/01/24 18:42:36; author: cbbrowne;
+ Added in stored function for generating SYNC events
+
+ ----------------------------
+
+
1.0.5 Bugfixes and required minor features
date: 2004/08/26 19:28:07; author: wieck;
Index: config.h.in
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/config.h.in,v
retrieving revision 1.8.2.4
retrieving revision 1.8.2.5
diff -Lconfig.h.in -Lconfig.h.in -u -w -r1.8.2.4 -r1.8.2.5
--- config.h.in
+++ config.h.in
@@ -12,7 +12,7 @@
#ifndef SLONY_I_CONFIG_H
#define SLONY_I_CONFIG_H
-#define SLONY_I_VERSION_STRING "1.0.5"
+#define SLONY_I_VERSION_STRING "1.0.6"
#undef PGSHARE
Index: slony1_funcs.sql
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/src/backend/slony1_funcs.sql,v
retrieving revision 1.15.2.16
retrieving revision 1.15.2.17
diff -Lsrc/backend/slony1_funcs.sql -Lsrc/backend/slony1_funcs.sql -u -w -r1.15.2.16 -r1.15.2.17
--- src/backend/slony1_funcs.sql
+++ src/backend/slony1_funcs.sql
@@ -218,7 +218,7 @@
returns int4
as '
begin
- return 5;
+ return 6;
end;
' language plpgsql;
- Previous message: [Slony1-commit] By wieck: Added release notes for 1.0.6
- Next message: [Slony1-commit] By devrim: Add supported platforms list among adminguide directory in
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list