The following bug has been logged online:
Bug reference: 5067
Logged by: Pasquale
Email address: pasquale(dot)napolitano(at)gmail(dot)com
PostgreSQL version: 8.1
Operating system: Linux Red HAT
Description: vacuum problem
I have this problem:
I don't connect any more to postres db because postgres needs to vacuum
Then, i use a standalone backend to connect to postgres db.
Now i'm im in backend> and i write VACUUM FULL.
I have this message:
WARNING: database "postgres" must be vacuumed within 999455 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in
but after this opertaione i don't resolve the problem,
I don't connect to postgres db.
How can i do? Please help me.
pgsql-bugs by date
|Next:||From: Tom Lane||Date: 2009-09-19 22:20:25|
|Subject: Re: notice on explicit primary key or index name |
|Previous:||From: Tomas Psika||Date: 2009-09-19 21:10:54|
|Subject: notice on explicit primary key or index name|