From: Milen A. Radev <milen@securax.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Cc: pgsql-hackers@postgresql.org
Subject: Re: Too frequent warnings for wraparound failure
Date: Thu, 10 Mar 2005 18:49:55 +0200
Message-ID: <42307AB3.4040507@securax.org> (raw)
In-Reply-To: <15542.1110471710@sss.pgh.pa.us>
References: <42301107.6010901@securax.org>
<14861.1110466606@sss.pgh.pa.us>
<15542.1110471710@sss.pgh.pa.us>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Tom Lane wrote:
> I wrote:
>
>>"Milen A. Radev" <milen@securax.org> 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-----
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: milen@securax.org, tgl@sss.pgh.pa.us, pgsql-hackers@postgresql.org
Subject: Re: Too frequent warnings for wraparound failure
In-Reply-To: <42307AB3.4040507@securax.org>
References: <42301107.6010901@securax.org> <14861.1110466606@sss.pgh.pa.us> <15542.1110471710@sss.pgh.pa.us> <42307AB3.4040507@securax.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox