On Fri, 2008-10-10 at 10:58 +0200, "Stéphane A. Schildknecht" wrote:
> > My Slony Master daemon died and for some reason, the slave died along
> > with it and that was over 4 days ago.
> > 
> > I read back the archives and found that it really _isn't_ a problem (if
> > my hardware can handle it) [which I know it can't really]
> > 

> > So, the question now is, is there anything I can do to break up the sync
> > into a few more, more manageable qty? I'm not sure if it can sync up
> > 9million rows in 1 BIG SYNC.
> > 
> > Is there any way I can eg: sync it manually? meaning, remove the
> > triggers from the slave and then copy the data over and then restart
> > slony?
> > 
> 
> 33 sync events late is not really a big deal. As both replication daemons were
> stopped, there may not be any Sync produced since then.
> 
> What's more annoying is that you may have add/updated 9 millions rows in one
> single transaction. That could lead in a real long time synchronisation. But,
> Slony can really well handle it. All you have to do is restart both daemons and
> wait...


I'm waiting now.... Not sure how long it will take for the entire
process to finish.

If not mistaken the entire SYNC is done in a transaction, that means 1
BIG lock??