Fri Nov 4 13:21:10 PDT 2011
- Previous message: [Slony1-bugs] [Bug 247] Slony log shipper doesn't parse TRUNCATE
- Next message: [Slony1-bugs] [Bug 248] Log shipper targets can't add sequences after initial setup
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=248 Summary: Log shipper targets can't add sequences after initial setup Product: Slony-I Version: 2.0 Platform: PC OS/Version: Linux Status: NEW Severity: enhancement Priority: low Component: slon AssignedTo: slony1-bugs at lists.slony.info ReportedBy: ssinger at ca.afilias.info CC: slony1-bugs at lists.slony.info Estimated Hours: 0.0 The slony1_dump.sh creates a sl_sequence_offline table for tracking sequences on a log shipping target. If you add+subscribe a new sequence to a new set after the log shipping slave has been setup then the slon generating the log ship files will not generate any SQL to update sl_sequence_offline to reflect the new sequence. Updates to the sequence then fail on the log shipping target. I have changes to the LogShipping.js disorder test to replicate this issue that I will include with the fix. I think 2.0 2.1 and 2.2 all have this bug (I haven't looked at the log shipping code in 1.2) -- Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You are the assignee for the bug.
- Previous message: [Slony1-bugs] [Bug 247] Slony log shipper doesn't parse TRUNCATE
- Next message: [Slony1-bugs] [Bug 248] Log shipper targets can't add sequences after initial setup
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list