Fri Jun 7 12:17:25 PDT 2013
- Previous message: [Slony1-bugs] [Bug 151] Let DDL for EXECUTE SCRIPT to be specified inline
- Next message: [Slony1-bugs] [Bug 291] The slony logApply trigger messes up on cmdupdncols=0
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=291 Summary: The slony logApply trigger messes up on cmdupdncols=0 Product: Slony-I Version: devel Platform: All OS/Version: All Status: NEW Severity: blocker Priority: low Component: slon AssignedTo: slony1-bugs at lists.slony.info ReportedBy: janwieck at yahoo.com CC: slony1-bugs at lists.slony.info Estimated Hours: 0.0 When an update on the master does not materially change any column value, Slony tries to replicate this as updating the first PK column to itself. This is a special case done so that an eventual replica-only trigger would still fire on the replica. I have already identified the problem in the code and will commit a fix for it later. This affects current development until 2.2.0.b4. -- 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 151] Let DDL for EXECUTE SCRIPT to be specified inline
- Next message: [Slony1-bugs] [Bug 291] The slony logApply trigger messes up on cmdupdncols=0
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list