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                       j...@nasby.net
512.569.9461 (cell)                         http://jim.nasby.net


--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Reply via email to