Tue Feb 19 08:24:10 PST 2008
- Previous message: [Slony1-general] proper procedure for re-starting slony after replication slave reboots
- Next message: [Slony1-general] proper procedure for re-starting slony after replication slave reboots
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I'm finding some records that exist in the master that do not exist in the slave. I'm also finding records that exist in the slave, that don't exist in the master. I simply don't understand how this is possible. I'm assuming the first issue is a record that was never populated to the slave, whereas the second would be a delete that was never populated to the slave. Further, these examples are 4 days old, so it's not the case that the slave just hasn't caught up. -- Until later, Geoffrey Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. - Benjamin Franklin
- Previous message: [Slony1-general] proper procedure for re-starting slony after replication slave reboots
- Next message: [Slony1-general] proper procedure for re-starting slony after replication slave reboots
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list