From: Tom Lane <tgl@sss.pgh.pa.us>
To: Koichi Suzuki <koichi.dbms@gmail.com>
cc: Tatsuo Ishii <ishii@postgresql.org>, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18735: Specific multibyte character in psql file path
 command parameter for Windows
In-reply-to: 
 <CABEZHFurokPoY+Vs0zhSf7J5ahZV1p7naOPiH5_3C-ubPdDWgA@mail.gmail.com>
References: <18735-4acdb3998bb9f2b1@postgresql.org>
 <2572359.1733424649@sss.pgh.pa.us>
 <20241206.142130.1661155698933375612.ishii@postgresql.org>
 <CABEZHFurokPoY+Vs0zhSf7J5ahZV1p7naOPiH5_3C-ubPdDWgA@mail.gmail.com>
Comments: In-reply-to Koichi Suzuki <koichi.dbms@gmail.com>
	message dated "Fri, 06 Dec 2024 14:26:34 +0900"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2751824.1733464455.1@sss.pgh.pa.us>
Date: Fri, 06 Dec 2024 00:54:15 -0500
Message-ID: <2751825.1733464455@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2751825.1733464455%40sss.pgh.pa.us>
Precedence: bulk

Koichi Suzuki <koichi.dbms@gmail.com> writes:
> I'm not sure if we can fix src/fe_utils/psqlscan.l and/or
> src/bin/psql/psqlscanslash.l for this.  Needs some more investigqation.

I don't believe the theory that the fault lies there.  If the flex
rules were taking the backslash-embedded-in-a-shift-JIS-character
as a backslash, they would think it is the start of a new backslash
command, with the result being that the filename argument gets
truncated there.  That doesn't match the reported symptoms: we
see more of the filename than that echoed back in the error message.
So I think the filename is getting through that part just fine,
and then we're messing it up in canonicalize_path or adjacent
processing.

			regards, tom lane