Re: libpq and mysterious "invalid byte sequence for encoding UTF8".

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jiří Pavlovský <jiri(at)pavlovsky(dot)eu>
Cc: rob stone <floriparob(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: libpq and mysterious "invalid byte sequence for encoding UTF8".
Date: 2021-02-02 15:28:32
Message-ID: 3715069.1612279712@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

=?UTF-8?B?SmnFmcOtIFBhdmxvdnNrw70=?= <jiri(at)pavlovsky(dot)eu> writes:
> Client and server encoding is UTF8. Locales are set to C.UTF8.

If lc_messages is C then no translation of error strings would happen,
so that theory goes out the window. Oh well.

Perhaps you could attach gdb to the backend and get a stack trace
from the call to errfinish?

https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2021-02-02 16:32:22 Re: permission denied for large object 200936761
Previous Message Peter J. Holzer 2021-02-02 15:14:33 Re: ransomware