Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 7EBC02E00F0 for ; Sun, 2 Mar 2008 12:16:04 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 22363-04 for ; Sun, 2 Mar 2008 12:16:01 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id F09B62E00ED for ; Sun, 2 Mar 2008 12:16:00 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m22GFx5H020300; Sun, 2 Mar 2008 11:15:59 -0500 (EST) To: "Michael Goldner" cc: pgsql-admin@postgresql.org Subject: Re: Is my vacuumdb stuck in a loop? In-reply-to: References: Comments: In-reply-to "Michael Goldner" message dated "Sun, 02 Mar 2008 09:46:27 -0500" Date: Sun, 02 Mar 2008 11:15:59 -0500 Message-ID: <20299.1204474559@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200803/5 X-Sequence-Number: 28488 "Michael Goldner" writes: > Am I stuck in a loop, or is this happening because the size of the relation > is so large that postgres is operating on smaller chunks? It's removing as many dead rows at a time as it can handle. Arithmetic suggests that you've got maintenance_work_mem set to 64MB, which would be enough room to process 11184810 rows per index scanning cycle. The fact that there are so many dead large objects is what I'd be worrying about. Does that square with your sense of what you've removed, or does it suggest you've got a large object leak? Do you use contrib/lo and/or contrib/vacuumlo to manage them? The numbers also suggest that you might be removing all or nearly all of the rows in pg_largeobject. If so, a CLUSTER on it might be more effective than VACUUM as a one-shot cleanup method. regards, tom lane