Re: transactoin id wraparound problem

From: "Sriram Dandapani" <sdandapani(at)counterpane(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-admin(at)postgresql(dot)org>
Subject: Re: transactoin id wraparound problem
Date: 2006-09-06 16:48:45
Message-ID: 6992E470F12A444BB787B5C937B9D4DF05ABC81A@ca-mail1.cis.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Is there a quick way(other than vacuum full) to re-init the transaction
ids. (I can afford some downtime)

-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Wednesday, September 06, 2006 6:41 AM
To: Sriram Dandapani
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] transactoin id wraparound problem

"Sriram Dandapani" <sdandapani(at)counterpane(dot)com> writes:
> I get error messages on the console that says
> WARNING: database "xxx" must be vacuumed within 10094646 transactions

> I shutdown, restart pg and issue a vacuumdb -f <database>

The shutdown/restart was a waste of typing, and -f doesn't really help
here either.

> I still get messages saying database must be vacuumed and the
> transaction count keeps decreasing.

I'll bet a nickel you did not run the vacuum as superuser. It has to be
done by a superuser to have permission to vacuum every table in the
database (including system catalogs).

regards, tom lane

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Matthew O'Connor 2006-09-06 17:25:51 Re: transactoin id wraparound problem
Previous Message Sriram Dandapani 2006-09-06 16:02:38 Re: transactoin id wraparound problem