On Mon, 3 Aug 2026 at 16:52, Chao Li <[email protected]> wrote: > The optimized data structure looks good to me. The test result on my side > exactly matches yours: 3583kB vs. 2801kB. I had to turn off hash join, > otherwise the planner always chose a parallel hash join.
Thanks for looking and checking. > I have only one nitpick. MAXALIGN(sizeof(MinimalTuple)) appears 4 times. > Would it make sense to define a macro for it, say MEMOIZE_TUPLE_LINK_SIZE? Good idea. Here's a new patch with that adjustment made. David
v2-0001-Reduce-memory-overheads-for-storing-a-Memoize-tup.patch
Description: Binary data
