Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id E64749FB255 for ; Thu, 28 Sep 2006 16:29:21 -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 95875-03 for ; Thu, 28 Sep 2006 19:29:12 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id 298FE9FB354 for ; Thu, 28 Sep 2006 16:29:11 -0300 (ADT) Received: by noel.decibel.org (Postfix, from userid 1001) id ECEBE56431; Thu, 28 Sep 2006 14:29:10 -0500 (CDT) Received: (hashcash-sendmail, from uid 1001); Thu, 28 Sep 2006 14:29:10 -0500 Date: Thu, 28 Sep 2006 14:29:10 -0500 From: "Jim C. Nasby" To: Sriram Dandapani Cc: pgsql-admin@postgresql.org Subject: Re: transaction id wraparound Message-ID: <20060928192910.GZ34238@nasby.net> References: <6992E470F12A444BB787B5C937B9D4DF060E5A57@ca-mail1.cis.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6992E470F12A444BB787B5C937B9D4DF060E5A57@ca-mail1.cis.local> X-Operating-System: FreeBSD 6.0-RELEASE-p4 amd64 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.11 X-Hashcash: 1:20:060928:sdandapani@counterpane.com::+aeks3EspyoKHqQN:00000000000 0000000000000000000000000h7x X-Hashcash: 1:20:060928:pgsql-admin@postgresql.org::RkTQ4e9WYNttSJyj:00000000000 0000000000000000000000003eN3 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/343 X-Sequence-Number: 23257 Interesting... age(xid) isn't documented anywhere. No, vacuum shouldn't be generating a lot of xid's. My guess is that your generating process actually does 2 transactions per row. On Thu, Sep 28, 2006 at 11:16:24AM -0700, Sriram Dandapani wrote: > When I run this query > > > > fwdb01=# select current_timestamp,datname,age(datfrozenxid) from > pg_database; > > now | datname | age > > -------------------------------+-----------+------------ > > 2006-09-28 18:04:24.489935+00 | postgres | 1087834006 > > 2006-09-28 18:04:24.489935+00 | fwdb01 | 2039254861 > > 2006-09-28 18:04:24.489935+00 | template1 | 2039253122 > > 2006-09-28 18:04:24.489935+00 | template0 | 1542808250 > > (4 rows) > > > > fwdb01=# select current_timestamp,datname,age(datfrozenxid) from > pg_database; > > now | datname | age > > ------------------------------+-----------+------------ > > 2006-09-28 18:10:45.64452+00 | postgres | 1088357075 > > 2006-09-28 18:10:45.64452+00 | fwdb01 | 2039777930 > > 2006-09-28 18:10:45.64452+00 | template1 | 2039776191 > > 2006-09-28 18:10:45.64452+00 | template0 | 1543331319 > > > > > > In approximately 6 minutes, the fwdb01 count has gone up by about 500K. > I am generating about 250K rows for every 6 . I am also running > vacuumdb. > > > > Does vacuumdb generate a lot of transactions that affects this counter. > -- Jim Nasby jim@nasby.net EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)