Postgres Pro
Downloads
Home   >   mailing lists

Thread: Fw: postgrepsql vacuum

Fw: postgrepsql vacuum

From
"wenjing wu"
Date:
 

Hi,
Our site run into a pnfs server failure, because of the postgresql transaction id wraparound problem,
Now , I am trying to vacuum the database companion in the standalone model:
 
root@head02 /var/lib/pgsql/data/pg_log# su - postgres
-bash-3.00$  postgres -D /var/lib/pgsql/data        
WARNING:  database "companion" must be vacuumed within 4294599306 transactions
HINT:  To avoid a database shutdown, execute a full-database VACUUM in "companion".
WARNING:  database "companion" must be vacuumed within 4294599306 transactions
HINT:  To avoid a database shutdown, execute a full-database VACUUM in "companion".
 
PostgreSQL stand-alone backend 8.1.4
backend> vacuum full
WARNING:  database "companion" must be vacuumed within 4294599250 transactions
HINT:  To avoid a database shutdown, execute a full-database VACUUM in "companion".
WARNING:  database "companion" must be vacuumed within 4294599249 transactions
HINT:  To avoid a database shutdown, execute a full-database VACUUM in "companion".
 
and

 
it seems the vacuum failed?
any ideas about it?
 
thanks
 
wenjing
 
 

Re: Fw: postgrepsql vacuum

From
Tom Lane
Date:
"wenjing wu" <wuwj@umich.edu> writes:
> Now , I am trying to vacuum the database companion in the standalone model:

> root@head02 /var/lib/pgsql/data/pg_log# su - postgres
> -bash-3.00$  postgres -D /var/lib/pgsql/data

This is defaulting to connecting to database postgres ...

> WARNING:  database "companion" must be vacuumed within 4294599306 transactions
> HINT:  To avoid a database shutdown, execute a full-database VACUUM in "companion".

... which is not the one you need to vacuum.

> backend> vacuum full

Use a plain vacuum --- vacuum full is uselessly expensive.

            regards, tom lane