BUG #19410: Cannot ser client_encoding - Mailing list pgsql-bugs

From David G. Johnston
Subject BUG #19410: Cannot ser client_encoding
Date
Msg-id CAKFQuwYYWsCTBBah+4OSLHOX7vjrS8o2K4DxhEzbuMbSp5KAqQ@mail.gmail.com
Whole thread Raw
In response to BUG #19410: Cannot ser client_encoding  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #19410: Cannot ser client_encoding
List pgsql-bugs
On Saturday, February 14, 2026, PG Bug reporting form <noreply@postgresql.org> wrote:
The following bug has been logged on the website:

Bug reference:      19410
Logged by:          Guest-615695028
Email address:      615695028@qq.com
PostgreSQL version: 18.1
Operating system:   Microsoft Windows [版本 10.0.26200.7840]
Description:       


Everything you’ve shown worked as expected.

If you want to always use UTF-8 I’d suggest you figure out how to configure your client to do so.  psql will then just auto-detect whatever is actually in use.  It doesn’t really make sense to use SET with client_encoding.

David J.

pgsql-bugs by date:

Previous
From: Tender Wang
Date:
Subject: Re: BUG #19405: Assertion in eval_windowaggregates() fails due to integer overflow
Next
From: Tom Lane
Date:
Subject: Re: BUG #19410: Cannot ser client_encoding