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

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: shihao zhong <zhong950419(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 00:38:52
Message-ID: CAHGQGwFzy_DY5kPJk_B_DbOO68Th9G8HJ8euHvaXspzDftAmWg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Oct 16, 2026 at 4:34 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Thinking about that some more: why don't we just drop that test,
> along with the OUTPUT_CHARSET hacks, and confine ourselves to
> testing that (1) server_encoding equals client_encoding and
> (2) the translated string passes pg_encoding_verifymbstr?

Sounds reasonable to me.

Regards,

--
Fujii Masao

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Richard Guo 2026-10-16 00:57:43 Assert failure in create_lateral_join_info
Previous Message zengxx 2026-10-16 00:37:10 Re: [PATCH 0/2] Improve ndistinct estimates for flattened UNION ALL