Postgres Pro
Downloads
Home   >   mailing lists

Re: Dupe Key Violations in Logical Replication with PKs in Place - Mailing list pgsql-admin

From Scott Ribe
Subject Re: Dupe Key Violations in Logical Replication with PKs in Place
Date
Msg-id DBF3465E-49A1-4F72-8795-3B98229EE04D@elevated-dev.com
Whole thread Raw
In response to Re: Dupe Key Violations in Logical Replication with PKs in Place  (Don Seiler <don@seiler.us>)
Responses Re: Dupe Key Violations in Logical Replication with PKs in Place
List pgsql-admin
Tree view 
> On Nov 14, 2023, at 10:54 AM, Don Seiler <don@seiler.us> wrote:
>
> Well this looks to be human error/cause after all. I made the mistake of announcing the upcoming migration and one
eagerdeveloper connected to the new/subscription DB and ran some inserts (also running them on the old/publication DB).
Theinserts were all in one transaction, and look to be responsible for all 3 of duplicate key incidents. 

So this would be about the 2 billionth or so episode in the DBA series titled "shit happens" ;-) Glad you figured it
out.

pgsql-admin by date:

Previous
From: Don Seiler
Date:
Subject: Re: Dupe Key Violations in Logical Replication with PKs in Place
Next
From: Don Seiler
Date:
Subject: Re: Dupe Key Violations in Logical Replication with PKs in Place