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

From Tom Lane
Subject Re: BUG #19410: Cannot ser client_encoding
Date
Msg-id 911028.1771168233@sss.pgh.pa.us
Whole thread Raw
In response to BUG #19410: Cannot ser client_encoding  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-bugs
"David G. Johnston" <david.g.johnston@gmail.com> writes:
> On Saturday, February 14, 2026, PG Bug reporting form <
> noreply@postgresql.org> wrote:
>> [ SET doesn't persist across sessions ]

> Everything you’ve shown worked as expected.

Indeed.  I suggest reading

https://www.postgresql.org/docs/current/config-setting.html

which not only explains that the effects of SET are per-session,
but lists all the other ways to adjust a server setting.

> 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.

Yeah, that's an orthogonal issue: you really need client_encoding to
match whatever your terminal window is using, or non-ASCII characters
won't display correctly.  So letting psql deduce it from environment
is usually the right thing.

            regards, tom lane



pgsql-bugs by date:

Previous
From: "David G. Johnston"
Date:
Subject: BUG #19410: Cannot ser client_encoding
Next
From: Andrey Borodin
Date:
Subject: Re: 17.8 standby crashes during WAL replay from 17.5 primary: "could not access status of transaction"