Re: Bug in jsonb_path_exists (maybe _match) one-element scalar/variable jsonpath handling - Mailing list pgsql-bugs

From Alexander Korotkov
Subject Re: Bug in jsonb_path_exists (maybe _match) one-element scalar/variable jsonpath handling
Date
Msg-id CAPpHfdtweZwYrf0uTXRWiFRW6_L0eAWMBQFH9fM-SCbwqikJUA@mail.gmail.com
Whole thread Raw
In response to Re: Bug in jsonb_path_exists (maybe _match) one-element scalar/variable jsonpath handling  (Alexander Korotkov <aekorotkov@gmail.com>)
Responses Re: Bug in jsonb_path_exists (maybe _match) one-element scalar/variable jsonpath handling
List pgsql-bugs
On Fri, Dec 2, 2022 at 3:18 PM Alexander Korotkov <aekorotkov@gmail.com> wrote:
> Draft patch fixing the issue is attached.  Let me know what you think
> about this.

Revised patch is attached, wrong pfree() is fixed.  I was intended to
backpatch it.  But the behavior change makes me uneasy.

select * from jsonb_path_query('{"a": 10}', '$ ? (@.a < $value)');

Currently, this query generates an error because of missing "value"
variable.  The patch suppress this error.  I'm not sure this error
should be suppressed.  Especially, I'm sure this should be
backpatched.

Should we fix only existence checking behaviour and let other cases
throw an error?  Thoughts?

------
Regards,
Alexander Korotkov

Attachment

pgsql-bugs by date:

Previous
From: Thomas Munro
Date:
Subject: Re: BUG #17705: Segmentation fault in BufFileLoadBuffer
Next
From: Jeff Davis
Date:
Subject: Re: CREATE COLLATION without LOCALE throws error in v15