Tue Dec 4 13:02:55 PST 2007
- Previous message: [Slony1-general] Renumbering a node and renaming a database
- Next message: [Slony1-general] Dropped a node and still has status
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
<postgres at dac.e4ward.com> writes: > Hi there. > > I've droped our node2 from replication and would like to renumber > node3 as node2 for the sake of beauty. :-D > > I'd like to rename node3 replicated database too. > > Is there any procedure to do this kind of stuff aside from creating a > new node2 replication and going over all the new node replication > obvious one? That wold consume much time. Unfortunately, node numbering is deeply intertwined into the configuration of a cluster. Indeed, it is intertwined to the point that the node number is associated with numerous tables *across nodes.* You won't be able to change this consistently without a lot more trouble thatn it seems to be worth. -- output = reverse("ofni.secnanifxunil" "@" "enworbbc") http://cbbrowne.com/info/internet.html Rules of the Evil Overlord #82. "I will not shoot at any of my enemies if they are standing in front of the crucial support beam to a heavy, dangerous, unbalanced structure. <http://www.eviloverlord.com/>
- Previous message: [Slony1-general] Renumbering a node and renaming a database
- Next message: [Slony1-general] Dropped a node and still has status
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list