Re: reindex/vacuum locking/performance?

From: Neil Conway <neilc(at)samurai(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Sullivan <andrew(at)libertyrms(dot)info>, PostgreSQL Performance <pgsql-performance(at)postgresql(dot)org>
Subject: Re: reindex/vacuum locking/performance?
Date: 2003-10-05 23:50:35
Message-ID: 1065397835.471.17.camel@tokyo
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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.

True.

> I don't know any portable way to do that :-(

For the non-portable way of doing this, are you referring to O_DIRECT?

Even if it isn't available everywhere, it might be worth considering
this at least for the platforms on which it is supported.

-Neil

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Andrew Sullivan 2003-10-06 02:01:03 Re: reindex/vacuum locking/performance?
Previous Message Tom Lane 2003-10-05 23:43:48 Re: reindex/vacuum locking/performance?