Re: [PG19] psql backslash commands fail with translated messages and a non UTF-8 client encoding

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: shihao zhong <zhong950419(at)gmail(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Greg Sabino Mullane <htamfids(at)gmail(dot)com>
Subject: Re: [PG19] psql backslash commands fail with translated messages and a non UTF-8 client encoding
Date: 2026-10-16 05:11:36
Message-ID: 2979839.1792127496@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

shihao zhong <zhong950419(at)gmail(dot)com> writes:
> Thanks for pushing the infrastructure. v8 does what you suggest,
> with one more restriction: it translates only when both encodings are
> UTF8.

Uh ... what?

> WIN1252 accepts byte 0x81 but has no character for it.

Surely your solution is shooting the messenger. If WIN1252 behaves
that way, we need to fix its validator, not insert arbitrary
restrictions elsewhere to work around the inadequate validation.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Previous Message David Rowley 2026-10-16 05:03:57 Re: Weird usages of sentinel_ok()