| From: | Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Matheus Alcantara <matheusssilv97(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Fixing memory leaks in postgres_fdw |
| Date: | 2025-05-31 11:29:10 |
| Message-ID: | CAPmGK17GKZkhZBp8PSbZ7zmWX9v-KBDBW7Fiq-PoP61TEtKd6A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, May 30, 2025 at 2:02 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jelte Fennema-Nio | 2025-05-31 11:47:43 | Commitfest app release at half June |
| Previous Message | Daniil Davydov | 2025-05-31 06:26:14 | Re: Speedup truncations of temporary relation forks |