Re: catalog corruption bug

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: catalog corruption bug
Дата
Msg-id 23751.1136567776@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: catalog corruption bug  (Jeremy Drake <pgsql@jdrake.com>)
Ответы Re: catalog corruption bug  (Jeremy Drake <pgsql@jdrake.com>)
Список pgsql-hackers
Jeremy Drake <pgsql@jdrake.com> writes:
>>> DBD::Pg::st execute failed: ERROR:  duplicate key violates unique
>>> constraint "pg_type_typname_nsp_index"
>> 
>> Hm, did you REINDEX things beforehand?  This could be leftover corruption...

> Yes.  I ran that VACUUM FULL ANALYZE VERBOSE which I emailed part of the
> excerpt from, and then I started a standalone backend (postgres -D data
> -P) and ran REINDEX SYSTEM dbname on the database in question.

OK, this must be a different issue then.  I think we have seen reports
like this one before, but not been able to reproduce it.

Could you rebuild with Asserts enabled and see if any asserts trigger?
Also, at this point it'd be worth trying to boil it down to a test case
you can give to other people.
        regards, tom lane


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

Предыдущее
От: Jeremy Drake
Дата:
Сообщение: Re: catalog corruption bug
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Improving N-Distinct estimation by ANALYZE