Received: from localhost (maia-1.hub.org [200.46.204.191])
	by postgresql.org (Postfix) with ESMTP id C0ED79F9F08
	for <pgsql-performance-postgresql.org@postgresql.org>;
	Mon, 18 Dec 2006 11:51:27 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024)
	with ESMTP id 14385-06 for
	<pgsql-performance-postgresql.org@postgresql.org>;
	Mon, 18 Dec 2006 11:51:09 -0400 (AST)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.4
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
	by postgresql.org (Postfix) with ESMTP id D320D9F9B05
	for <pgsql-performance@postgresql.org>;
	Mon, 18 Dec 2006 11:51:09 -0400 (AST)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id kBIFp14s009114;
	Mon, 18 Dec 2006 10:51:01 -0500 (EST)
To: "Sabin Coanda" <sabin.coanda@deuromedia.ro>
cc: pgsql-performance@postgresql.org
Subject: Re: transaction ID wrap limit 
In-reply-to: <em5mse$e51$1@news.hub.org> 
References: <em5mse$e51$1@news.hub.org>
Comments: In-reply-to "Sabin Coanda" <sabin.coanda@deuromedia.ro>
	message dated "Mon, 18 Dec 2006 11:26:38 +0200"
Date: Mon, 18 Dec 2006 10:51:01 -0500
Message-ID: <9113.1166457061@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200612/461
X-Sequence-Number: 22517

"Sabin Coanda" <sabin.coanda@deuromedia.ro> writes:
> A vacuum full command logs the message:
> ... LOG:  transaction ID wrap limit is 1073822617, limited by database "A"

> Sometimes ago, the vacuum full logged:
> ... LOG:  transaction ID wrap limit is 2147484148, limited by database "A"

> What causes that difference of the limit ?

The limit is *supposed* to advance.  The fact that it jumped this much
in one step suggests you're not vacuuming often enough :-(

			regards, tom lane