Re: Is a clearer memory lifespan for outerTuple and innerTuple useful?

From: Andy Fan <zhihuifan1213(at)163(dot)com>
To: Andy Fan <zhihuifan1213(at)163(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Is a clearer memory lifespan for outerTuple and innerTuple useful?
Date: 2023-12-17 13:46:52
Message-ID: 877cldx7h8.fsf@163.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Andy Fan <zhihuifan1213(at)163(dot)com> writes:

> Andy Fan <zhihuifan1213(at)163(dot)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.

Attachment Content-Type Size
v2-0001-Use-MemoryContext-instead-of-ExprContext-for-node.patch text/x-diff 4.2 KB
unknown_filename text/plain 27 bytes

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hayato Kuroda (Fujitsu) 2023-12-17 15:03:33 RE: [PoC] pg_upgrade: allow to upgrade publisher node
Previous Message Chris Travers 2023-12-17 06:30:50 Re: Moving forward with TDE