On Wed, Dec 1, 2010 at 9:33 AM, Mark Steben <[email protected]> wrote: > Should I: > 1. issue a ./slon_start and allow slony to catch-up two weeks worth of > updates > Or > 2. Punt, start from scratch, redefine everything and rerun the 16 hour > subscription process? >
It all depends on the rate of change in your database. Do you do a lot of insert/update/deletes to the DB? Take a look at the number of rows in the sl_log_1 and sl_log_2 tables in your replication schema on the master. If the number is very very high, say in the tens or hundreds of milliions, then perhaps restarting from scratch may be helpful. If it is in the low tens of millions, I'd venture to day you could recover by just restarting slony. One optimization may be to drop all indexes (except the PK index) on the replica until it is caught up. This will reduce the I/O it needs to apply the changes. _______________________________________________ Slony1-general mailing list [email protected] http://lists.slony.info/mailman/listinfo/slony1-general
