| From: | "Pasquale" <pasquale(dot)napolitano(at)gmail(dot)com> |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | BUG #5067: vacuum problem |
| Date: | 2009-09-19 21:48:32 |
| Message-ID: | 200909192148.n8JLmWfN019450@wwwmaster.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-09-19 22:20:25 | Re: notice on explicit primary key or index name |
| Previous Message | Tomas Psika | 2009-09-19 21:10:54 | notice on explicit primary key or index name |