Horton

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

Alexander Korotkov <aekorotkov@gmail.com>

View thread View on postgr.es
From: Alexander Korotkov <aekorotkov@gmail.com>
To: "David G. Johnston" <david.g.johnston@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL Bug List <pgsql-bugs@lists.postgresql.org>
Date: 2022-12-05T23:57:49Z
Lists: pgsql-bugs

Attachments

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

Commits

  1. Fix jsonpath existense checking of missing variables

  2. Harmonize more parameter names in bulk.