transactionID wraparound problem

From: jing han <jing_han_66(at)yahoo(dot)com>
To: pgsql-interfaces(at)postgresql(dot)org
Subject: transactionID wraparound problem
Date: 2007-05-24 15:28:06
Message-ID: 924920.77151.qm@web53510.mail.re2.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-interfaces

Hello,

In our project, we create one database named mydbname.

when I use

select datname from pg_database;

I got:

datname
-----------
postgres
mydbname
template1
template0

According to the postgresql document, in order to prevent transaction ID wraparound failures,
in my code, I use:

SELECT datname, age(datfrozenxid) FROM pg_database;

datname | age
-----------+------------
postgres | 1086137251
mydbname | 1073771662
template1 | 1086137306
template0 | 13977307

to check if age of postgres, template1, mydbname are over 1500000000,

if one of them age number is over 1500000000, for example, postgres age number is over 1500000000
I do psql --username=postgres -c 'VACUUM full' -d postgres

I have to do vacuum on template1, mydbname, and postgres, but not at the same time.

Is this the correct way to get rid of transaction ID wraparound failure?

Any answer will be appreciated.
jing


____________________________________________________________________________________Pinpoint customers who are looking for what you sell.
http://searchmarketing.yahoo.com/

Browse pgsql-interfaces by date

  From Date Subject
Next Message RaviRam Kolipaka 2007-05-28 06:59:37 C++ postgresql interface in fedora core 5
Previous Message jing han 2007-05-24 12:46:58 unexpected EOF on client connection