X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id DB9F555683; Thu, 10 Mar 2005 16:21:55 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 72302-09; Thu, 10 Mar 2005 16:21:52 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 58BC053D6E; Thu, 10 Mar 2005 16:21:51 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j2AGLoOw015543; Thu, 10 Mar 2005 11:21:50 -0500 (EST) To: "Milen A. Radev" Cc: pgsql-admin@postgresql.org, pgsql-hackers@postgresql.org Subject: Re: Too frequent warnings for wraparound failure In-reply-to: <14861.1110466606@sss.pgh.pa.us> References: <42301107.6010901@securax.org> <14861.1110466606@sss.pgh.pa.us> Comments: In-reply-to Tom Lane message dated "Thu, 10 Mar 2005 09:56:46 -0500" Date: Thu, 10 Mar 2005 11:21:50 -0500 Message-ID: <15542.1110471710@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.007 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200503/151 X-Sequence-Number: 16649 I wrote: > "Milen A. Radev" writes: >> I review the log every morning. In the beginning I got "wraparound >> failure" warnings every third day. But from a week I got those warnings >> every day. Well we have one table in one database where there are a lot >> of inserts, but not that many - around 30-40 thousand per day. > Are you really doing half a billion transactions a day? I thought of another mechanism that wouldn't require such a preposterous load, only half a billion transactions since initdb. (How old is this installation, anyway, and which PG version?) If you are creating new databases every day and you do it by cloning template0, then the new databases would come into existence with datfrozenxid equal to template0's. Once template0 is more than half a billion transactions old, you'd start seeing the warning. This is relatively harmless, but probably we should try to mask it. We could make CREATE DATABASE set datfrozenxid to current time when cloning a database that has datallowconn false, on the assumption that the source DB is entirely frozen and so there's nothing to vacuum yet. regards, tom lane