Wed May 25 14:39:13 PDT 2011
- Previous message: [Slony1-general] Slony 2.0.7 rc1 released
- Next message: [Slony1-general] CESTERROR remoteListenThread_1: timeout, (300 s) for event selection
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> In the early days, the solution to a whole lot of problems was "kill > off the slons and let them restart," and that wouldn't ever corrupt > data. Correct, however not during a copy set, if I'm right. In that case a restart of the slon process would start copying the set from the start again..... Not a big deal for smaller sets, but if you're replicating multiple Gigabytes..... Ger
- Previous message: [Slony1-general] Slony 2.0.7 rc1 released
- Next message: [Slony1-general] CESTERROR remoteListenThread_1: timeout, (300 s) for event selection
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list