Re: Dupe Key Violations in Logical Replication with PKs in Place

From: Don Seiler <don(at)seiler(dot)us>
To: Scott Ribe <scott_ribe(at)elevated-dev(dot)com>
Cc: Ron <ronljohnsonjr(at)gmail(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: Dupe Key Violations in Logical Replication with PKs in Place
Date: 2023-11-14 16:14:02
Message-ID: CAHJZqBAatQLaHpZOBRX_yP5JboER0O9bs6OSORKegX1aoAgmgQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Tue, Nov 14, 2023 at 10:12 AM Scott Ribe <scott_ribe(at)elevated-dev(dot)com>
wrote:

> > On Nov 14, 2023, at 9:10 AM, Don Seiler <don(at)seiler(dot)us> wrote:
> >
> > The data is UUID strings (typical alphanumeric characters and hyphens)
> stored in varchar(36) fields,
>
> Well, there you go: digits and dashes, the sort order changed.

But this is a logical replica. That problem and its re-indexing solution
should only apply to physical replicas.

--
Don Seiler
www.seiler.us

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Scott Ribe 2023-11-14 16:15:03 Re: Dupe Key Violations in Logical Replication with PKs in Place
Previous Message Don Seiler 2023-11-14 16:12:25 Re: Dupe Key Violations in Logical Replication with PKs in Place