From: Tom Lane <tgl@sss.pgh.pa.us>
To: Etsuro Fujita <etsuro.fujita@gmail.com>
cc: Matheus Alcantara <matheusssilv97@gmail.com>,
        pgsql-hackers@lists.postgresql.org
Subject: Re: Fixing memory leaks in postgres_fdw
In-reply-to: 
 <CAPmGK17GKZkhZBp8PSbZ7zmWX9v-KBDBW7Fiq-PoP61TEtKd6A@mail.gmail.com>
References: <2976982.1748049023@sss.pgh.pa.us>
 <CAPmGK17iOh6W25UswGcn5k75jEukSgLMpiaJEATcAZQTec7xxg@mail.gmail.com>
 <216286.1748202797@sss.pgh.pa.us> <519144.1748217540@sss.pgh.pa.us>
 <918254.1748288174@sss.pgh.pa.us>
 <CAFY6G8fEa9sZ1V9cJpMOZAp6Wfa35U_rE0Y=eoQLS2G3OAqiAw@mail.gmail.com>
 <1346940.1748381911@sss.pgh.pa.us> <1696019.1748465792@sss.pgh.pa.us>
 <CAFY6G8fY=e8n1K=sHuXovgxEgRqN1Df5db230uF1KtffvWUT-Q@mail.gmail.com>
 <1876117.1748524672@sss.pgh.pa.us> <2017375.1748530785@sss.pgh.pa.us>
 <2082618.1748538159@sss.pgh.pa.us>
 <CAPmGK17GKZkhZBp8PSbZ7zmWX9v-KBDBW7Fiq-PoP61TEtKd6A@mail.gmail.com>
Comments: In-reply-to Etsuro Fujita <etsuro.fujita@gmail.com>
	message dated "Sat, 31 May 2025 20:29:10 +0900"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <2223526.1753476592.1@sss.pgh.pa.us>
Content-Transfer-Encoding: 8bit
Date: Fri, 25 Jul 2025 16:49:52 -0400
Message-ID: <2223527.1753476592@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2223527.1753476592%40sss.pgh.pa.us>
Precedence: bulk

Etsuro Fujita <etsuro.fujita@gmail.com> writes:
> 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.

Pushed the larger patchset now.  I had to do a little more work
to get it to play with 112faf137, but it wasn't hard.

			regards, tom lane