Tue Nov 15 13:13:40 PST 2011
- Previous message: [Slony1-commit] Slony-I-commit Fix for bug 247.
- Next message: [Slony1-commit] Slony-I-commit Fix for bug 247.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Bug 248. Stop tracking the sequence name on log shipping targets. Instead include the sequence name in the log shipping files on sequence updates. This avoids the issue of us not adding new tracking table entries on an enable subscription. Add an OMIT COPY option to the script to allow a log shipping target to be upgraded to a new slony version without reloading all the data. During an outage you would drop the $clustername schema from the target then run slony1_dump.sh with -omit_copy to reinit the node. Branch ------ master Details ------- http://git.postgresql.org/gitweb?p=slony1-engine.git;a=commitdiff;h=4b502d83cdcd072e023068d2d2b9a80c3a6e197e Modified Files -------------- RELEASE | 4 +- clustertest/disorder/tests/LogShipping.js | 6 ++ src/slon/remote_worker.c | 9 ++- src/slony_logshipper/parser.y | 10 ++-- tools/slony1_dump.sh | 100 +++++++++++++--------------- 5 files changed, 66 insertions(+), 63 deletions(-)
- Previous message: [Slony1-commit] Slony-I-commit Fix for bug 247.
- Next message: [Slony1-commit] Slony-I-commit Fix for bug 247.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list