Re: Fixing memory leaks in postgres_fdw

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Matheus Alcantara <matheusssilv97(at)gmail(dot)com>
Cc: Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Fixing memory leaks in postgres_fdw
Date: 2025-05-30 18:31:54
Message-ID: 2677387.1748629914@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Matheus Alcantara <matheusssilv97(at)gmail(dot)com> writes:
> Sounds reasonable to me. +1 for going forward with these patches.

I got cold feet about applying the full patchset to v18 --- it's
kind of a large change and it's not fixing any known bug that the
minimal patch doesn't, so it feels like something not to do after
beta1. So I pushed the minimal patch in all branches. Here is
a rebased-on-top-of-that version of the full patchset, which
I plan to push once v19 development opens.

regards, tom lane

Attachment Content-Type Size
v8-0001-Create-infrastructure-to-reliably-prevent-leakage.patch text/x-diff 16.9 KB
v8-0002-Reap-the-benefits-of-not-having-to-avoid-leaking-.patch text/x-diff 32.7 KB
v8-0003-Run-pgindent-on-the-changes-of-the-previous-patch.patch text/x-diff 41.6 KB
v8-0004-Silence-leakage-complaint-about-postgres_fdw-s-In.patch text/x-diff 3.9 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Sami Imseih 2025-05-30 19:23:30 pg_get_multixact_members not documented
Previous Message Sami Imseih 2025-05-30 18:27:27 Re: queryId constant squashing does not support prepared statements