| From: | Amit Langote <amitlangote09(at)gmail(dot)com> |
|---|---|
| To: | Andrey Rachitskiy <pl0h0yp1(at)gmail(dot)com> |
| Cc: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Nikita Malakhov <hukutoc(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Nikolay Shaplov <dhyan(at)nataraj(dot)su> |
| Subject: | Re: BUG #19458: OOM killer in jsonb_path_exists_opr (@?) with malformed JSONPath containing non-existent variables |
| Date: | 2026-06-18 06:57:20 |
| Message-ID: | CA+HiwqGxuv-G7AATJG4NCUw7r9P677vwmzegR68473wf9Leo-A@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, Jun 17, 2026 at 6:58 PM Andrey Rachitskiy <pl0h0yp1(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2026-06-18 07:52:50 | BUG #19524: In `contrib/btree_gist` float4/float8 GiST index operations, handling NaN values with raw C operator |
| Previous Message | Michael Paquier | 2026-06-18 05:40:46 | Re: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions = |