Re: Fixing memory leaks in postgres_fdw

On Fri, May 30, 2025 at 2:02 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Finally, here's a minimalistic version of the original v1-0001
> patch that I think we could safely apply to fix the DirectModify
> problem in the back branches.  I rejiggered it to not depend on
> inventing MemoryContextUnregisterResetCallback, so that there's
> not hazards of minor-version skew between postgres_fdw and the
> main backend.

Seems reasonable.

Thanks for updating the patch (and pushing it in all supported versions)!

Best regards,
Etsuro Fujita