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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Don Seiler <don@xxxxxxxxx>
Subject: Re: Dupe Key Violations in Logical Replication with PKs in Place
From: Scott Ribe <scott_ribe@xxxxxxxxxxxxxxxx>
Date: Tue, 14 Nov 2023 09:12:22 -0700
Cc: Ron <ronljohnsonjr@xxxxxxxxx>, pgsql-admin@xxxxxxxxxxxxxxxxxxxx
In-reply-to: <CAHJZqBDRLBzZoOGOxMY5Cb+8cT++Fzm_6ZUu0NSv9sJi-sgKoA@mail.gmail.com>
References: <CAHJZqBC_mnKAH_vwep8cmVqyLhnj1CN+tc36kt73VBXpK_Etsg@mail.gmail.com> <401c360a-ff4c-4904-8608-22b24b2179d6@gmail.com> <CAHJZqBDRLBzZoOGOxMY5Cb+8cT++Fzm_6ZUu0NSv9sJi-sgKoA@mail.gmail.com>

> On Nov 14, 2023, at 9:10 AM, Don Seiler <don@xxxxxxxxx> 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.

Follow-Ups:
- Re: Dupe Key Violations in Logical Replication with PKs in Place
  - From: Don Seiler

References:
- Dupe Key Violations in Logical Replication with PKs in Place
  - From: Don Seiler
- Re: Dupe Key Violations in Logical Replication with PKs in Place
  - From: Ron
- Re: Dupe Key Violations in Logical Replication with PKs in Place
  - From: Don Seiler

Prev by Date: Re: Dupe Key Violations in Logical Replication with PKs in Place
Next by Date: Re: Dupe Key Violations in Logical Replication with PKs in Place
Previous by thread: Re: Dupe Key Violations in Logical Replication with PKs in Place
Next by thread: Re: Dupe Key Violations in Logical Replication with PKs in Place
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Home] [Postgresql General] [Postgresql Performance] [Postgresql PHP] [Postgresql Jobs] [PHP Users] [PHP Databases] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Databases] [Yosemite Forum]

Powered by Linux