Wed Jul 7 09:54:39 PDT 2010
- Previous message: [Slony1-bugs] [Bug 135] slon can get stuck waiting for a sl_config_lock it already has
- Next 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.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=136 --- Comment #3 from Jan Wieck <janwieck at yahoo.com> 2010-07-07 09:54:39 PDT --- It is actually intended to listen for events on the same node, that is the data provider for a subscription. In this case, nodes 4 and 5 are using node 2 as data provider for a set originating on node 1. If they would be listening for events from node 1 anywhere else other than on node 2, they would possibly get those events BEFORE node 2 has finished replicating them. They cannot process them at that time anyway. Jan -- 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 135] slon can get stuck waiting for a sl_config_lock it already has
- Next 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.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list