On 5/15/07, Stéphane Schildknecht <[EMAIL PROTECTED]>
wrote:
Hi ,
I have a replication consisting of 6 nodes.
N1 is master, N3 and N5 are directly connected to N1. N6 is connected to
N5 and N4 to N3.
That gives me:
test2=# select * from _instance3.sl_subscribe ;
sub_set | sub_provider | sub_receiver | sub_forward | sub_active
---------+--------------+--------------+-------------+------------
1 | 1 | 3 | t | t
1 | 1 | 5 | t | t
1 | 3 | 4 | t | t
1 | 5 | 6 | t | t
(4 lignes)
For maintenance purpose, for instance, I'd like to switch N1 and N3. I
was wondering it would give me something like :
3->1
3->5
3->4
5->6
But I then obtain :
test2=# select * from _instance3.sl_subscribe ;
sub_set | sub_provider | sub_receiver | sub_forward | sub_active
---------+--------------+--------------+-------------+------------
1 | 1 | 5 | t | t
1 | 3 | 4 | t | t
1 | 5 | 6 | t | t
1 | 3 | 1 | t | t
(4 lignes)
I thought the move set would have switched N1 and N3 for all nodes
directly subscribed to N1.
I guess that wouldn't be an unreasonable way to do things, but it's not the
way slony does things. Since all you've specified is that you want to move
the set, it doesn't change any of the subscription paths (except the obvious
re-routing necessary between the old origin and the new origin), it just
moves the set.
As I am actually wrong, what should I do in order to really move all
sets to the new master ?
Er, I think you meant move all nodes, not sets since in your example above I
only see a single set. If that's what you want, then all you'd need to do to
go from what you have above to what you appear to want is subscribe node 5
to node 3. Recall that the subscribe command is used both to initiate
subscriptions and to change subscription sources. Which is exactly what you
want to do in this case.
Andrew
_______________________________________________
Slony1-general mailing list
[email protected]
http://gborg.postgresql.org/mailman/listinfo/slony1-general
