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

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-21 15:17:44
Message-ID: CAGRkXqSrf0C+NZTA0EOY=m7w2YYgRWK3VB8c6V4xv+dv7yKnXg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Works for me, pushed.

Thanks for committing 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.

I had put that into my queue and planned to start work on that
after 19 GA.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Burd 2026-10-21 15:25:06 Re: Expanding HOT updates for expression and partial indexes
Previous Message Rui Zhao 2026-10-21 14:56:06 Re: Allow table AMs to define their own reloptions