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 E13B29FB322 for ; Wed, 6 Sep 2006 14:58:45 -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 05330-02-3 for ; Wed, 6 Sep 2006 17:58:42 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from exchange.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by postgresql.org (Postfix) with ESMTP id B0B6B9FB331 for ; Wed, 6 Sep 2006 14:57:29 -0300 (ADT) Received: from 10.10.1.37 ([10.10.1.37]) by exchange.g2switchworks.com ([10.10.1.2]) with Microsoft Exchange Server HTTP-DAV ; Wed, 6 Sep 2006 17:57:28 +0000 Received: from state.g2switchworks.com by mail.g2switchworks.com; 06 Sep 2006 12:57:27 -0500 Subject: Re: transactoin id wraparound problem From: Scott Marlowe To: Sriram Dandapani Cc: Tom Lane , pgsql-admin@postgresql.org In-Reply-To: <6992E470F12A444BB787B5C937B9D4DF05ABC83C@ca-mail1.cis.local> References: <6992E470F12A444BB787B5C937B9D4DF05ABC83C@ca-mail1.cis.local> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1157565447.20424.16.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Wed, 06 Sep 2006 12:57:27 -0500 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=SPF_PASS, UNPARSEABLE_RELAY X-Spam-Level: X-Archive-Number: 200609/44 X-Sequence-Number: 22958 Transaction ID wraparound is a cluster issue, not an individual database issue. Due to the way PostgreSQL is designed, you need to vacuum ALL your databases, but you don't need a FULL vacuum on them all, just a regular vacuum. I'm guessing that your other databases aren't real big anyway, so it shouldn't be a big problem. If your other databases are huge, then yeah, it might take a while. On Wed, 2006-09-06 at 12:39, Sriram Dandapani wrote: > I started this about a few hours ago (I guess the message shows as a > general warning)..I am only interested in the specific database..will > this command NOT do a full vacuum of the specific database(I would like > to save the few hours that I invested in this vacuum command if > possible) > > -----Original Message----- > From: Scott Marlowe [mailto:smarlowe@g2switchworks.com] > Sent: Wednesday, September 06, 2006 10:35 AM > To: Sriram Dandapani > Cc: Tom Lane; pgsql-admin@postgresql.org > Subject: Re: [ADMIN] transactoin id wraparound problem > > Change the -f to -a > > On Wed, 2006-09-06 at 11:02, Sriram Dandapani wrote: > > I created a super user using the createuser command and issued > > > > vacuumdb -f -U superuser > > > > I still keep getting a decreasing transaction count warning. Am I > doing > > something wrong here.(The database is about 120G and while I do expect > > vacuum full to take time, I expect the warning to show an increasing > > count)