X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id C56D59FA4CF for ; Wed, 13 Sep 2006 14:27:30 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 55384-02 for ; Wed, 13 Sep 2006 17:27:23 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id F1DC49FA380 for ; Wed, 13 Sep 2006 14:27:22 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k8DHRLlV013916; Wed, 13 Sep 2006 13:27:21 -0400 (EDT) To: Ellen Cyran cc: "pgsql-admin@postgresql.org" Subject: Re: After how many updates should a vacuum be performed? In-reply-to: <45083BCE.9070109@urban.csuohio.edu> References: <45082C83.5040206@urban.csuohio.edu> <12738.1158164349@sss.pgh.pa.us> <45083274.902@urban.csuohio.edu> <13301.1158166441@sss.pgh.pa.us> <45083BCE.9070109@urban.csuohio.edu> Comments: In-reply-to Ellen Cyran message dated "Wed, 13 Sep 2006 13:11:42 -0400" Date: Wed, 13 Sep 2006 13:27:21 -0400 Message-ID: <13915.1158168441@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200609/115 X-Sequence-Number: 23029 Ellen Cyran writes: >> Hm, that should be OK. What do you have maintenance_work_mem set to? > It's set at the default 16384. That should be plenty for getting rid of a million or so tuples. I'm wondering if you are seeing some weird locking effect. Is the VACUUM constantly busy with I/O or does it sit and wait at points? Do you have other queries actively accessing the table during the VACUUM? regards, tom lane