Fri Jul 9 07:02:31 PDT 2010
- Previous message: [Slony1-bugs] [Bug 139] sighandler is calling non async safe functions
- Next message: [Slony1-bugs] [Bug 104] slon core in sched_add_fdset
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=75 --- Comment #4 from Steve Singer <ssinger at ca.afilias.info> 2010-07-09 07:02:31 PDT --- I wrote up a patch to add a "commit transaction" at the top of remoteWorkerThread_main appended after the "set session_replication_role". When I test it I get warnings, "WARNING: there is no transaction in progress". Nor do I see where we start the transaction. This was with 8.3 is there either a configuration option, environment variable or change with a newer version that makes libpq default to auto-commit=false? Otherwise I don't see why the set session_replication would be rolled back because it isn't done as part of a transaction. -- 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 139] sighandler is calling non async safe functions
- Next message: [Slony1-bugs] [Bug 104] slon core in sched_add_fdset
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list