Re: Is a clearer memory lifespan for outerTuple and innerTuple useful? - Mailing list pgsql-hackers

From Nikita Malakhov
Subject Re: Is a clearer memory lifespan for outerTuple and innerTuple useful?
Date
Msg-id CAN-LCVOvP70kb0hhMptjd-_NYufZScdTsq8fc9LBVadWNV+Rag@mail.gmail.com
Whole thread Raw
In response to Re: Is a clearer memory lifespan for outerTuple and innerTuple useful?  (Andy Fan <zhihuifan1213@163.com>)
Responses Re: Is a clearer memory lifespan for outerTuple and innerTuple useful?
List pgsql-hackers
Hi!

Maybe, the alternative way is using a separate kind of context, say name it
'ToastContext' for all custom data related to Toasted values? What do you think?

On Sun, Dec 17, 2023 at 4:52 PM Andy Fan <zhihuifan1213@163.com> wrote:

Andy Fan <zhihuifan1213@163.com> writes:

> Andy Fan <zhihuifan1213@163.com> writes:
>
>> ...,  I attached the 2 MemoryContext in
>> JoinState rather than MergeJoinState, which is for the "shared detoast
>> value"[0] more or less. 
>>

In order to delimit the scope of this discussion, I attached the 2
MemoryContext to MergeJoinState. Since the code was writen by Tom at
2005, so add Tom to the cc-list.


--
Best Regards
Andy Fan


--
Regards,
Nikita Malakhov
Postgres Professional
The Russian Postgres Company

pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: XID formatting and SLRU refactorings
Next
From: Tomas Vondra
Date:
Subject: Re: brininsert optimization opportunity