Wed May 25 18:06:38 PDT 2011
- Previous message: [Slony1-general] CESTERROR remoteListenThread_1: timeout, (300 s) for event selection
- Next message: [Slony1-general] Support for EnterpriseDB version string?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 5/25/2011 5:39 PM, Ger Timmens wrote: > >> 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..... Makes no difference with respect to data integrity. Yes, it has to start over from scratch, but if you think there is a reason to kill your slon processes over and over again, you need to find out what exactly is wrong with either your network, you setup or yourself. Jan -- Anyone who trades liberty for security deserves neither liberty nor security. -- Benjamin Franklin
- Previous message: [Slony1-general] CESTERROR remoteListenThread_1: timeout, (300 s) for event selection
- Next message: [Slony1-general] Support for EnterpriseDB version string?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list