| 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-29 14:59:45 |
| Message-ID: | 2017375.1748530785@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wrote:
> Yeah, it's not intended to be done in that order: the v5-0001 patch is
> an independent thing. I anticipate I'll have to rebase the other
> patches after I push v5-0001.
Pushed v5-0001, and here are rebased versions of the other four
patches, mostly so that the cfbot knows what is the patch-of-record.
(The rebasing is completely trivial; I'm surprised that "git am"
fails to cope.)
regards, tom lane
| Attachment | Content-Type | Size |
|---|---|---|
| v6-0001-Fix-memory-leakage-in-postgres_fdw-s-DirectModify.patch | text/x-diff | 14.6 KB |
| v6-0002-Reap-the-benefits-of-not-having-to-avoid-leaking-.patch | text/x-diff | 33.3 KB |
| v6-0003-Run-pgindent-on-the-changes-of-the-previous-patch.patch | text/x-diff | 42.3 KB |
| v6-0004-Silence-leakage-complaint-about-postgres_fdw-s-In.patch | text/x-diff | 3.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-05-29 15:12:27 | Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them |
| Previous Message | Melanie Plageman | 2025-05-29 14:57:02 | Correcting freeze conflict horizon calculation |