Re: Extended Prefetching using Asynchronous IO - proposal and patch

From: Jim Nasby <jim(at)nasby(dot)net>
To: John Lumby <johnlumby(at)hotmail(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, pgsql hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Extended Prefetching using Asynchronous IO - proposal and patch
Date: 2014-06-23 21:05:23
Message-ID: 53A89693.2030003@nasby.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

On 6/20/14, 5:12 PM, John Lumby wrote:
> I also appreciate it is not easy to review the patch.
> There are really 4 (or maybe 5) parts :
>
> . async io (librt functions)
> . buffer management (allocating, locking and pinning etc)
> . scanners making prefetch calls
> . statistics
>
> and the autoconf input program
>
> I will see what I can do. Maybe putting an indicator against each modified file?

Generally the best way to handle cases like this is to create multiple patches, each of which builds upon previous ones.
--
Jim C. Nasby, Data Architect jim(at)nasby(dot)net
512.569.9461 (cell) http://jim.nasby.net

In response to

Browse pgsql-general by date

  From Date Subject
Next Message John Lumby 2014-06-23 21:43:06 Re: Extended Prefetching using Asynchronous IO - proposal and patch
Previous Message Jeff Janes 2014-06-23 18:00:27 Re: How to get involved in the development of postgreSQL

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2014-06-23 21:10:02 Re: ALTER TABLESPACE MOVE command tag tweak
Previous Message Stephen Frost 2014-06-23 20:51:55 Re: pgaudit - an auditing extension for PostgreSQL