On 11/14/2006 3:07 PM, Julian Scarfe wrote: >> As for the duplicate key errors, can it be that you have sequences >> replicated and that those actually are in a different set than the table >> they belong to? > > No, I don't think so. But what's weird is that the INSERTs that are failing > on node 3 are all rows that are timestamped with the original insertion time > on node 1 and they are from between 10 and 20 minutes before the switchover. > So in some sense they are "old" events and I presume that they have already > been processed on node 3 because the content of node 3 remains a perfect > replica of nodes 1 and 2 (at least after slon restarts 10 times).
How exactly is your setup? Assuming node 1 is the old origin and node 2 the new origin, is node 3 cascaded from 2 or is it a direct subscriber from 1 as well? Jan -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #================================================== [EMAIL PROTECTED] # _______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
