Re: pg_attribute_relid_attnam_index problem after log disk filled up

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: pg_attribute_relid_attnam_index problem after log disk filled up
Дата
Msg-id 19689.967510098@sss.pgh.pa.us
обсуждение исходный текст
Ответ на pg_attribute_relid_attnam_index problem after log disk filled up  (Palle Girgensohn <girgen@partitur.se>)
Список pgsql-sql
Palle Girgensohn <girgen@partitur.se> writes:
> What's this? What to do? Shall I bother?

> pp=> vacuum;
> NOTICE:  Index pg_attribute_relid_attnam_index: NUMBER OF
> INDEX' TUPLES (3094) IS NOT THE SAME AS HEAP' (3093)

Under 6.5, if vacuum doesn't get rid of the message then I think the
only way to do so is to dump and reload the database.  (I'd strongly
recommend updating to 7.0.2 while you do that.)

The message in itself is not catastrophic, but it does raise the
question of what other damage there might be.  Updating would be
a good idea anyway, considering all the bugs that got fixed between
6.5 and 7.0.

> The problem started when the log partition (where
> postmaster logging output is written) was full, and some
> backends crashed.

Did they actually crash, or just hang up waiting for space to become
available for the log file?  That really shouldn't have been much of
a problem, AFAICS.
        regards, tom lane


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

Предыдущее
От: Palle Girgensohn
Дата:
Сообщение: pg_attribute_relid_attnam_index problem after log disk filled up
Следующее
От: Renato De Giovanni
Дата:
Сообщение: Re: better way