MIME-Version: 1.0
In-Reply-To: <19410-ae5020230ee6369b@postgresql.org>
References: <19410-ae5020230ee6369b@postgresql.org>
From: "David G. Johnston" <david.g.johnston@gmail.com>
Date: Sun, 15 Feb 2026 07:55:27 -0700
Message-ID: <CAKFQuwYYWsCTBBah+4OSLHOX7vjrS8o2K4DxhEzbuMbSp5KAqQ@mail.gmail.com>
Subject: BUG #19410: Cannot ser client_encoding
To: "615695028@qq.com" <615695028@qq.com>, 
	"pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="0000000000006d323f064ade073f"
Archived-At: <https://www.postgresql.org/message-id/CAKFQuwYYWsCTBBah%2B4OSLHOX7vjrS8o2K4DxhEzbuMbSp5KAqQ%40mail.gmail.com>
Precedence: bulk

--0000000000006d323f064ade073f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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 [=E7=89=88=E6=9C=AC 10.0.26200.7840=
]
> Description:
>
>
Everything you=E2=80=99ve shown worked as expected.

If you want to always use UTF-8 I=E2=80=99d suggest you figure out how to c=
onfigure
your client to do so.  psql will then just auto-detect whatever is actually
in use.  It doesn=E2=80=99t really make sense to use SET with client_encodi=
ng.

David J.

--0000000000006d323f064ade073f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Saturday, February 14, 2026, PG Bug reporting form &lt;<a href=3D"mailto=
:noreply@postgresql.org" target=3D"_blank">noreply@postgresql.org</a>&gt; w=
rote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex">The following bug has been logged o=
n the website:<br>
<br>
Bug reference:=C2=A0 =C2=A0 =C2=A0 19410<br>
Logged by:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Guest-615695028<br>
Email address:=C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:615695028@qq.com" targ=
et=3D"_blank">615695028@qq.com</a><br>
PostgreSQL version: 18.1<br>
Operating system:=C2=A0 =C2=A0Microsoft Windows [=E7=89=88=E6=9C=AC 10.0.26=
200.7840]<br>
Description:=C2=A0 =C2=A0 =C2=A0 =C2=A0 <br><br>
</blockquote><div><br></div><div>Everything you=E2=80=99ve shown worked as =
expected.</div><div><br></div><div>If you want to always use UTF-8 I=E2=80=
=99d suggest you figure out how to configure your client to do so. =C2=A0ps=
ql will then just auto-detect whatever is actually in use.=C2=A0 It doesn=
=E2=80=99t really make sense to use SET with client_encoding.</div><div><br=
></div><div>David J.</div><div><br></div>

--0000000000006d323f064ade073f--