On Tue, 2025-01-14 at 22:01 +1300, David Rowley wrote:
> The trick would be to ensure ExecClearTuple() still works.
I'm confused by this. The comment over copy_minimal_slot says:
/*
* Return a copy of minimal tuple representing the contents of the
slot.
* The copy needs to be palloc'd in the current memory context. The
slot
* itself is expected to remain unaffected. It is *not* expected to
have
* meaningful "system columns" in the copy. The copy is not be "owned"
by
* the slot i.e. the caller has to take responsibility to free memory
* consumed by the slot.
*/
So why would ExecClearTuple() be a problem?
Regards,
Jeff Davis
