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 04550D1B515 for ; Sun, 5 Oct 2003 23:44:33 +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 25775-10 for ; Sun, 5 Oct 2003 20:43:49 -0300 (ADT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id F05C9D1B53A for ; Sun, 5 Oct 2003 20:43:45 -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 h95Nhmhn015814; Sun, 5 Oct 2003 19:43:48 -0400 (EDT) To: Neil Conway Cc: Andrew Sullivan , PostgreSQL Performance Subject: Re: reindex/vacuum locking/performance? In-reply-to: <1065396767.466.12.camel@tokyo> References: <60d6de9fah.fsf@dev6.int.libertyrms.info> <20031004152241.GL580@libertyrms.info> <1065396767.466.12.camel@tokyo> Comments: In-reply-to Neil Conway message dated "Sun, 05 Oct 2003 19:32:47 -0400" Date: Sun, 05 Oct 2003 19:43:48 -0400 Message-ID: <15813.1065397428@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/164 X-Sequence-Number: 3912 Neil Conway writes: > ... We could even have the > VACUUM command inform the bufmgr that the pages it is in the process of > reading in are part of a seqscan, and so are unlikely to be needed in > the immediate future. This would be relatively easy to fix as far as our own buffering is concerned, but the thing that's needed to make it really useful is to prevent caching of seqscan-read pages in the kernel disk buffers. I don't know any portable way to do that :-( regards, tom lane