Fri Jan 3 10:44:22 PST 2014
- Previous message: [Slony1-general] testing slony state in slony 2.0.4
- Next message: [Slony1-general] 6 hours to replicate single table, 12 hours to replicate DB
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Am 2014-01-02 17:49, schrieb Scott Marlowe: > On Thu, Jan 2, 2014 at 9:36 AM, Matthias Leopold <matthias at aic.at> wrote: >> hi, >> >> i successfully used test_slony_state-dbi.pl with slony 1.2. >> >> after our cluster got rebuilt with slony 2.0 (which wasn't done by >> me...) replication seems to work but the test script keeps complaining >> about events and confirmations not propagating for all of the nodes. as >> i said replication seems to work, logs are fine, dropping and readding a >> node doesn't make a difference, sl_log_1/sl_log_2 look unsuspicious. >> slony 2.0.4 is from debian 6. >> >> can you tell me where to look next? > > Into updating? 2.0.4 had a fair few bugs, and 2.0.7 is the latest 2.0 > release. I tried 2.0.4 a ways back and had some issues with it much > like what you're experiencing that 2.0.5 fixed. > thx, updating (rolling my own 2.0.7 debian package) indeed solved the issue. i'm still putting too much trust in distribution packages after all those years... matthias
- Previous message: [Slony1-general] testing slony state in slony 2.0.4
- Next message: [Slony1-general] 6 hours to replicate single table, 12 hours to replicate DB
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list