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
In-reply-to: <19581-e1b37ea2556ab74d@postgresql.org>
References: <19581-e1b37ea2556ab74d@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Sun, 26 Jul 2026 10:28:01 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <3803794.1785155554.1@sss.pgh.pa.us>
Content-Transfer-Encoding: 8bit
Date: Mon, 27 Jul 2026 08:32:34 -0400
Message-ID: <3803795.1785155554@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/3803795.1785155554%40sss.pgh.pa.us>
Precedence: bulk

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