From: Tom Lane <tgl@sss.pgh.pa.us>
To: redoute@tortenboxer.de
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19581: Non-UTF8-encoded text in log file
Date: Mon, 27 Jul 2026 08:32:34 -0400
Message-ID: <3803795.1785155554@sss.pgh.pa.us> (raw)
In-Reply-To: <19581-e1b37ea2556ab74d@postgresql.org>
References: <19581-e1b37ea2556ab74d@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> writes:
> Internal log messages (e.g. checkpoint messages) are written with CP1252
> bytes (0xFC for ΓΌ) instead of UTF-8.
I see no reason to think this is a bug. It's documented that sessions
write to the log in whatever their prevailing encoding is. I think
the checkpointer isn't attached to any particular database, so instead
of adopting some database's encoding it would use whatever is implied
by the postmaster's locale environment (LANG, LC_ALL, LC_CTYPE, or
related environment variables). So would the postmaster itself, for
that matter.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, redoute@tortenboxer.de, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19581: Non-UTF8-encoded text in log file
In-Reply-To: <3803795.1785155554@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox