X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 38CA09FB203 for ; Thu, 27 Jul 2006 12:31:49 -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 09694-08 for ; Thu, 27 Jul 2006 12:31:46 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 1D5369FB202 for ; Thu, 27 Jul 2006 12:31:45 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.3 Received: from alvh.no-ip.org (200-126-100-4.bk7-dsl.surnet.cl [200.126.100.4]) by svr4.postgresql.org (Postfix) with ESMTP id 8E5545AF04C for ; Thu, 27 Jul 2006 15:31:45 +0000 (GMT) Received: by alvh.no-ip.org (Postfix, from userid 1000) id 359A3C2F859; Thu, 27 Jul 2006 11:31:43 -0400 (CLT) Date: Thu, 27 Jul 2006 11:31:43 -0400 From: Alvaro Herrera To: Nolan Cafferky Cc: pgsql-admin@postgresql.org Subject: Re: VACUUM ANALYZE suddenly taking forever Message-ID: <20060727153143.GA18774@surnet.cl> Mail-Followup-To: Nolan Cafferky , pgsql-admin@postgresql.org References: <44C8DB88.80708@rbsinteractive.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44C8DB88.80708@rbsinteractive.com> User-Agent: Mutt/1.5.12-2006-07-14 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=1.859 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE, DNS_FROM_RFC_POST, FORGED_RCVD_HELO X-Spam-Level: * X-Archive-Number: 200607/238 X-Sequence-Number: 22484 Nolan Cafferky wrote: > The so far untried ideas I've had are: > > * Try out the autovacuum service > * Re-index tables (this hasn't been done for at least months, maybe never) > * Do some selective VACUUM FULL on high-use tables (materialized view > for report seems like a likely culprit, but also seems like it wouldn't > influence both databases) > * Restart postgres, restart the machine itself, and other useless handwaving * Check whether there are open, idle transactions and close them -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support