Hi



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>



I still get messages saying database must be vacuumed and the
transaction count keeps decreasing. Is vacuumdb -f not working for some
reason?

On Tue, Sep 05, 2006 at 10:45:40PM -0700, Sriram Dandapani wrote:
> WARNING: database "xxx" must be vacuumed within 10094646 transactions
>
>
>
> I shutdown, restart pg and issue a vacuumdb -f <database>

-f does _not_ mean "vacuum all databases". It means "do VACUUM
FULL". These aren't the same thing. My bet is what you need is

vacuumdb -a

You've probably missed a database you don't know is there.

A


--
Andrew Sullivan | ajs@crankycanuck.ca
Everything that happens in the world happens at some place.
--Jane Jacobs

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

"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

What exactly permissions are required to vacuum every table including
system catalogs ?

Thanks , -alex

-----Original Message-----
From: pgsql-admin-owner@postgresql.org
[mailtogsql-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

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings