Re: BUG #3707: failure cases in reindex don't always report enough information to diagnose the issue

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: BUG #3707: failure cases in reindex don't always report enough information to diagnose the issue
Дата
Msg-id 2557.1193690989@sss.pgh.pa.us
обсуждение исходный текст
Ответ на BUG #3707: failure cases in reindex don't always report enough information to diagnose the issue  ("Rene Gollent" <rgollent@asteriasgi.com>)
Список pgsql-bugs
"Rene Gollent" <rgollent@asteriasgi.com> writes:
> If you issue a REINDEX DATABASE, which then fails due to db corruption (i.e.
> could not create index due to duplicate values), the resulting error message
> only specifies:
> ERROR:  could not create unique index
> DETAIL:  Table contains duplicated values.

Hmm.  It would be fairly easy to mention the index name here (less so to
mention the table name, but I think you'd really need to know which
index is the problem, anyway).  ISTR that when this error message was
written the index *wasn't* known at the place where the message was
being emitted, but we do have it now ...

            regards, tom lane

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

Предыдущее
От: "Rene Gollent"
Дата:
Сообщение: BUG #3707: failure cases in reindex don't always report enough information to diagnose the issue
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Possible planner bug/regression introduced in 8.2.5