From: Neil Conway <neilc@samurai.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andrew Sullivan <andrew@libertyrms.info>
Cc: PostgreSQL Performance <pgsql-performance@postgresql.org>
Subject: Re: reindex/vacuum locking/performance?
Date: Mon, 06 Oct 2003 14:14:29 -0400
Message-ID: <1065464069.473.31.camel@tokyo> (raw)
In-Reply-To: <1065397835.471.17.camel@tokyo>
References: <60d6de9fah.fsf@dev6.int.libertyrms.info>
<LFEIJBEOKGPDHCEMDGNFAEOCCFAA.matt@ymogen.net>
<20031004152241.GL580@libertyrms.info>
<1065396767.466.12.camel@tokyo>
<15813.1065397428@sss.pgh.pa.us>
<1065397835.471.17.camel@tokyo>
On Sun, 2003-10-05 at 19:50, Neil Conway wrote:
> On Sun, 2003-10-05 at 19:43, Tom Lane wrote:
> > This would be relatively easy to fix as far as our own buffering is
> > concerned, but the thing that's needed to make it really useful is
> > to prevent caching of seqscan-read pages in the kernel disk buffers.
> For the non-portable way of doing this, are you referring to O_DIRECT?
I was hoping you'd reply to this, Tom -- you were referring to O_DIRECT,
right?
(If you were referring to O_DIRECT, I wanted to add that I wouldn't be
surprised if using O_DIRECT on many kernels reduces or eliminates any
readahead the OS will be doing on the sequential read, so the net result
may actually be a loss for a typical seqscan.)
-Neil
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: neilc@samurai.com, tgl@sss.pgh.pa.us, andrew@libertyrms.info
Subject: Re: reindex/vacuum locking/performance?
In-Reply-To: <1065464069.473.31.camel@tokyo>
* 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