| From: | shihao zhong <zhong950419(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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-17 03:52:34 |
| Message-ID: | CAGRkXqR2P+Ghmo=swEUrMqebrLcLiv66Hq2suM-ofnzfDZhaeg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Tom,
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> 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.
Cool. v9 does what you suggested, equal encodings plus
pg_encoding_verifymbstr.
Fixing the WIN1252 validator would be master only. I want to focus
on 19 stability until GA, and I can look at it after that.
Thanks,
Shihao
| Attachment | Content-Type | Size |
|---|---|---|
| v9-0001-psql-Fall-back-to-English-for-unsafe-hidden-query.patch | application/octet-stream | 2.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Manu | 2026-10-17 04:00:26 | Re: [PG19] Wrong results from NOT NULL-based expression simplification |
| Previous Message | shihao zhong | 2026-10-17 03:41:20 | Re: [PG19] Three bugs with a CHECK constraint that only the child enforces |