Re: [ADMIN] WARNING: database must be vacuumed within 8439472 transactions
От | Scott Whitney |
---|---|
Тема | Re: [ADMIN] WARNING: database must be vacuumed within 8439472 transactions |
Дата | |
Msg-id | pbwq0jvbgjg1nw5hnhe18aqe.1404764557197@email.android.com обсуждение исходный текст |
Ответы |
Re: [ADMIN] WARNING: database must be vacuumed within
8439472 transactions
|
Список | pgsql-general |
It does say a FULL vacuum, and that you are not doing.
-------- Original message --------
From: Mike Christensen
Date:07/07/2014 3:17 PM (GMT-06:00)
To: Prabhjot Sheena
Cc: pgsql-admin@postgresql.org,Forums postgresql
Subject: Re: [ADMIN] [GENERAL] WARNING: database must be vacuumed within 8439472 transactions
Sounds like you just have to wait until it finishes..
On Mon, Jul 7, 2014 at 12:56 PM, Prabhjot Sheena <prabhjot.sheena@rivalwatch.com> wrote:
AviThanksCan anyone tell me what is the best way to sort up this issue.while this command is running i m still getting these messagesi am currently running this commandHelloWe are using postgresql 8.3 database for last 5 yrs for this production database and its running fine. This is our critical database which runs 24*7. This weekend we started getting these messages
HINT: To avoid a database shutdown, execute a full-database VACUUM.
WARNING: database must be vacuumed within 8439472 transactions
vacuumdb --analyze db
WARNING: database must be vacuumed within 2645303 transactions.
The value of number of transactions is going down every minute
В списке pgsql-general по дате отправления: