X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id E28D9D9EBE for ; Mon, 3 Oct 2005 16:39:05 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 93069-01 for ; Mon, 3 Oct 2005 19:39:00 +0000 (GMT) Received: from gwmta.wicourts.gov (gwmta.wicourts.gov [165.219.244.91]) by svr1.postgresql.org (Postfix) with ESMTP id 7CF49D9EAD for ; Mon, 3 Oct 2005 16:38:59 -0300 (ADT) Received: from Courts-MTA by gwmta.wicourts.gov with Novell_GroupWise; Mon, 03 Oct 2005 14:39:01 -0500 Message-Id: X-Mailer: Novell GroupWise Internet Agent 6.5.4 Date: Mon, 03 Oct 2005 14:38:56 -0500 From: "Kevin Grittner" To: , "Jeff Kirby" Cc: Subject: Re: Vacuum Full Analyze Stalled Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.004 required=5 tests=[AWL=0.004] X-Spam-Level: X-Archive-Number: 200510/36 X-Sequence-Number: 19108 In my previous post I failed to mention that after we stopped the applications and found that autovacuum remained idle for several minutes, we restarted postgres before cleaning up the bloat on the problem table. =20 Also, the log shows that autovacuum stopped kicking in after 4:43 p.m. on Friday. It was at about this point that I was dropping and creating indexes through psql. I did not use BEGIN TRANSACTION, but I went home with an index being built on a large table, so that connection remained open until Sunday at 9:00 p.m. I don't know if that matters, but I'm trying to be thorough. =20 -Kevin =20