[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-admin
Subject:    Re: Dupe Key Violations in Logical Replication with PKs in Place
From:       Don Seiler <don () seiler ! us>
Date:       2023-11-14 18:19:54
Message-ID: CAHJZqBBGOCdUeyz-38jHOJ0akxtsEispdPwpV77U_321+kpkqw () mail ! gmail ! com
[Download RAW message or body]

On Tue, Nov 14, 2023 at 12:02 PM Scott Ribe <scott_ribe@elevated-dev.com>
wrote:

> > 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.


I'm not sure why his connection didn't show up in my PG logs. I log
connects and disconnects but I don't see anything coming from our apps or
VPN network CIDRs, that would have been an important lead early on.


-- 
Don Seiler
www.seiler.us

[Attachment #3 (text/html)]

<div dir="ltr"><div dir="ltr">On Tue, Nov 14, 2023 at 12:02 PM Scott Ribe &lt;<a \
href="mailto:scott_ribe@elevated-dev.com">scott_ribe@elevated-dev.com</a>&gt; \
wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" \
style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex">&gt; On Nov 14, 2023, at 10:54 AM, Don Seiler \
&lt;<a href="mailto:don@seiler.us" target="_blank">don@seiler.us</a>&gt; wrote:<br> \
&gt; <br> &gt; 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.<br> <br>
So this would be about the 2 billionth or so episode in the DBA series titled \
&quot;shit happens&quot; ;-) Glad you figured it \
out.</blockquote><div><br></div><div>I&#39;m not sure why his connection didn&#39;t \
show up in my PG logs. I log connects and disconnects but I don&#39;t see anything \
coming from our apps or VPN network CIDRs, that would have been an important lead \
early on.</div></div><br clear="all"><div><br></div><span \
class="gmail_signature_prefix">-- </span><br><div dir="ltr" \
class="gmail_signature"><div dir="ltr"><div>Don Seiler<br><a \
href="http://www.seiler.us" target="_blank">www.seiler.us</a></div></div></div></div>



[prev in list] [next in list] [prev in thread] [next in thread]