Обсуждение: BUG #5067: vacuum problem
The following bug has been logged online: Bug reference: 5067 Logged by: Pasquale Email address: pasquale.napolitano@gmail.com PostgreSQL version: 8.1 Operating system: Linux Red HAT Description: vacuum problem Details: I have this problem: I don't connect any more to postres db because postgres needs to vacuum operation. 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 "postgres". 999453 but after this opertaione i don't resolve the problem, I don't connect to postgres db. How can i do? Please help me.
"Pasquale" <pasquale.napolitano@gmail.com> writes: > I don't connect any more to postres db because postgres needs to vacuum > operation. > Then, i use a standalone backend to connect to postgres db. > Now i'm im in backend> and i write VACUUM FULL. You don't really need VACUUM FULL, only VACUUM. > 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 > "postgres". > 999453 It's not an error, only a warning. You'll get a couple of those for each table in the VACUUM, but after you finish it should stop complaining. regards, tom lane