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 A6540D1B540 for ; Sun, 5 Oct 2003 14:35:20 +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 49102-03 for ; Sun, 5 Oct 2003 11:34:34 -0300 (ADT) Received: from mail.libertyrms.com (unknown [209.167.124.227]) by svr1.postgresql.org (Postfix) with ESMTP id BC422D1B548 for ; Sun, 5 Oct 2003 11:34:29 -0300 (ADT) Received: from [10.1.2.130] (helo=dba2) by mail.libertyrms.com with esmtp (Exim 3.22 #3 (Debian)) id 1A69xw-0006A3-00 for ; Sun, 05 Oct 2003 10:34:32 -0400 Received: by dba2 (Postfix, from userid 1019) id 09E7CC9FE; Sun, 5 Oct 2003 10:34:32 -0400 (EDT) Date: Sun, 5 Oct 2003 10:34:31 -0400 From: Andrew Sullivan To: pgsql-performance@postgresql.org Subject: Re: reindex/vacuum locking/performance? Message-ID: <20031005143431.GC3441@libertyrms.info> Mail-Followup-To: Andrew Sullivan , pgsql-performance@postgresql.org References: <20031004152241.GL580@libertyrms.info> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/154 X-Sequence-Number: 3902 On Sun, Oct 05, 2003 at 12:14:24PM +0100, Matt Clark wrote: > more info on how it clobbers shared_buffers? Vacuum is like a seqscan. It touches everything on a table. So it doesn't clobber them, but that's the latest data. It's unlikely your buffers are big enough to hold your database, unless your database is small. So you'll end up expiring potentially useful data in the buffer. A -- ---- Andrew Sullivan 204-4141 Yonge Street Afilias Canada Toronto, Ontario Canada M2P 2A8 +1 416 646 3304 x110