From: jing han <jing_han_66@yahoo.com>
To: pgsql-interfaces@postgresql.org
Subject: transactionID wraparound problem
Date: Thu, 24 May 2007 08:28:06 -0700 (PDT)
Message-ID: <924920.77151.qm@web53510.mail.re2.yahoo.com> (raw)
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/
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 using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: jing_han_66@yahoo.com
Subject: Re: transactionID wraparound problem
In-Reply-To: <924920.77151.qm@web53510.mail.re2.yahoo.com>
* 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