From: Tom Lane <tgl@sss.pgh.pa.us>
To: Shahar Belizon <shahar@cybear.co>
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17660: JSONPATH issue using like_regex followed by the &&
 operator
In-reply-to: 
 <CAOaN=Vib3SuyPUcXNMUQb6NtftosEepPz6Yi6dy77Q6DmVs3dw@mail.gmail.com>
References: <17660-3fe48447b080d5b6@postgresql.org>
 <3367660.1666446526@sss.pgh.pa.us>
 <CAOaN=Vib3SuyPUcXNMUQb6NtftosEepPz6Yi6dy77Q6DmVs3dw@mail.gmail.com>
Comments: In-reply-to Shahar Belizon <shahar@cybear.co>
	message dated "Sun, 23 Oct 2022 10:56:14 +0300"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3541493.1666539105.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Sun, 23 Oct 2022 11:31:45 -0400
Message-ID: <3541494.1666539105@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/3541494.1666539105%40sss.pgh.pa.us>
Precedence: bulk

Shahar Belizon <shahar@cybear.co> writes:
> Well, I see what you are saying, but still, when checking the result of =
*SELECT
> 'a' ~ '\$$'* I'm getting a *FALSE, *so I expect the JSONPATH parser to w=
ork
> the same way.

I don't think you did grasp the point.  There's an additional level of
literal-parsing and backslash-stripping involved in the jsonpath case,
because the jsonpath path string contains an embedded string literal,
which has to have some kind of escaping behavior.  Otherwise, how could
you search for a pattern that includes a double-quote?

The underlying regex behavior is the same either way; it's the surface
syntax that's different because of the extra parsing layer.

			regards, tom lane