From: Tom Lane <tgl@sss.pgh.pa.us>
To: James Pang (chaolpan) <chaolpan@cisco.com>
Cc: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
Subject: Re: inserts bypass encoding conversion
Date: Wed, 16 Aug 2023 10:02:55 -0400
Message-ID: <1320633.1692194575@sss.pgh.pa.us> (raw)
In-Reply-To: <PH0PR11MB5191EB32087DE307374EB2C4D615A@PH0PR11MB5191.namprd11.prod.outlook.com>
References: <PH0PR11MB5191EB32087DE307374EB2C4D615A@PH0PR11MB5191.namprd11.prod.outlook.com>
"James Pang (chaolpan)" <chaolpan@cisco.com> writes:
> With client_encoding=UTF8 and server_encoding=LATIN1, looks like insert into value with chr(codepoint) bypass encoding conversion , is it expected ? test as below ,
The chr() function is a server-side operation that has nothing to do
with the client encoding.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, chaolpan@cisco.com, pgsql-admin@lists.postgresql.org
Subject: Re: inserts bypass encoding conversion
In-Reply-To: <1320633.1692194575@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox