Re: seq scan cache vs. index cache smackdown - Mailing list pgsql-performance

From Merlin Moncure
Subject Re: seq scan cache vs. index cache smackdown
Date
Msg-id 6EE64EF3AB31D5448D0007DD34EEB3412A761E@Herge.rcsinc.local
Whole thread Raw
In response to seq scan cache vs. index cache smackdown  (Mark Aufflick <mark@pumptheory.com>)
List 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

pgsql-performance by date:

Previous
From: PFC
Date:
Subject: Re: VACCUM FULL ANALYZE PROBLEM
Next
From: Bricklen Anderson
Date:
Subject: Re: How to interpret this explain analyse?