From: | <alex(dot)cotarlan(at)thomson(dot)com> |
---|---|
To: | <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <sdandapani(at)counterpane(dot)com> |
Cc: | <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: transactoin id wraparound problem |
Date: | 2006-09-06 19:29:25 |
Message-ID: | ED5A90704BD7744380E00432EEE1652303803896@TFUSNYNYCMBX01.ERF.THOMSON.COM |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
What exactly permissions are required to vacuum every table including
system catalogs ?
Thanks , -alex
-----Original Message-----
From: pgsql-admin-owner(at)postgresql(dot)org
[mailto:pgsql-admin-owner(at)postgresql(dot)org] On Behalf Of Tom Lane
Sent: Wednesday, September 06, 2006 9: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
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
message can get through to the mailing list cleanly
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Sullivan | 2006-09-06 19:32:08 | Re: transactoin id wraparound problem |
Previous Message | Sriram Dandapani | 2006-09-06 19:23:01 | Re: transactoin id wraparound problem |