pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Craig Ringer <ringerc@ringerc.id.au>
To: Antonio Rodriges <antonio.rrz@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: [PERFORMANCE] Insights: fseek OR read_cluster?
Date: Mon, 26 Sep 2011 15:59:39 +0800
Message-ID: <4E8030EB.60105@ringerc.id.au> (raw)
In-Reply-To: <CAPrLoNdTbOpYEvk8CTbKK6T0VjskGPNve2BCYZCg5RqwQJzvrw@mail.gmail.com>
References: <CAPrLoNeyDqHwsm80iVTDeUg8-pa+pG6D43K8O1_rG2o9KHBGLw@mail.gmail.com>
	<CAPrLoNdTbOpYEvk8CTbKK6T0VjskGPNve2BCYZCg5RqwQJzvrw@mail.gmail.com>

On 24/09/2011 2:49 PM, Antonio Rodriges wrote:
> Hello,
>
> It is interesting how PostgreSQL reads the tablefiie.
> Whether its indexes store/use filesystem clusters locations containing
> required data (so it can issue a low level cluster read) or it just
> fseeks inside a file?

What is read_cluster()  ? Are you talking about some kind of async 
and/or direct I/O? If so, PostgreSQL is not designed for direct I/O, it 
benefits from using the OS's buffer cache, I/O scheduler, etc.

IIRC Pg uses pread() to read from its data files, but I didn't go double 
check in the sources to make sure.

--
Craig Ringer



view thread (6+ messages)  latest in thread

Message-ID: <4E8030EB.60105@ringerc.id.au>
Permalink:  ../4E8030EB.60105@ringerc.id.au/
Also on:    postgresql.org/message-id/4E8030EB.60105@ringerc.id.au

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: ringerc@ringerc.id.au, antonio.rrz@gmail.com
  Subject: Re: [PERFORMANCE] Insights: fseek OR read_cluster?
  In-Reply-To: <4E8030EB.60105@ringerc.id.au>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox