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-21 14:36:47
Message-ID: 2200339.1792593407@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:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>> Hmm, I wonder why we can't use this same logic on Windows?

> I am not a windows expert and agree "guessing is harder on Windows is
> no longer a factor.“
> v10 drops the WIN32 exclusion.

Works for me, pushed.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2026-10-21 14:43:13 Re: [PATCH] Report no unpinned buffers as insufficient resources
Previous Message Ayush Tiwari 2026-10-21 14:21:01 Re: [DEPARSE] EXPLAIN prints another ModifyTable's RETURNING aliases in a SubPlan