From: Tom Lane <tgl@sss.pgh.pa.us>
To: Matt Clark <matt@ymogen.net>
Cc: Andrew Sullivan <andrew@libertyrms.info>
Cc: pgsql-performance@postgresql.org
Subject: Re: reindex/vacuum locking/performance?
Date: Sun, 05 Oct 2003 13:11:10 -0400
Message-ID: <1368.1065373870@sss.pgh.pa.us> (raw)
In-Reply-To: <LFEIJBEOKGPDHCEMDGNFCEPLCFAA.matt@ymogen.net>
References: <LFEIJBEOKGPDHCEMDGNFCEPLCFAA.matt@ymogen.net>
"Matt Clark" <matt@ymogen.net> writes:
> OK I'm definitely missing something here.
The point is that a big seqscan (either VACUUM or a plain table scan)
hits a lot of pages, and thereby tends to fill your cache with pages
that aren't actually likely to get hit again soon, perhaps pushing out
pages that will be needed again soon. This happens at both the
shared-buffer and kernel-disk-cache levels of caching.
It would be good to find some way to prevent big seqscans from
populating cache, but I don't know of any portable way to tell the OS
that we don't want it to cache a page we are reading.
regards, tom lane
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: tgl@sss.pgh.pa.us, matt@ymogen.net, andrew@libertyrms.info
Subject: Re: reindex/vacuum locking/performance?
In-Reply-To: <1368.1065373870@sss.pgh.pa.us>
* 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