Received: from localhost (unknown [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id EA77C2E3A06 for ; Fri, 4 Jan 2008 14:17:08 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 78955-06 for ; Fri, 4 Jan 2008 14:17:06 -0400 (AST) Received: from main2.mycybernet.net (main2.mycybernet.net [209.222.63.140]) by postgresql.org (Postfix) with ESMTP id 7E2032E39C1 for ; Fri, 4 Jan 2008 14:17:06 -0400 (AST) Received: from 227-54-222-209.mycybernet.net ([209.222.54.227] helo=crankycanuck.ca) by main2.mycybernet.net with esmtp (Exim 4.62) (envelope-from ) id 1JAr61-0000HN-9i for pgsql-admin@postgresql.org; Fri, 04 Jan 2008 13:16:42 -0500 Received: by crankycanuck.ca (Postfix, from userid 1000) id 6D94A4FFDD; Fri, 4 Jan 2008 13:16:36 -0500 (EST) Date: Fri, 4 Jan 2008 13:16:36 -0500 From: Andrew Sullivan To: pgsql-admin@postgresql.org Subject: Re: Vacuum taking an age Message-ID: <20080104181636.GN821@crankycanuck.ca> Mail-Followup-To: Andrew Sullivan , pgsql-admin@postgresql.org References: <5a9699850801030448k126a5028m85ddb2153e95184f@mail.gmail.com> <5a9699850801032055t4d10a7e3k4e37763b4cd77d2e@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5a9699850801032055t4d10a7e3k4e37763b4cd77d2e@mail.gmail.com> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/68 X-Sequence-Number: 27842 On Fri, Jan 04, 2008 at 06:55:13AM +0200, Brian Modra wrote: > I started a vacuum on the table yesterday, and its still running. I > guess thats because the table is live. I am pretty sure that if I take > it offline, then the vacuum will complete relatively quickly. Am I > right? (I don't want to take it offline unless I really need to.) No. The vacuum on that table is going to take a long time, period. See upthread about not brushing teeth for 3 months. Anyway, I can't believe a plain vacuum is going to help you here. I'd perform CLUSTER or else dump the database and reload it. You're looking at a service outage, I think. A