Re: Extended Prefetching using Asynchronous IO - proposal and patch

From: Claudio Freire <klaussfreire(at)gmail(dot)com>
To: Peter Geoghegan <pg(at)heroku(dot)com>
Cc: John Lumby <johnlumby(at)hotmail(dot)com>, pgsql hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Extended Prefetching using Asynchronous IO - proposal and patch
Date: 2014-05-29 00:59:44
Message-ID: CAGTBQpZnSgxr2_RufpaSeQGWjVgjmTuaxTdooqxSicUNntS0dw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, May 28, 2014 at 6:51 PM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
> Have you thought about things like specialized prefetching for nested
> loop joins?

Currently, such a thing would need some non-trivial changes to the
execution nodes, I believe.

For nestloop, correct me if I'm wrong, but index scan nodes don't have
visibility of the next tuple to be searched for.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2014-05-29 01:12:23 Re: Extended Prefetching using Asynchronous IO - proposal and patch
Previous Message Bruce Momjian 2014-05-29 00:07:58 Re: Compression of full-page-writes