Re: [PATCH] Fix leak when a plpgsql exception block catches an error from CALL

From: Muzzammil Sarwar <muzzammil(at)umaish(dot)com>
To: Aleksander Alekseev <aleksander(at)tigerdata(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [PATCH] Fix leak when a plpgsql exception block catches an error from CALL
Date: 2026-11-20 19:11:11
Message-ID: CABUcsRR-eQL7igFKeLZnoB7NgOxOtExbsdK-NQmWkASW0EZiNQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Aleksander,

Thank you for reviewing the patch and for moving it to Ready for Committer.

Regards,
Muzzammil

On Thu, Nov 19, 2026 at 12:46 PM Aleksander Alekseev <
aleksander(at)tigerdata(dot)com> wrote:

> Hi Muzzammil,
>
> > A PL/pgSQL procedure, called outside a transaction block, that calls
> > another procedure inside an exception block keeps the plan of every
> > CALL that fails until it returns, so a loop that catches such failures
> > uses memory without limit:
> >
> > [...]
>
> Thanks for the patch and the detailed description. Looks correct and
> complete to me. Changing the CF entry status to RfC.
>
> --
> Best regards,
> Aleksander Alekseev
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Previous Message Melanie Plageman 2026-11-20 18:53:59 Stop masking visibility information during WAL consistency checking