| From: | Amit Langote <amitlangote09(at)gmail(dot)com> |
|---|---|
| To: | Trakshan Mishra <trakshanmishra477(at)gmail(dot)com> |
| Cc: | lucas(dot)jeffrey(at)anachronics(dot)com, tomas(at)vondra(dot)me, pgsql-hackers(at)lists(dot)postgresql(dot)org, andres(dot)kruger(at)anachronics(dot)com, rodolfo(dot)campero(at)anachronics(dot)com |
| Subject: | Re: Re: [PATCH] Fix segmentation fault caused by reentrancy in RI_Fkey_cascade_del (ri_triggers.c) |
| Date: | 2026-10-22 11:18:28 |
| Message-ID: | CA+HiwqEe=xrmaQnf6rXLwFa5CZXQg46iwTAk7_kMdC+Y6F1emQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Oct 21, 2026 at 9:02 PM Amit Langote <amitlangote09(at)gmail(dot)com> wrote:
> Thanks for the patch. I'm going to study it and post an updated
> version tomorrow. I'd like to handle errors as well as Lucas's patch
> does but I'd stick to using PG_TRY in all the branches instead of
> resowner in some and PG_TRY in others. I believe subtransaction
> aborts are handled correctly by PG_TRY-based solution but I'd need to
> test that. In any case, I want to avoid hash table and resowner calls
> in the per-row path and keep the tracking code as minimal as possible.
Sorry, ran out of time today, so will post the patch tomorrow.
--
Thanks, Amit Langote
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Bjørge Løvland | 2026-10-22 11:19:50 | Re: Design proposal: grain, exact per-time-bucket aggregates from a summarizing index |
| Previous Message | Amit Langote | 2026-10-22 11:16:39 | Re: PG19: two RI fast-path issues found while testing the batching revert |