| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "615695028(at)qq(dot)com" <615695028(at)qq(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | BUG #19410: Cannot ser client_encoding |
| Date: | 2026-02-15 14:55:27 |
| Message-ID: | CAKFQuwYYWsCTBBah+4OSLHOX7vjrS8o2K4DxhEzbuMbSp5KAqQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Saturday, February 14, 2026, PG Bug reporting form <
noreply(at)postgresql(dot)org> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 19410
> Logged by: Guest-615695028
> Email address: 615695028(at)qq(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2026-02-15 15:10:33 | Re: BUG #19410: Cannot ser client_encoding |
| Previous Message | Tender Wang | 2026-02-15 08:48:04 | Re: BUG #19405: Assertion in eval_windowaggregates() fails due to integer overflow |