X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 0A13AD1B500 for ; Sun, 5 Oct 2003 17:11:58 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 62298-09 for ; Sun, 5 Oct 2003 14:11:12 -0300 (ADT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id E43D7D1B4ED for ; Sun, 5 Oct 2003 14:11:10 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.10/8.12.10) with ESMTP id h95HBAhn001369; Sun, 5 Oct 2003 13:11:10 -0400 (EDT) To: "Matt Clark" Cc: "Andrew Sullivan" , pgsql-performance@postgresql.org Subject: Re: reindex/vacuum locking/performance? In-reply-to: References: Comments: In-reply-to "Matt Clark" message dated "Sun, 05 Oct 2003 17:46:21 +0100" Date: Sun, 05 Oct 2003 13:11:10 -0400 Message-ID: <1368.1065373870@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/156 X-Sequence-Number: 3904 "Matt Clark" 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