Tue Jul 6 12:33:32 PDT 2010
- Previous message: [Slony1-bugs] [Bug 75] Bugs: (1) Initialize forgotten cs->plan_active_log. (2) Session_replication_role and "SET datestyle TO 'ISO'" in slonik at connection start.
- Next message: [Slony1-bugs] [Bug 135] slon can get stuck waiting for a sl_config_lock it already has
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
bugzilla-daemon at main.slony.info writes: > http://www.slony.info/bugzilla/show_bug.cgi?id=75 > > --- Comment #1 from Jan Wieck <janwieck at yahoo.com> 2010-07-06 11:40:37 PDT --- > plan_active_log can only be NULL on the very first trigger call in a session. > At this time, the currentXid is invalid, so the check for !cs->plan_active_log > is redundant. > > About setting date style and replication role, wouldn't committing the > transaction instead of rolling it back have the desired effects? My reading of the bug was that doing a COMMIT rather than ROLLBACK would have the desired effect of not rolling back these settings. That seems a good approach to me. -- output = ("cbbrowne" "@" "ca.afilias.info") Christopher Browne "Bother," said Pooh, "Eeyore, ready two photon torpedoes and lock phasers on the Heffalump, Piglet, meet me in transporter room three"
- Previous message: [Slony1-bugs] [Bug 75] Bugs: (1) Initialize forgotten cs->plan_active_log. (2) Session_replication_role and "SET datestyle TO 'ISO'" in slonik at connection start.
- Next message: [Slony1-bugs] [Bug 135] slon can get stuck waiting for a sl_config_lock it already has
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list