Received: from localhost (unknown [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 4411B2E2762 for ; Wed, 14 Nov 2007 17:33:19 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 30814-01 for ; Wed, 14 Nov 2007 17:33:07 -0400 (AST) Received: from gwmta.wicourts.gov (gwmta.wicourts.gov [165.219.244.99]) by postgresql.org (Postfix) with ESMTP id 1D3652E2002 for ; Wed, 14 Nov 2007 17:33:16 -0400 (AST) Received: from Courts-MTA by gwmta.wicourts.gov with Novell_GroupWise; Wed, 14 Nov 2007 15:33:14 -0600 Message-Id: <473B1535.EE98.0025.0@wicourts.gov> X-Mailer: Novell GroupWise Internet Agent 7.0.2 Date: Wed, 14 Nov 2007 15:33:09 -0600 From: "Kevin Grittner" To: "Tena Sakai" , "Scott Marlowe" Cc: Subject: Re: postgres bogged down beyond tolerance References: In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200711/129 X-Sequence-Number: 27372 >>> On Wed, Nov 14, 2007 at 3:16 PM, in message , "Scott = Marlowe" wrote:=20 =20 > 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 =20 >> Total free space (including removable row versions) is 161940948 = bytes. =20 > It looks to me like your tables were bloated. After running vacuum > full your cron should run faster now. =20 Isn't it usually a good idea to REINDEX after using VACUUM FULL to recover from this level of bloat? =20 -Kevin =20