Re: Reduce TupleHashEntryData struct size by half

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Reduce TupleHashEntryData struct size by half
Date: 2025-01-14 19:38:27
Message-ID: CAApHDvrRN3_hJMzQ7HdWVeQNoGwbLvsfDePkoYDcjAcNMtYRWg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 15 Jan 2025 at 07:47, Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
>
> 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:

I must have confused TupleTableSlotOps.copy_minimal_tuple with
get_minimal_tuple. Admittedly, I didn't look at the code and was
working from memory, which must be faulty. Sounds like this makes
things easier. Good.

David

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Sami Imseih 2025-01-14 19:46:00 Re: New GUC autovacuum_max_threshold ?
Previous Message Robert Haas 2025-01-14 19:30:13 Re: New GUC autovacuum_max_threshold ?