Re: Unexpected chunk number

Поиск
Список
Период
Сортировка
От Chris Purcell
Тема Re: Unexpected chunk number
Дата
Msg-id AA613804-69E9-4C3D-A880-A274A2940407@gmail.com
обсуждение исходный текст
Ответ на Re: Unexpected chunk number  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Unexpected chunk number  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-bugs
>> 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 ...

Just out of curiosity, why is it not possible to rebuild these
indices entirely from scratch, dropping the defective file entirely,
*without* reimporting into a fresh database?

Cheers,
Chris

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

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