Wed Aug 18 10:22:09 PDT 2010
- Previous message: [Slony1-bugs] [Bug 134] TRUNCATE support
- Next message: [Slony1-bugs] [Bug 134] TRUNCATE support
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=137 Christopher Browne <cbbrowne at ca.afilias.info> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|excute script does not get |execute script does not get |applied in the correct |applied in the correct |order |order Depends on| |134 --- Comment #3 from Christopher Browne <cbbrowne at ca.afilias.info> 2010-08-18 10:22:09 PDT --- Concurrent with resolution of the other issues, we might wish to shift the DDL data from sl_event to sl_log_1/2. In that case, we'd parse the statements just once, inside Slonik, and introduce one sl_log_* tuple for each statement. This eliminates the need to parse things later, and eliminates the need to link the C code in src/parsestatements to both slon and slonik - it's only needed by slon. We had speculated that this split might allow avoiding the ordering problems, but that is regrettably not the case, even in the ambitious scenario where we'd have commit timestamps available to us, because the time at which the DDL is executed and the time at which the DDL statement is recorded in sl_log_* isn't identical. But we'd get the other benefits mentioned earlier from the split/shift, e.g. - parse once, and eliminate component from slon. -- 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 134] TRUNCATE support
- Next message: [Slony1-bugs] [Bug 134] TRUNCATE support
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list