Re: transactoin id wraparound problem - Mailing list pgsql-admin

From
Subject Re: transactoin id wraparound problem
Date
Msg-id ED5A90704BD7744380E00432EEE1652303803896@TFUSNYNYCMBX01.ERF.THOMSON.COM
Whole thread Raw
In response to Re: transactoin id wraparound problem  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-admin
What exactly permissions are required to vacuum every table including
system catalogs ?

Thanks , -alex

-----Original Message-----
From: pgsql-admin-owner@postgresql.org
[mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Tom Lane
Sent: Wednesday, September 06, 2006 9:41 AM
To: Sriram Dandapani
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] transactoin id wraparound problem

"Sriram Dandapani" <sdandapani@counterpane.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

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
       subscribe-nomail command to majordomo@postgresql.org so that your
       message can get through to the mailing list cleanly

pgsql-admin by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Why so long between archive calls?
Next
From: Tom Lane
Date:
Subject: Re: Why so long between archive calls?