Re: database must be vacuumed with transactions

Поиск
Список
Период
Сортировка
От Dave Johansen
Тема Re: database must be vacuumed with transactions
Дата
Msg-id CAAcYxUce5+vBgqEJyJ6guGjRn1xg+FpCT_GUK8jrworkGG6eOw@mail.gmail.com
обсуждение исходный текст
Ответ на database must be vacuumed with transactions  (Dave Johansen <davejohansen@gmail.com>)
Ответы Re: database must be vacuumed with transactions
Re: database must be vacuumed with transactions
Список pgsql-admin
On Thu, Jun 25, 2015 at 8:49 AM, Dave Johansen <davejohansen@gmail.com> wrote:
The database I work on started spitting out the following message last night:
WARNING:  database "ops" must be vacuumed within 9361597 transaction

I ran VACUUM as soon as I got in, but then shortly after, it stopped accepting transactions. I stopped the database and opened single user mode to run VACUUM. So my questions are:
1) How long should I expect this to take (database has about 5 TB of data)?
2) Is there a faster way to make the database be operational again?

Sorry for the multiple emails, but I forgot to mention that I'm using 8.4 on RHEL 6.4.

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

Предыдущее
От: Dave Johansen
Дата:
Сообщение: database must be vacuumed with transactions
Следующее
От: John Scalia
Дата:
Сообщение: Re: Trying to change the owner of some tables