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:12:25 |
Message-ID: | CAHJZqBD3z8eFG=Hit2NGcvAr6Gvv_y2i42BYDxi4wpONJ0D-zw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Tue, Nov 14, 2023 at 10:10 AM Scott Ribe <scott_ribe(at)elevated-dev(dot)com>
wrote:
> > On Nov 14, 2023, at 9: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.
>
> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Don Seiler | 2023-11-14 16:14:02 | Re: Dupe Key Violations in Logical Replication with PKs in Place |
Previous Message | Scott Ribe | 2023-11-14 16:12:22 | Re: Dupe Key Violations in Logical Replication with PKs in Place |