Re: Extended Prefetching using Asynchronous IO - proposal and patch - Mailing list pgsql-hackers

From Claudio Freire
Subject Re: Extended Prefetching using Asynchronous IO - proposal and patch
Date
Msg-id CAGTBQpZnSgxr2_RufpaSeQGWjVgjmTuaxTdooqxSicUNntS0dw@mail.gmail.com
Whole thread Raw
In response to Re: Extended Prefetching using Asynchronous IO - proposal and patch  (Peter Geoghegan <pg@heroku.com>)
Responses Re: Extended Prefetching using Asynchronous IO - proposal and patch  (Peter Geoghegan <pg@heroku.com>)
List pgsql-hackers
On Wed, May 28, 2014 at 6:51 PM, Peter Geoghegan <pg@heroku.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.



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Compression of full-page-writes
Next
From: Peter Geoghegan
Date:
Subject: Re: Extended Prefetching using Asynchronous IO - proposal and patch