Horton

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

Amit Langote <amitlangote09@gmail.com>

View thread View on postgr.es
From: Amit Langote <amitlangote09@gmail.com>
To: Andrey Rachitskiy <pl0h0yp1@gmail.com>
Cc: Andrey Borodin <x4mmm@yandex-team.ru>, Nikita Malakhov <hukutoc@gmail.com>, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>, Nikolay Shaplov <dhyan@nataraj.su>
Date: 2026-06-18T06:57:20Z
Lists: 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 three branches, 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

Commits

  1. Report undefined jsonpath variable when no variables are supplied