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 CF6EC9FB2E1 for ; Thu, 7 Sep 2006 11:06:52 -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 61155-03-5 for ; Thu, 7 Sep 2006 11:06:43 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from lists.commandprompt.com (host-130.commandprompt.net [207.173.203.130]) by postgresql.org (Postfix) with ESMTP id 8E5449FB2FC for ; Thu, 7 Sep 2006 11:03:32 -0300 (ADT) Received: from alvh.no-ip.org (201-221-202-127.bk11-dsl.surnet.cl [201.221.202.127]) (authenticated bits=0) by lists.commandprompt.com (8.13.7/8.13.6) with ESMTP id k87E2gXG002529; Thu, 7 Sep 2006 07:02:47 -0700 Received: by alvh.no-ip.org (Postfix, from userid 1000) id 31A61C3715F; Thu, 7 Sep 2006 10:02:40 -0400 (CLT) Date: Thu, 7 Sep 2006 10:02:40 -0400 From: Alvaro Herrera To: Sriram Dandapani Cc: Scott Marlowe , Tom Lane , pgsql-admin@postgresql.org Subject: Re: transactoin id wraparound problem Message-ID: <20060907140240.GB5892@alvh.no-ip.org> Mail-Followup-To: Sriram Dandapani , Scott Marlowe , Tom Lane , pgsql-admin@postgresql.org References: <6992E470F12A444BB787B5C937B9D4DF05ABC941@ca-mail1.cis.local> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6992E470F12A444BB787B5C937B9D4DF05ABC941@ca-mail1.cis.local> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: ClamAV version 0.88.3, clamav-milter version 0.88.3 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (lists.commandprompt.com [192.168.2.159]); Thu, 07 Sep 2006 07:02:51 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.265 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200609/64 X-Sequence-Number: 22978 Sriram Dandapani wrote: > Ihave a 60Gb db on which I issued a vacuumdb -a call as a superuser. It > as been running for about 20 hours. (All client connections have been > disabled as well as jobs that access any table). I see 0% cpu > utilization. The vacuumdb process by itself takes about 10% memory and > postgres uses very little cpu and some io.(10-20%). > > Is there a way to tell vacuumdb to use more resources so it can run > faster? Maybe you have the vacuum cost delay parameters set? IIRC you should drop vacuum_cost_delay to 0 if you want it to run as fast as possible. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.