Re: encoding problem while inictial copy in logical replication

On Tue, Sep 16, 2025 at 12:44 PM Adrian Klaver
<adrian.klaver@aklaver.com> wrote:
>
> On 9/16/25 04:01, Jaime Casanova wrote:
> > Hi,
> >
> > I have a database with UTF8 encoding. This database seems to be
> > receiving data in WIN1252 encoding from some client.
> >
[...]
> >
> > Some time ago I tried to create a logical replication, for a speed up
> > I used I created a physical replica and converted it in a logical one
> > and it works fine.
> > But the I tried to add a new table to the replica, so I added it to
> > the publication and when I "ALTER SUBSCRIPTION .... REFRESH
> > PUBLICATION" got this error.
> >
> > 2025-09-16 08:20:24.971 UTC [1535715] LOG:  logical replication table
> > synchronization worker for subscription "sub1", table "new_table" has
> > started
> > 2025-09-16 09:20:23.037 UTC [1535715] ERROR:  character with byte
> > sequence 0x8d in encoding "WIN1252" has no equivalent in encoding
> > "UTF8"
> > 2025-09-16 09:20:23.037 UTC [1535715] CONTEXT:  COPY new_table, line 2489
> > 2025-09-16 09:20:23.041 UTC [1463234] LOG:  background worker "logical
> > replication worker" (PID 1535715) exited with exit code 1
> >
[...]
> >
> > Any idea? Currently my process is to manually copy the data.
>
> Read this?:
>
> https://www.i18nqa.com/debug/bug-double-conversion.html
> https://www.i18nqa.com/debug/utf8-debug.html
>
> Bottom line 0x8d is unassigned in WIN1252 and there is no UTF8
> equivalent for it and four other code points.
>
> The solution would seem to be determining what is using this code point
> and stopping it's use if possible.
>

But then, why pg_dump works if it's also using COPY?

--
Jaime Casanova
SYSTEMGUARDS
Director de servicios profesionales