| From: | Nikita Malakhov <hukutoc(at)gmail(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 21:20:22 |
| Message-ID: | CAN-LCVOvP70kb0hhMptjd-_NYufZScdTsq8fc9LBVadWNV+Rag@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)163(dot)com> wrote:
>
> 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.
>
>
> --
> Best Regards
> Andy Fan
>
--
Regards,
Nikita Malakhov
Postgres Professional
The Russian Postgres Company
https://postgrespro.ru/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2023-12-17 21:27:23 | Re: brininsert optimization opportunity |
| Previous Message | Thomas Munro | 2023-12-17 21:14:03 | Re: XID formatting and SLRU refactorings |