X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 0E5BC9FB202 for ; Thu, 14 Sep 2006 10:18:44 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 28220-07 for ; Thu, 14 Sep 2006 10:18:25 -0300 (ADT) 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 72DCD9FA103 for ; Thu, 14 Sep 2006 10:18:33 -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 k8EDHUDx022904 for ; Thu, 14 Sep 2006 09:17:35 -0400 (EDT) Message-ID: <4509566A.20303@urban.csuohio.edu> Date: Thu, 14 Sep 2006 09:17:30 -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: "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.025 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200609/130 X-Sequence-Number: 23044 The FSM seems to be large enough. The verbose indicated 39 relations, 5090 pages, and 3952 total pages needed. Allocated FSM size is 1000 relations & 20000 pages = 186KB shared memory. Also, the vacuum of all the database only took 1 hour and 20 minutes so is there anything I should look at the next time this happens besides i/o? Thanks. 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