Mon Mar 19 14:26:17 PDT 2012
- Previous message: [Slony1-general] Moveset changes to sub_forward
- Next message: [Slony1-general] Moveset changes to sub_forward
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Le 19/03/2012 22:04, Brian Trudal a écrit : > Hi there Hi, > > We have 3 nodes in cluster. > > After moving a set from one node (node-1) to another (node-2), whats the best > way to reset the origin in another subscriber (node-3) as it still talking to > node-1 as node-1 is doing forward of node-2 changes to node-3 ; rather I want > node-3 directly talk to node-2 (new origin) without sub_forward by node-1. > > The sl_subscribe looks like this: > > engine_db=# select * from sl_subscribe where sub_set=1; > sub_set | sub_provider | sub_receiver | sub_forward | sub_active > ---------+--------------+--------------+-------------+------------ > 1 | 1 | 3 | f | t > 1 | 2 | 1 | t | t > (3 rows) > > Rather, after moveset, I expected, line 1 to go away and line-2 to have direct > replication to 3 instead of forward through 1. > You can re-subscribe your nodes in a way that fits your needs. Just issue subscribe sets commands, and tell node 3 to subscribe to 2. BR, -- Stéphane Schildknecht http://www.Loxodata.com Contact régional PostgreSQL
- Previous message: [Slony1-general] Moveset changes to sub_forward
- Next message: [Slony1-general] Moveset changes to sub_forward
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list