Re: BUG #19458: OOM killer in jsonb_path_exists_opr (@?) with malformed JSONPath containing non-existent variables - Mailing list pgsql-bugs

From Amit Langote
Subject Re: BUG #19458: OOM killer in jsonb_path_exists_opr (@?) with malformed JSONPath containing non-existent variables
Date
Msg-id CA+HiwqGxuv-G7AATJG4NCUw7r9P677vwmzegR68473wf9Leo-A@mail.gmail.com
Whole thread
In response to Re: BUG #19458: OOM killer in jsonb_path_exists_opr (@?) with malformed JSONPath containing non-existent variables  (Andrey Rachitskiy <pl0h0yp1@gmail.com>)
List pgsql-bugs
On Wed, Jun 17, 2026 at 6:58 PM Andrey Rachitskiy <pl0h0yp1@gmail.com> wrote:
>
> Hi Amit,
>
> I tested patch v2-0001-Report-undefined-jsonpath-variable-when-no-variab.patch on:
>
> REL_14_STABLE
> REL_15_STABLE
> REL_16_STABLE
>
> Results:
> The patch applies cleanly on all three branches.
> Regression tests added/affected by the patch pass on all three branches:
> REL_14: all relevant tests passed
> REL_15: all relevant tests passed
> REL_16: all relevant tests passed
> The provided jsonpath reproducer query now consistently returns an error about an undefined jsonpath variable on all
threebranches, which matches the expected behavior change from this patch. 
>
> Conclusion:
> The patch looks good from the testing side and can be merged.

Thanks for checking, pushed.

--
Thanks, Amit Langote



pgsql-bugs by date:

Previous
From: Michael Paquier
Date:
Subject: Re: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions =
Next
From: PG Bug reporting form
Date:
Subject: BUG #19523: psql tab-completion shadows pg_db_role_setting