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

From: Don Seiler <don(at)seiler(dot)us>
To: Ron <ronljohnsonjr(at)gmail(dot)com>
Cc: 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:10:05
Message-ID: CAHJZqBDRLBzZoOGOxMY5Cb+8cT++Fzm_6ZUu0NSv9sJi-sgKoA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Tue, Nov 14, 2023 at 10:04 AM Ron <ronljohnsonjr(at)gmail(dot)com> wrote:

>
> What data type(s) in those columns, and what locale on each server? Maybe
> the change from 18.04/12 to 22.04/15 has caused some weirdness with
> "foreign" characters.
>

The data is UUID strings (typical alphanumeric characters and hyphens)
stored in varchar(36) fields, a few booleans and an int. Nothing
exotic/weird/foreign to a US-based observer. The DBs are both using UTF8,
the LANG env is set to "en_US.utf8" in both sides as well. The primary key
fields are those varchar fields storing UUID strings, not using a sequence
or any type of auto-incrementing value.

Don.

--
Don Seiler
www.seiler.us

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Scott Ribe 2023-11-14 16:12:22 Re: Dupe Key Violations in Logical Replication with PKs in Place
Previous Message Scott Ribe 2023-11-14 16:09:28 Re: Dupe Key Violations in Logical Replication with PKs in Place