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 B369D9F9F0C for ; Wed, 13 Sep 2006 15:07:44 -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 53936-09 for ; Wed, 13 Sep 2006 18:07:41 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from wolf.urban.csuohio.edu (wolf.urban.csuohio.edu [137.148.96.16]) by postgresql.org (Postfix) with ESMTP id B0D8C9FA4CF for ; Wed, 13 Sep 2006 15:07:41 -0300 (ADT) Received: from [137.148.93.10] (UB-LL-01137-148-93-10.dhcp.csuohio.edu [137.148.93.10]) by wolf.urban.csuohio.edu (8.13.7/8.13.7) with ESMTP id k8DI7LD7024954; Wed, 13 Sep 2006 14:07:21 -0400 (EDT) Message-ID: <450848DB.9030303@urban.csuohio.edu> Date: Wed, 13 Sep 2006 14:07:23 -0400 From: Ellen Cyran User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.11) Gecko/20050728 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Lane CC: "pgsql-admin@postgresql.org" Subject: Re: After how many updates should a vacuum be performed? 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> <13915.1158168441@sss.pgh.pa.us> In-Reply-To: <13915.1158168441@sss.pgh.pa.us> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-MGLCUA-CSU-MailScanner-Information: Please contact the help desk (x2200) for more information X-MGLCUA-CSU-MailScanner: Found to be clean X-MGLCUA-CSU-MailScanner-SpamCheck: not spam, SpamAssassin (notcached, score=-4.399, required 6, autolearn=not spam, ALL_TRUSTED -1.80, BAYES_00 -2.60) X-MGLCUA-CSU-MailScanner-From: ellen@urban.csuohio.edu X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200609/116 X-Sequence-Number: 23030 Someone else was doing the vacuum that didn't complete this last time and they started it at night so no other queries were running. I wasn't monitoring I/O usage at the time and in the past I just always removed the indexes and vacuumed when this happened. This is on a Solaris server, would you suggest any additional commands besides iostat to monitor the i/o? Ellen Tom Lane wrote: > 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