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 D9ABC9FB340 for ; Wed, 6 Sep 2006 23:49:02 -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 50967-09 for ; Thu, 7 Sep 2006 02:48:53 +0000 (UTC) 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 3FA069FA50F for ; Wed, 6 Sep 2006 23:48:01 -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 k872luOg021553; Wed, 6 Sep 2006 19:47:57 -0700 Received: by alvh.no-ip.org (Postfix, from userid 1000) id 77052C3715F; Wed, 6 Sep 2006 22:47:50 -0400 (CLT) Date: Wed, 6 Sep 2006 22:47:50 -0400 From: Alvaro Herrera To: Sriram Dandapani Cc: Scott Marlowe , Tom Lane , pgsql-admin@postgresql.org Subject: Re: transactoin id wraparound problem Message-ID: <20060907024750.GN14024@alvh.no-ip.org> Mail-Followup-To: Sriram Dandapani , Scott Marlowe , Tom Lane , pgsql-admin@postgresql.org References: <6992E470F12A444BB787B5C937B9D4DF05ABC91A@ca-mail1.cis.local> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6992E470F12A444BB787B5C937B9D4DF05ABC91A@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]); Wed, 06 Sep 2006 19:48:01 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.135 tagged_above=0 required=5 tests=FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200609/61 X-Sequence-Number: 22975 Sriram Dandapani wrote: > Hi > I have several such databases to issue vacuum on. If I were to vacuum > each table individually, would the transaction id be updated after every > table vacuum. No, you must issue database-wide vacuums. Single-table vacuums, even if done to each and every table, do not suffice. > Wonder if it is because I have several large partitioned tables that I > drop every day that don't get vacuumed enough. The best time of the day to do the vacuum would be just after one such partition was dropped, one would think. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support