From: Scott Ribe <scott_ribe@elevated-dev.com>
To: Don Seiler <don@seiler.us>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: Dupe Key Violations in Logical Replication with PKs in Place
Date: Tue, 14 Nov 2023 11:02:47 -0700
Message-ID: <DBF3465E-49A1-4F72-8795-3B98229EE04D@elevated-dev.com> (raw)
In-Reply-To: <CAHJZqBCEBRkhWgzzYp72o_D6qzGHz-3qN8+3JTet40M1k3Ek6Q@mail.gmail.com>
References: <CAHJZqBC_mnKAH_vwep8cmVqyLhnj1CN+tc36kt73VBXpK_Etsg@mail.gmail.com>
<CAHJZqBCEBRkhWgzzYp72o_D6qzGHz-3qN8+3JTet40M1k3Ek6Q@mail.gmail.com>
> 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 eager developer connected to the new/subscription DB and ran some inserts (also running them on the old/publication DB). The inserts 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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: scott_ribe@elevated-dev.com, don@seiler.us
Subject: Re: Dupe Key Violations in Logical Replication with PKs in Place
In-Reply-To: <DBF3465E-49A1-4F72-8795-3B98229EE04D@elevated-dev.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox