Wed May 30 14:58:45 PDT 2012
- Previous message: [Slony1-commit] Slony-I-commit Merge branch 'master' of ssh://git.postgresql.org/slony1
- Next message: [Slony1-commit] Slony-I-commit Additional remerges for bug 248
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Remerging bug 248. This was partially unmerged as part of the COPY protocol commits 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=93e163c6fa6c555335f65d283ce2bedc2ce28313 Modified Files -------------- RELEASE | 1 - tools/slony1_dump.sh | 237 ++++++++++++++++++++++++++++++++++++++++---------- 2 files changed, 191 insertions(+), 47 deletions(-)
- Previous message: [Slony1-commit] Slony-I-commit Merge branch 'master' of ssh://git.postgresql.org/slony1
- Next message: [Slony1-commit] Slony-I-commit Additional remerges for bug 248
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list