Re: corruption issue after server crash - ERROR: unexpected chunk number 0

Поиск
Список
Период
Сортировка
От Mike Broers
Тема Re: corruption issue after server crash - ERROR: unexpected chunk number 0
Дата
Msg-id CAB9893hXCLgxyPNZ=qPUimRhiBWR_hborL6p8VbGcTPURxeTUA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: corruption issue after server crash - ERROR: unexpected chunk number 0  (Kevin Grittner <kgrittn@ymail.com>)
Ответы Re: corruption issue after server crash - ERROR: unexpected chunk number 0
Список pgsql-general
Дерево обсуждения
vacuumb avz, pg_dumpall, and vacuum freeze analyze on the former standby database that received the corruption via replication all came back without errors.  Is the vacuum freeze intended to potentially fix problems or just reveal if other tables may have corruption, Im trying to decide if this needs to be run in production.


On Thu, Nov 21, 2013 at 5:09 PM, Kevin Grittner <kgrittn@ymail.com> wrote:
Mike Broers <mbroers@gmail.com> wrote:

> Is there anything I should look out for with vacuum freeze?

Just check the logs and the vacuum output for errors and warnings.

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

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

Предыдущее
От:
Дата:
Сообщение: Re: [GENERAL] Puzzling table scan in a CTE
Следующее
От: Brian Wong
Дата:
Сообщение: Re: ERROR: out of memory DETAIL: Failed on request of size ???