Hi, I've recently come across a situation where slony logshipping files were being written incorrectly. Normally, the files are written in this order: - Begin transaction - Set archive tracking index - INSERTs/UPDATEs/DELETEs - Set sequences - Vacuum - Commit
I noticed that in my particular instance, the files were being written as such: - Begin transaction - Set archive tracking index - Vacuum - Commit - INSERTs/UPDATEs/DELETEs - Set sequences Obviously, this sounds pretty dangerous, and I actually encountered the situation where my logship destination got corrupted, and needed to rebuild that node. Would anyone have any insight into why this happens? Using 2.0.6 on CentOS, with Postgres 8.4.5 Thanks! --Richard
_______________________________________________ Slony1-general mailing list [email protected] http://lists.slony.info/mailman/listinfo/slony1-general
