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:[EMAIL PROTECTED] Sent: Wednesday, September 06, 2006 6:41 AM To: Sriram Dandapani Cc: [email protected] Subject: Re: [ADMIN] transactoin id wraparound problem "Sriram Dandapani" <[EMAIL PROTECTED]> 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 ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
