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 1BAF156374 for ; Thu, 10 Mar 2005 16:49:59 +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 85465-01 for ; Thu, 10 Mar 2005 16:49:56 +0000 (GMT) Received: from mail.securax.org (mail.securax.org [212.123.25.145]) by svr1.postgresql.org (Postfix) with ESMTP id 2E8FA53D6E for ; Thu, 10 Mar 2005 16:49:55 +0000 (GMT) Received: (qmail 22615 invoked by uid 2077); 10 Mar 2005 16:46:28 -0000 Received: from scx (HELO ?10.3.3.12?) (milen@securax.org@scx) by mail.securax.org with SMTP; 10 Mar 2005 16:46:28 -0000 Message-ID: <42307AB3.4040507@securax.org> Date: Thu, 10 Mar 2005 18:49:55 +0200 From: "Milen A. Radev" User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Lane Cc: pgsql-admin@postgresql.org, pgsql-hackers@postgresql.org Subject: Re: Too frequent warnings for wraparound failure References: <42301107.6010901@securax.org> <14861.1110466606@sss.pgh.pa.us> <15542.1110471710@sss.pgh.pa.us> In-Reply-To: <15542.1110471710@sss.pgh.pa.us> X-Enigmail-Version: 0.90.1.1 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.005 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200503/153 X-Sequence-Number: 16651 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Tom Lane wrote: > 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?) It's created on February 16 and is 7.4.7 on Debian GNU/Linux 3.0 (Woody) (kernel 2.6.10). > > 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. No, we do not do anything like that. We imported all databases from a backup created by using pg_dump. > > 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 - -- Milen A. Radev -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCMHqzqGlhYx0/sboRAr1dAKCB4vGHvzwsQ9zsM20y3hLrOSfqsQCgqVai 8RrSaVHjsoktDriCwCRWjfc= =ju16 -----END PGP SIGNATURE-----