Re: inserts bypass encoding conversion

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "James Pang (chaolpan)" <chaolpan(at)cisco(dot)com>
Cc: "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: inserts bypass encoding conversion
Date: 2023-08-16 14:02:55
Message-ID: 1320633.1692194575@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

"James Pang (chaolpan)" <chaolpan(at)cisco(dot)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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message James Pang (chaolpan) 2023-08-17 01:08:21 RE: inserts bypass encoding conversion
Previous Message James Pang (chaolpan) 2023-08-16 07:06:51 inserts bypass encoding conversion