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 DD2D0D1B584 for ; Fri, 3 Oct 2003 23:27:32 +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 64190-07 for ; Fri, 3 Oct 2003 20:26:46 -0300 (ADT) Received: from davinci.ethosmedia.com (unknown [209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP id 301C9D1B56A for ; Fri, 3 Oct 2003 20:25:55 -0300 (ADT) Received: from [66.219.92.2] (HELO temoku) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 3722108; Fri, 03 Oct 2003 16:26:32 -0700 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: "Matt Clark" , "Rob Nagler" , Subject: Re: reindex/vacuum locking/performance? Date: Fri, 3 Oct 2003 16:24:03 -0700 User-Agent: KMail/1.4.3 References: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200310031624.03933.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/121 X-Sequence-Number: 3869 Rob, > > 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. >=20 > Yes and no. You only need a plain VACUUM that is run often enough to > recover space as fast as you need to grab it. For heavily updated tables > run it often - I run it every 5 minutes on some tables. A VACUUM FULL is > only needed if you haven't been running VACUUM often enough in the first > place. Also, if you find that you need to run VACUUM FULL often, then you need to= =20 raise your max_fsm_pages. --=20 -Josh Berkus Aglio Database Solutions San Francisco