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

Поиск
Список
Период
Сортировка
От Don Seiler
Тема Re: Dupe Key Violations in Logical Replication with PKs in Place
Дата
Msg-id CAHJZqBDRLBzZoOGOxMY5Cb+8cT++Fzm_6ZUu0NSv9sJi-sgKoA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Dupe Key Violations in Logical Replication with PKs in Place  (Ron <ronljohnsonjr@gmail.com>)
Ответы Re: Dupe Key Violations in Logical Replication with PKs in Place  (Scott Ribe <scott_ribe@elevated-dev.com>)
Список pgsql-admin
Дерево обсуждения
On Tue, Nov 14, 2023 at 10:04 AM Ron <ronljohnsonjr@gmail.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

В списке pgsql-admin по дате отправления:

Предыдущее
От: Scott Ribe
Дата:
Сообщение: Re: Dupe Key Violations in Logical Replication with PKs in Place
Следующее
От: Scott Ribe
Дата:
Сообщение: Re: Dupe Key Violations in Logical Replication with PKs in Place