Received: from localhost.localdomain (postgresql.org [64.49.215.8]) by localhost (Postfix) with ESMTP id F0F0A4759F1 for ; Fri, 10 May 2002 20:38:30 -0400 (EDT) Received: from bast.unixathome.org (bast.unixathome.org [216.187.105.150]) by postgresql.org (Postfix) with ESMTP id 0FEC84759B0 for ; Fri, 10 May 2002 20:38:30 -0400 (EDT) Received: from wocker (wocker.unixathome.org [192.168.0.99]) by bast.unixathome.org (Postfix) with ESMTP id 21CB03F3F; Fri, 11 May 2001 16:41:13 -0400 (EDT) From: "Dan Langille" Organization: DVL Software Limited To: Brian McCane Date: Fri, 10 May 2002 20:38:30 -0400 MIME-Version: 1.0 Subject: Re: VACUUM FULL Reply-To: dan@langille.org Cc: pgsql-admin References: In-reply-to: <20020510185436.F62674-100000@fw.mccons.net> X-mailer: Pegasus Mail for Windows (v4.01) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body Message-Id: <20010511204113.21CB03F3F@bast.unixathome.org> X-Archive-Number: 200205/91 X-Sequence-Number: 4266 On 10 May 2002 at 19:18, Brian McCane wrote: > But, a 4% decrease in size should not add up to a 84% increase in > performance (is that right? I always get the ratio confused :). Have you tried an ANALYZE as well? It wasn't mentioned. See http://www.postgresql.org/idocs/index.php?routine-vacuuming.html PostgreSQL's VACUUM command must be run on a regular basis for several reasons: 1. To recover disk space occupied by updated or deleted rows. 2. To update data statistics used by the PostgreSQL query planner. 3. To protect against loss of very old data due to transaction ID wraparound. Read 8.2.2. Updating planner statistics -- Dan Langille The FreeBSD Diary - http://freebsddiary.org/ - practical examples