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 AF8B4D1B4FE for ; Fri, 3 Oct 2003 21:53:09 +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 50995-09 for ; Fri, 3 Oct 2003 18:52:21 -0300 (ADT) Received: from wolff.to (wolff.to [66.93.249.74]) by svr1.postgresql.org (Postfix) with SMTP id C90BDD1B4F0 for ; Fri, 3 Oct 2003 18:52:18 -0300 (ADT) Received: (qmail 24502 invoked by uid 500); 3 Oct 2003 21:59:39 -0000 Date: Fri, 3 Oct 2003 16:59:39 -0500 From: Bruno Wolff III To: Rob Nagler Cc: pgsql-performance@postgresql.org Subject: Re: reindex/vacuum locking/performance? Message-ID: <20031003215939.GA24446@wolff.to> Mail-Followup-To: Rob Nagler , pgsql-performance@postgresql.org References: <16253.56074.737161.470428@jump.bivio.com> <954.1065214676@sss.pgh.pa.us> <16253.61013.56254.526139@jump.bivio.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <16253.61013.56254.526139@jump.bivio.com> User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/112 X-Sequence-Number: 3860 On Fri, Oct 03, 2003 at 15:47:01 -0600, Rob Nagler wrote: > > vacuum full does require exclusive lock, plain vacuum does not. > > I think I need full, because there are updates on the table. As I > understand it, an update in pg is an insert/delete, so it needs > to be garbage collected. Plain vacuum will mark the space used by deleted tuples as reusable. Most of the time this is good enough and you don't need to run vacuum full.