Mon Jun 28 08:50:31 PDT 2010
- Previous message: [Slony1-patches] slon restart on SIGALRM
- Next message: [PATCH 10/10] Fix for bug #120 The slon does not always respond to a STORE PATH (until it is restarted) The only time the no_active attribute of the node configuration in memory for the slon is at start up or with an enable node event. This is not correct in all cases, for example a storeNode might be adding an enabled node.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
The attached patches are for log-shipping. 1. When we generate the dump in slony1_dump.sh for log shipping we want to make sure we restore the dump using the replica role so any triggers on the log shipping target do not get fired during the load. 2. slony_logshipper was exiting when it ran out of log files to apply. This patch will properly detect the return code to continue sleeping/looping looking for more. -- Steve Singer Afilias Canada Data Services Developer 416-673-1142 -------------- next part -------------- A non-text attachment was scrubbed... Name: 0005-add-data-to-the-slave-as-session-replication-role-so.patch Type: text/x-patch Size: 0 bytes Desc: not available Url : http://lists.slony.info/pipermail/slony1-patches/attachments/20100628/72f1011a/attachment.bin
- Previous message: [Slony1-patches] slon restart on SIGALRM
- Next message: [PATCH 10/10] Fix for bug #120 The slon does not always respond to a STORE PATH (until it is restarted) The only time the no_active attribute of the node configuration in memory for the slon is at start up or with an enable node event. This is not correct in all cases, for example a storeNode might be adding an enabled node.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-patches mailing list