CS DBA cs_dba at consistentstate.com
Thu Aug 29 11:09:30 PDT 2013
All;

I have a 35GB table that we are trying to add to a replication set.
The connection keeps timing out, we've changed the system keep alive to 
every 30minutes



If it fails again we're going to try a no-sync approach.

I want to do a normal run once more which includes:
- create set (create set 2)
- set add table (only for the big table)
- subscribe set (with OMIT COPY = false)

If this fails again, then I want to do this:
- copy the table myself
- create set (create set 2)
- set add table (only for the big table)
- subscribe set (with OMIT COPY = true)

So here's my question:
If the above normal run fails again, how can I cleanly revert / remove 
the now failed replication set 2 completely from slony so I can then set 
it up again using "OMIT COPY = true" in the subscribe set command?

will a drop set work with it in this state?

Thanks in advance





More information about the Slony1-general mailing list