Re: Extended Prefetching using Asynchronous IO - proposal and patch

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Claudio Freire <klaussfreire(at)gmail(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 01:12:23
Message-ID: CAM3SWZQ5LwW-1kP52Faza6JSsXbw9FSMLoXqV+7nD9zVVistzQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, May 28, 2014 at 5:59 PM, Claudio Freire <klaussfreire(at)gmail(dot)com> wrote:
> For nestloop, correct me if I'm wrong, but index scan nodes don't have
> visibility of the next tuple to be searched for.

Nested loop joins are considered a particularly compelling case for
prefetching, actually.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2014-05-29 01:23:09 Avoiding re-creation of uuid_t state with OSSP UUID
Previous Message Claudio Freire 2014-05-29 00:59:44 Re: Extended Prefetching using Asynchronous IO - proposal and patch