Received: from localhost (unknown [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id ABB0E2E2DF5 for ; Wed, 14 Nov 2007 17:47:26 -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 77226-04 for ; Wed, 14 Nov 2007 17:47:24 -0400 (AST) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.177]) by postgresql.org (Postfix) with ESMTP id 49C912E2DCD for ; Wed, 14 Nov 2007 17:47:23 -0400 (AST) Received: by wa-out-1112.google.com with SMTP id m38so448236waf for ; Wed, 14 Nov 2007 13:46:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=LTIleY9bM9tyJLOYpH1yX+3PJ7GXTRHFV/t2pvA7Aq8=; b=Wy5oWO1+sQGeENWhZfy82xJ3/l0Oc7mwqam37+ZJMsCBg5wNSNjm60xrL914uWVRf/zQiI0Gn03n6ScRwQR98kk/Ag7/ufbqOo8Tznghjg6y5U8ezoQmdH0pTrZCmiZCc3I5dLSDkgmrPhFvM6KtQb5yuPVlcXZkeSDLZg9bRgc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=D3Vmuu18SyazOJYjGtTCPOCI6TqfzVhV8YjiJ8pvI2NbeXcsF0FrH3BJr2s+nQ7JOS7mvUBHwtLYan6kaycaG8Uq7FYxX+2Lzvi5yWr5Gur1kr1j2oHrDbKrdGtdhdz6ZcU41tw0lr5vnOxWyfKFJYDuPhNA+rWkQKPMxOBZOZ0= Received: by 10.115.106.7 with SMTP id i7mr309419wam.1195076760506; Wed, 14 Nov 2007 13:46:00 -0800 (PST) Received: by 10.114.171.20 with HTTP; Wed, 14 Nov 2007 13:46:00 -0800 (PST) Message-ID: Date: Wed, 14 Nov 2007 15:46:00 -0600 From: "Scott Marlowe" To: "Kevin Grittner" Subject: Re: postgres bogged down beyond tolerance Cc: "Tena Sakai" , pgsql-admin@postgresql.org In-Reply-To: <473B1535.EE98.0025.0@wicourts.gov> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <473B1535.EE98.0025.0@wicourts.gov> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200711/130 X-Sequence-Number: 27373 On Nov 14, 2007 3:33 PM, Kevin Grittner wrote: > >>> On Wed, Nov 14, 2007 at 3:16 PM, in message > , "Scott Marlowe" > wrote: > > > On Nov 14, 2007 2:26 PM, Tena Sakai wrote: > >> INFO: vacuuming "public.allele" > >> INFO: "allele": found 2518282 removable, 1257262 nonremovable row versions > >> in 31511 pages > > >> Total free space (including removable row versions) is 161940948 bytes. > > > It looks to me like your tables were bloated. After running vacuum > > full your cron should run faster now. > > Isn't it usually a good idea to REINDEX after using VACUUM FULL to > recover from this level of bloat? Depends on your indexes. These didn't look bloated to me, but that wasn't the whole output of vacuum full either. Yes, reindex is a good idea after a vacuum full though.