Re: Too frequent warnings for wraparound failure - Mailing list pgsql-admin

From Milen A. Radev
Subject Re: Too frequent warnings for wraparound failure
Date
Msg-id 42316D98.9030507@securax.org
Whole thread Raw
In response to Re: Too frequent warnings for wraparound failure  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Too frequent warnings for wraparound failure  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Too frequent warnings for wraparound failure  (Michael Fuhr <mike@fuhr.org>)
List pgsql-admin
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Tom Lane wrote:
> "Milen A. Radev" <milen@securax.org> writes:
>
>>Two queries - 2 seconds apart:
>
>
>>template1=# SELECT datname, age(datfrozenxid) FROM pg_database;
>>  datname  |     age
>>- -----------+-------------
>> xxx1      |  1519763573
>
>
>>template1=# SELECT datname, age(datfrozenxid) FROM pg_database;
>>  datname  |     age
>>- -----------+-------------
>> xxx1      |  1519769620
>
>
> So you managed to execute about 6000 transactions in those two seconds.
> Doing what?
>
>             regards, tom lane


Well that could be the problem - I'm 99.99% positive we do not execute
so many transactions - may be 30-40 thousand per day and that's only for
one relatively busy DB. The example database ("xxx1") you've chosen is
not used at all. As most of the other databases in that cluster.

And another observation (closely related IMO): when I login on another
development server/cluster and execute the same query I get an increment
 for every database for every query execution. But there the version is
8.0.1.


- --
Milen A. Radev
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCMW2YqGlhYx0/sboRAvO3AJ9PAaADiX2Ci9iChyNCpojFb5uvwgCgnJ99
mzTydVpBaMCp/hJjrUvuO5Q=
=OKGe
-----END PGP SIGNATURE-----

pgsql-admin by date:

Previous
From: thomas.revell@powerconv.alstom.com
Date:
Subject: Re: How to enable automatic md5 password prompting when
Next
From: John DeSoi
Date:
Subject: Re: How to enable automatic md5 password prompting when connecting to PostgreSQL