BUG #5067: vacuum problem

Поиск
Список
Период
Сортировка
От Pasquale
Тема BUG #5067: vacuum problem
Дата
Msg-id 200909192148.n8JLmWfN019450@wwwmaster.postgresql.org
обсуждение исходный текст
Ответы Re: BUG #5067: vacuum problem  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-bugs
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.

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Tomas Psika
Дата:
Сообщение: notice on explicit primary key or index name
Следующее
От: Tom Lane
Дата:
Сообщение: Re: notice on explicit primary key or index name