X-Original-To: pgsql-performance-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 8EBDC9FB217 for ; Fri, 7 Jul 2006 20:15:36 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 79137-01 for ; Fri, 7 Jul 2006 20:15:28 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from web31814.mail.mud.yahoo.com (web31814.mail.mud.yahoo.com [68.142.206.167]) by postgresql.org (Postfix) with SMTP id A602B9FB20A for ; Fri, 7 Jul 2006 20:15:28 -0300 (ADT) Received: (qmail 92788 invoked by uid 60001); 7 Jul 2006 23:15:27 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=w8WvLkueqfMM6vHWq0TnLu/IycefJAuZUQ53Fl+BPDz4Z2/9fwEOrPqOO8b01UHC+ShyZlrytmEJk8TQiUJtihtpdzjxEAhZCtLRzadJ2SMmMIhWEiULStqJjxbapFBPIZGSK3f1R5HSN7ZlHRZV8kxWZaTfQcG1fNKnOU46RQw= ; Message-ID: <20060707231527.92786.qmail@web31814.mail.mud.yahoo.com> Received: from [65.211.203.44] by web31814.mail.mud.yahoo.com via HTTP; Fri, 07 Jul 2006 16:15:27 PDT Date: Fri, 7 Jul 2006 16:15:27 -0700 (PDT) From: Richard Broersma Jr Subject: Re: VACUUM vs. REINDEX To: William Scott Jordan , pgsql-performance@postgresql.org In-Reply-To: <6.2.3.0.2.20060707145857.0342ca58@mail.pandimensional.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200607/74 X-Sequence-Number: 19934 > I'm trying to decide now if we need to include a daily REINDEX along > with our daily VACUUM FULL, and more importantly I'm just curious to > know why we should or shouldn't do that. > > Any information on this subject would be appreciated. My understanding is that vaccum full frees all of the unused space from deprecated tuples in the table. This effective reduces that amount of tuples that will be sequencially scanned which deceases sequencial scan times. reindex rebuilds the index to removed all of the deprecated tuple references. This free memory and reduces that time it takes to scan the index. Thats how I understand it. Regards, Richard Broersma Jr.