Thu Jul 25 12:23:03 PDT 2013
- Previous message: [Slony1-bugs] [Bug 303] Slony Watchdog failed starting up the child process
- Next message: [Slony1-bugs] [Bug 304] Sequences are not SYNC'd as part of EXECUTE SCRIPT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=304 Summary: Sequences are not SYNC'd as part of EXECUTE SCRIPT Product: Slony-I Version: devel Platform: PC OS/Version: Linux Status: NEW Severity: enhancement Priority: low Component: stored procedures AssignedTo: slony1-bugs at lists.slony.info ReportedBy: ssinger at ca.afilias.info CC: slony1-bugs at lists.slony.info Estimated Hours: 0.0 This was observed in 2.2.0 b4 but might exists in older versions When slonik performs an EXECUTE SCRIPT on the event node, user-defined (and replicated) sequences can be at earlier values when that script is executed by slon on the remote nodes. In slony 2.2 the script in sl_log_script is executed as part of a SYNC, but the sequences are not set to the seqlog values until the END of the sync processing. Furthermore the sequences captured in sl_seqlog as part of the SYNC are captured when the SYNC is generated which might be sometime after the execute script. -- 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 303] Slony Watchdog failed starting up the child process
- Next message: [Slony1-bugs] [Bug 304] Sequences are not SYNC'd as part of EXECUTE SCRIPT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list