Re: EXPLAIN ANALYZE printing logical and hardware I/O per-node

From: "Trevor Talbot" <quension(at)gmail(dot)com>
To: Decibel! <decibel(at)decibel(dot)org>
Cc: "Neil Conway" <neilc(at)samurai(dot)com>, "Gregory Stark" <stark(at)enterprisedb(dot)com>, "pgsql-hackers list" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: EXPLAIN ANALYZE printing logical and hardware I/O per-node
Date: 2007-12-18 06:29:54
Message-ID: 90bce5730712172229u24e1fb2cg2cc71e226cd79aac@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 12/17/07, Decibel! <decibel(at)decibel(dot)org> wrote:

> Also, has anyone looked into adding a class of system calls that
> would actually tell us if the kernel issued physical IO? I find it
> hard to believe that other RDBMSes wouldn't like to have that info...

Non-blocking style interfaces can help here. On Windows, for instance,
a read returns data at the call site if it was satisfied by cache,
instead of invoking the asynchronous notification.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dimitri Fontaine 2007-12-18 09:03:25 Re: Sorting Improvements for 8.4
Previous Message Greg Smith 2007-12-18 02:56:16 Re: EXPLAIN ANALYZE printing logical and hardware I/O per-node