Thu Aug 19 13:39:16 PDT 2010
- Previous message: [Slony1-bugs] [Bug 137] execute script does not get applied in the correct order
- Next message: [Slony1-bugs] [Bug 139] sighandler is calling non async safe functions
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=75 --- Comment #10 from Christopher Browne <cbbrowne at ca.afilias.info> 2010-08-19 13:39:16 PDT --- (In reply to comment #9) > Created an attachment (id=59) --> (http://www.slony.info/bugzilla/attachment.cgi?id=59) [details] > Proposed patch for bug 75 > > Patch to commit session settings. Available also at github as a branch off > REL_2_0_STABLE here: http://github.com/wieck/slony1-engine/tree/bug75 This compiles and runs fine for me, against the "testddl" test (http://github.com/wieck/slony1-engine/tree/master/tests/testddl/). Unfortunately, according to the bug, we're masking the problem. Is there a straightforward way to induce the bug to express itself, so that we can expressly see that it's fixed? I'd think there should be some update we could do to "testddl" that would exercise the bug, even if all it involves is spelunking in the Postgres logs to verify that raised notices indicate the right values. -- 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.
- Previous message: [Slony1-bugs] [Bug 137] execute script does not get applied in the correct order
- Next message: [Slony1-bugs] [Bug 139] sighandler is calling non async safe functions
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list