From: | Tomas Vondra <tomas(at)vondra(dot)me> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
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 19:51:38 |
Message-ID: | 6f690979-c477-49ee-91d2-71f676fb0b7a@email.android.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
<div dir='auto'><div><div><div class="elided-text">On Aug 21, 2024 19:17, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:<br type="attribution"><blockquote style="margin:0 0 0 0.8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">On Wed, Aug 21, 2024 at 12:31 PM Tomas Vondra <tomas(at)vondra(dot)me> wrote:
<br>
> Anyway, I took a look and the basic idea is simple - when shuffling
<br>
> tuples between batches in a hash join, we're currently deforming the
<br>
> tuple (->slot) we just read from a batch, only to immediately form it
<br>
> (slot->) again and write it to the "correct" batch.
<br>
<br>
Does skipping this cause any problem if some attributes are toasted?
<br>
<br>
I suppose not, just something to think about.
<br>
</p></blockquote></div></div></div><div dir="auto">I don't see why would this cause any such problems - if anything has to be done when forming the tuples, it had to be done the first time. Shuffling tuples to a different batch may happen, but AFAIK it's really just a copy.</div><div dir="auto"><br></div><div dir="auto"><div><div dir="auto">--</div><div dir="auto">Tomas Vondra</div></div></div></div>
Attachment | Content-Type | Size |
---|---|---|
unknown_filename | text/html | 1.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Gabriele Bartolini | 2024-08-21 19:59:46 | Re: RFC: Additional Directory for Extensions |
Previous Message | Kirill Reshke | 2024-08-21 19:34:40 | Re: Index AM API cleanup |