On Thu, 29 Aug 2013, CS DBA wrote: > 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?
No don't drop the set. You will probably need to make the SUBSCRIBE_SET and ENABLE_SUBSCRIPTION events as being confirmed (even though they aren't). Then you can unsubscribe the set. Alternatively you could maybe manipulate the options on the SUBSCRIBE_SET event in sl_event so that it is a OMIT_COPY subscribe set. > > Thanks in advance > > > > _______________________________________________ > Slony1-general mailing list > [email protected] > http://lists.slony.info/mailman/listinfo/slony1-general > _______________________________________________ Slony1-general mailing list [email protected] http://lists.slony.info/mailman/listinfo/slony1-general
