Re: Reduce TupleHashEntryData struct size by half - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: Reduce TupleHashEntryData struct size by half
Date
Msg-id ef80cf623dca460ac865869c8b324b501e00052a.camel@j-davis.com
Whole thread Raw
In response to Re: Reduce TupleHashEntryData struct size by half  (David Rowley <dgrowleyml@gmail.com>)
Responses Re: Reduce TupleHashEntryData struct size by half
List pgsql-hackers
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




pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: pgsql: Consolidate docs for vacuum-related GUCs in new subsection
Next
From: Melanie Plageman
Date:
Subject: Re: pgsql: Consolidate docs for vacuum-related GUCs in new subsection