> On May 22, 2020, at 5:08 PM, Jeff Ross <[email protected]> wrote: > > Hi all, > > We're getting a lot of errors in syncs after upgrading to 5.6 in a master > <--> master setup. The left master is the dominant side, supposedly the > right side is not yet trying to insert/update back to the left side.
Do you happen to have a record of how you upgraded this cluster? Just installing, then `bucardo upgrade`? > From the logs it almost appears that we are getting both of these: > > a) inserts/updates from left are applied to right, then right tries to > re-apply them back to left. This results in a pkey_conflict on the left side. It kind of sounds like the data is being copied with the wrong session_replication_role, meaning that the delta rows are being captured as if you were in srr “origin" mode, instead of “replica”. Can you look if there are any errors in the postgres logs related to “session_replication_role”? Can we verify the “bucardo” user is being used to connect, and that it is set to superuser on all nodes in the cluster? Are nodes involved self-hosted, or something else like RDS? > b) sequences now appear to be replicated? This is a long shot but > before upgrading to 5.6 I had set left side sequences to increment by 2, > starting with odd and right side sequences to increment by 2 stating with > even. Now. left side gives even numbers for nextval(seq) and it should not. > I've tried to reset this multiple times with no success--but it *had* been > working prior to upgrade to 5.6. Sequences *can* be replicated, but only if you explicitly ask for it; it shouldn’t be coming as part of the normal upgrade. If you are using a multi-master setup, you definitely should *not* be replicating sequences as a matter of course. If it *did* get sync’d though, this would be the behavior I’d expect though, since the current value would get set, leaving the increment the same. -- David Christensen Senior Software and Database Engineer End Point Corporation [email protected] 785-727-1171
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ Bucardo-general mailing list [email protected] https://bucardo.org/mailman/listinfo/bucardo-general
