From: Tom Lane <tgl@sss.pgh.pa.us>
To: Koichi Suzuki <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: Fri, 06 Dec 2024 00:05:00 -0500
Message-ID: <2744315.1733461500@sss.pgh.pa.us> (raw)
In-Reply-To: <CABEZHFuqEkpoEf91VkK8A2Gbmcp0ELhYAYz_5J0SRCim=KJwWA@mail.gmail.com>
References: <18735-4acdb3998bb9f2b1@postgresql.org>
<2572359.1733424649@sss.pgh.pa.us>
<CABEZHFuqEkpoEf91VkK8A2Gbmcp0ELhYAYz_5J0SRCim=KJwWA@mail.gmail.com>
Koichi Suzuki <koichi.dbms@gmail.com> writes:
> Lexical analysis of backshash commands in psql is handled
> by psqlscanslash.l and this module scans iput byte-by-byte, not
> character-by-character. I'm afraid that the cause of the bug is in
> this part.. Is there any way to make this flex syntax local-dependent?
I think you're mistaken: see the "safe_encoding" hackery in
psqlscan.l (which does also operate for the rules in psqlscanslash.l).
Now it could be that psqlscan.l has been misinformed about the
encoding that's in use, but that wouldn't be its fault.
regards, tom lane
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: 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: <2744315.1733461500@sss.pgh.pa.us>
* 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