Re: 8.3.5 broken after power fail

Поиск
Список
Период
Сортировка
От Michael Monnerie
Тема Re: 8.3.5 broken after power fail
Дата
Msg-id bb6b51d03ec44eb00c06921b104b8059@webmail.zmi.at
обсуждение исходный текст
Ответ на Re: 8.3.5 broken after power fail  (Michael Monnerie <michael.monnerie@is.it-management.at>)
Ответы Re: 8.3.5 broken after power fail  (Michael Monnerie <michael.monnerie@is.it-management.at>)
Список pgsql-admin
"Michael Monnerie" <michael.monnerie@is.it-management.at> schrieb:
> select * from dbmail_messageblks where messageblk_idnr not in (3904492);
>
> That helps. Slowly I may be able to find all broken entries. Is there a
more
> automated way?

Now I already have
select * from dbmail_messageblks where messageblk_idnr not in
(3904492,3904495,3904496,3904499,3904500,3904501,3904503);
ERROR:  unexpected chunk number 1 (expected 0) for toast value 1460210 in
pg_toast_1281127

Is there a way to find out what "toast value 1460210" stands for? I'd like
to find the connection between messageblk_idnr and that toast value, as it's
not easy to find that.

mfg zmi



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

Предыдущее
От: Michael Monnerie
Дата:
Сообщение: Re: 8.3.5 broken after power fail
Следующее
От: Haluk Durmus
Дата:
Сообщение: Re: initdb causes Segmentation fault