Wed Feb 27 02:20:27 PST 2008
- Previous message: [Slony1-general] slonik_uninstall_nodes unsafe ?
- Next message: [Slony1-general] slonik_uninstall_nodes unsafe ?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
You guess right : my purpose is precisly to add a new slave and drop the old one. Of course, i stop replication process before performing so. What are the kind of 'all replication information ' i can loose? So far, i can't see what it implies... My first step would to retrieve my primary dabase just as before it was instrumented by slony. So i can have a 'virgin dump' and restore it in any not replicated architecture. My second step would be to restart on entirely new replication with a new configuration by creating a new cluster and so on. Btw, on my opinion, bare-metal functions are not really industrial. I have to supply an integrated solution to a system operator. I would rather think of using perl commands just by switching through differents slon_tool.conf. Any comments on this appoach? thanks. 2008/2/27, "St=E9phane A. Schildknecht" < stephane.schildknecht at postgresqlfr.org>: > > lio bod a =E9crit : > > Hello world, > > > > I'm trying some procedures to modify a cluster : my need is to change > > the slave host (same base, same name, same model...) for a given master > > base master host. > > > > I had a look on slonik_uninstall_nodes command and i wonder why the doc > > (http://www.slony.info/documentation/adminscripts.html) tells it is 'a > > /VERY/ unsafe script' > > > > I'd like to know why it's supposed to be so unsafe? > > > > Any better practice? > > Any best practice? > > > > Thx, > > It is unsafe because it drops all replication information from all nodes > involved. You then lose your replication network in a single operation. Be > sure > it won't break your databases, but you will lose your replication. > > If your need is to add a new slave and drop the old one, you'd better have > a > look at bare-metal functions. > > something like "select _INSTANCE.uninstallnode()" on the old slave should > do > the work. You could also execute some drop node procedure on a "specific" > node, > which is not, what the perl script you invoked does. > > You could have a look at slonik_drop_node also. You just should verify > twice > you will execute that script against the right node :-) > > Regards, > > -- > St=E9phane SCHILDKNECHT > Pr=E9sident de PostgreSQLFr > T=E9l. 09 53 69 97 12 > http://www.postgresqlfr.org > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.slony.info/pipermail/slony1-general/attachments/20080227/= 6cc1d7d5/attachment-0001.htm
- Previous message: [Slony1-general] slonik_uninstall_nodes unsafe ?
- Next message: [Slony1-general] slonik_uninstall_nodes unsafe ?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list