Re: Unexpected chunk number

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Unexpected chunk number
Дата
Msg-id 21404.1158093856@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Unexpected chunk number  (Chris Purcell <chris.purcell.39@gmail.com>)
Ответы Re: Unexpected chunk number  (Chris Purcell <chris.purcell.39@gmail.com>)
Список pgsql-bugs
Chris Purcell <chris.purcell.39@gmail.com> writes:
>> That will get you past the reported problem, but I wonder what other
>> corruption is lurking ... once you've managed to pg_dump you'd better
>> inspect the data very carefully.

> Would the best advice be to get a pg_dump, then drop the database
> entirely and rebuild it?

Definitely.  It's entirely possible for pg_dump to dump successfully
from a database that still contains corruption.  An example:
broken indexes on user tables.  COPY just does a seqscan and never looks
at the contents of indexes ...

            regards, tom lane

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

Предыдущее
От: Chris Purcell
Дата:
Сообщение: Re: Unexpected chunk number
Следующее
От: Chris Purcell
Дата:
Сообщение: Re: Unexpected chunk number