Fri Jul 18 11:14:29 PDT 2008
- Previous message: [Slony1-general] Node not found in the runtime configuration
- Next message: [Slony1-general] Best way to check if a table is in replication?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Imagine I have two databases which are correctly replicated - maybe I did dump&restore, maybe some other replication technique (*). Imagine I can assure myself that those are equal. Does there exist any method to fool slony so it skips initial DELETE & COPY TABLE, but just starts replicating new data instead? (*) Well, to say the true in the very scenario I survived recently, I had Slony replication which went stuck after a few add node, drop node, move set operations (I was just another victim of neverending "ACCEPT_SET - MOVE_SET or FAILOVER_SET not received yet - sleep" case). But if I read list archives correctly this is to be corrected in 1.2.14 (I use 1.2.13 which ubuntu installs). -- ---------------------------------------------------------------------- | Marcin Kasperski | Software is not released, | http://mekk.waw.pl | it is allowed to escape. | | ----------------------------------------------------------------------
- Previous message: [Slony1-general] Node not found in the runtime configuration
- Next message: [Slony1-general] Best way to check if a table is in replication?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list