On Tue, Mar 16, 2010 at 1:48 PM, Pierre C <lists@xxxxxxxxxx> wrote: > Actually, I meant that in the case of a seq scan, PG will try to use just a > few buffers (a ring) in shared_buffers instead of thrashing the whole > buffers. But if there was actually a lot of free space in shared_buffers, do > the pages stay, or do they not ? They don't. The logic only kicks in if the table is expected to be > 1/4 of shared buffers though. -- greg -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
