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 CAHJZqBD3z8eFG=Hit2NGcvAr6Gvv_y2i42BYDxi4wpONJ0D-zw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Dupe Key Violations in Logical Replication with PKs in Place  (Scott Ribe <scott_ribe@elevated-dev.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:10 AM Scott Ribe <scott_ribe@elevated-dev.com> wrote:
> On Nov 14, 2023, at 9: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.

Problems with the locale updates are not limited to non-ASCII characters, sorting rules involving "-" changed, for instance. When you make that OS upgrade, you really, really, need to reindex all text types.

That's precisely why I'm using logical replication for this migration. The indexes are new on the subscriber server. Re-indexing should only be necessary if I were to do physical replication/restore onto a 22.04 server, no?

Don.

--
Don Seiler
www.seiler.us

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

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