Re: There's random access and then there's random access - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: There's random access and then there's random access
Date
Msg-id 200712120706.lBC76d929538@momjian.us
Whole thread Raw
In response to Re: There's random access and then there's random access  (Gregory Stark <stark@enterprisedb.com>)
List pgsql-hackers
Gregory Stark wrote:
> I could swear this has been discussed in the past too. I seem to recall Luke
> disparaging Postgres on the same basis but proposing an immensely complicated
> solution. posix_fadvise or using libaio in a simplistic fashion as a kind of
> fadvise would be fairly lightweight way to get most of the benefit of the more
> complex solutions.

It has been on the TODO list for a long time:* Do async I/O for faster random read-ahead of data  Async I/O allows
multipleI/O requests to be sent to the disk with  results coming back asynchronously.
http://archives.postgresql.org/pgsql-hackers/2006-10/msg00820.php

I have added your thread URL to this.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://postgres.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [hensa22@yahoo.es: Re: [pgsql-es-ayuda] SLL error 100% cpu]
Next
From: Simon Riggs
Date:
Subject: Re: WORM and Read Only Tables (v0.1)