Skip site navigation (1) Skip section navigation (2)

BUG #5067: vacuum problem

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 (view raw or flat)
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.

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2009-09-19 22:20:25
Subject: Re: notice on explicit primary key or index name
Previous:From: Tomas PsikaDate: 2009-09-19 21:10:54
Subject: notice on explicit primary key or index name

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group