Re: optimize hashjoin

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tomas Vondra <tomas(at)vondra(dot)me>
Cc: bucoo <bucoo(at)sohu(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: optimize hashjoin
Date: 2024-08-21 17:17:47
Message-ID: CA+TgmoZVEZ9-CD5gSzRzPrWbYYwnMb0sc-DPFsA19KkZBjibaQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Aug 21, 2024 at 12:31 PM Tomas Vondra <tomas(at)vondra(dot)me> wrote:
> Anyway, I took a look and the basic idea is simple - when shuffling
> tuples between batches in a hash join, we're currently deforming the
> tuple (->slot) we just read from a batch, only to immediately form it
> (slot->) again and write it to the "correct" batch.

Does skipping this cause any problem if some attributes are toasted?

I suppose not, just something to think about.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2024-08-21 17:55:06 Re: MultiXact\SLRU buffers configuration
Previous Message Peter Eisentraut 2024-08-21 16:39:21 Re: [PATCH] Add get_bytes() and set_bytes() functions