From: Tatsuo Ishii <ishii@postgresql.org>
To: tgl@sss.pgh.pa.us
Cc: koichi.dbms@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows
Date: Sun, 08 Dec 2024 20:01:18 +0900 (JST)
Message-ID: <20241208.200118.410748201504579781.ishii@postgresql.org> (raw)
In-Reply-To: <2850994.1733516077@sss.pgh.pa.us>
References: <20241206.154248.1191531539866262856.ishii@postgresql.org>
<2840430.1733510664@sss.pgh.pa.us>
<2850994.1733516077@sss.pgh.pa.us>
> Another way, given that we only really need this to work for
> SJIS, is to hard-wire the logic into path.c --- it's not like
> pg_sjis_mblen is either long or likely to change. That's
> ugly but would be a lot less invasive and safer to back-patch.
>
> I'm leaning a bit to the second way, mainly because of the
> extern-relocation annoyance.
+1. I believe the logic of detecting byte length in Shift-JIS will not
be changed.
Best reagards,
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: ishii@postgresql.org, tgl@sss.pgh.pa.us, koichi.dbms@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows
In-Reply-To: <20241208.200118.410748201504579781.ishii@postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox