BUG #19410: Cannot ser client_encoding

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: 615695028(at)qq(dot)com
Subject: BUG #19410: Cannot ser client_encoding
Date: 2026-02-15 01:53:30
Message-ID: 19410-ae5020230ee6369b@postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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:

PS C:\> psql -U postgres
Password for user postgres:

psql (18.1)
Type "help" for help.

postgres=# SHOW client_encoding;
client_encoding
-----------------
GBK
(1 row)

postgres=# SET client_encoding='UTF8';
SET
postgres=# SHOW client_encoding;
client_encoding
-----------------
UTF8
(1 row)

postgres=# \q
PS C:\> psql -U postgres
Password for user postgres:

psql (18.1)
Type "help" for help.

postgres=# SHOW client_encoding;
client_encoding
-----------------
GBK
(1 row)

postgres=#

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tender Wang 2026-02-15 08:48:04 Re: BUG #19405: Assertion in eval_windowaggregates() fails due to integer overflow
Previous Message Noah Misch 2026-02-14 22:46:21 Re: BUG #19406: substring(text) fails on valid UTF-8 toasted value in PostgreSQL 15.16