Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id ADCC09F9386 for ; Mon, 18 Dec 2006 05:26:44 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-new, port 10024) with ESMTP id 03526-03 for ; Mon, 18 Dec 2006 05:26:37 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from floppy.pyrenet.fr (floppy.pyrenet.fr [194.116.145.2]) by postgresql.org (Postfix) with ESMTP id CAB5A9F9357 for ; Mon, 18 Dec 2006 05:26:39 -0400 (AST) Received: by floppy.pyrenet.fr (Postfix, from userid 106) id D39BA30DF4; Mon, 18 Dec 2006 10:26:38 +0100 (MET) From: "Sabin Coanda" X-Newsgroups: pgsql.performance Subject: transaction ID wrap limit Date: Mon, 18 Dec 2006 11:26:38 +0200 Organization: Hub.Org Networking Services Lines: 15 Message-ID: X-Complaints-To: usenet@news.hub.org X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-RFC2646: Format=Flowed; Original To: pgsql-performance@postgresql.org X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=BAYES_50 X-Spam-Level: X-Archive-Number: 200612/459 X-Sequence-Number: 22515 Hi all, 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 ? Should I set or optimize something on my Postgresql server ? TIA, Sabin