Re: Extended Prefetching using Asynchronous IO - proposal and patch

From: Claudio Freire <klaussfreire(at)gmail(dot)com>
To: John Lumby <johnlumby(at)hotmail(dot)com>
Cc: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, pgsql hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Extended Prefetching using Asynchronous IO - proposal and patch
Date: 2014-05-29 22:29:16
Message-ID: CAGTBQpbPmoxO4OmBD04NRbr0cj4Wp1PwMY_nrB6ZGF=KyCzZyg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

On Thu, May 29, 2014 at 7:26 PM, Claudio Freire <klaussfreire(at)gmail(dot)com> wrote:
> 1) If it's the same process, wait for the full timeout (no looping).
> If you have to loop (EAGAIN or EINTR - which I just noticed you don't
> check for), that's ok.

Sorry, meant to say just looping on EINTR.

About the style guidelines, no, I just copy the style of surrounding
code usually.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2014-05-29 23:22:01 Re: Postgresql service stopped automatically after restart
Previous Message Claudio Freire 2014-05-29 22:26:44 Re: Extended Prefetching using Asynchronous IO - proposal and patch

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2014-05-29 22:45:37 Re: Odd uuid-ossp behavior on smew and shearwater
Previous Message Claudio Freire 2014-05-29 22:26:44 Re: Extended Prefetching using Asynchronous IO - proposal and patch