Re: There's random access and then there's random access

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Gregory Stark <stark(at)enterprisedb(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers list <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: There's random access and then there's random access
Date: 2007-12-12 07:06:39
Message-ID: 200712120706.lBC76d929538@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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 multiple I/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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2007-12-12 08:34:09 Re: WORM and Read Only Tables (v0.1)
Previous Message Tom Lane 2007-12-12 05:30:50 Re: [hensa22@yahoo.es: Re: [pgsql-es-ayuda] SLL error 100% cpu]