Skip site navigation (1) Skip section navigation (2)

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: (view raw, whole thread or download thread mbox)
Lists: pgsql-interfaces

In our project, we create one database named mydbname.

when I use 

select datname from pg_database;

I got:


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.

____________________________________________________________________________________Pinpoint customers who are looking for what you sell.

pgsql-interfaces by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group