Re: seq scan cache vs. index cache smackdown

From: "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com>
To: "Greg Stark" <gsstark(at)mit(dot)edu>
Cc: <pgsql-performance(at)postgresql(dot)org>
Subject: Re: seq scan cache vs. index cache smackdown
Date: 2005-02-15 14:46:33
Message-ID: 6EE64EF3AB31D5448D0007DD34EEB3412A761E@Herge.rcsinc.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

> It seems inevitable that Postgres will eventually eliminate that
redundant
> layer of buffering. Since mmap is not workable, that means using
O_DIRECT
> to
> read table and index data.

What about going the other way and simply letting the o/s do all the
caching? How bad (or good) would the performance really be?

Merlin

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Bricklen Anderson 2005-02-15 15:11:57 Re: How to interpret this explain analyse?
Previous Message PFC 2005-02-15 08:51:22 Re: VACCUM FULL ANALYZE PROBLEM