Skip site navigation (1) Skip section navigation (2)

Re: 8.3.5 broken after power fail

From: Michael Monnerie <michael(dot)monnerie(at)is(dot)it-management(dot)at>
To: Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com>, pgsql-admin(at)postgresql(dot)org
Subject: Re: 8.3.5 broken after power fail
Date: 2009-02-17 16:08:15
Message-ID: bb6b51d03ec44eb00c06921b104b8059@webmail.zmi.at (view raw or flat)
Thread:
Lists: pgsql-admin
"Michael Monnerie" <michael(dot)monnerie(at)is(dot)it-management(dot)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



In response to

Responses

pgsql-admin by date

Next:From: Haluk DurmusDate: 2009-02-17 19:46:52
Subject: Re: initdb causes Segmentation fault
Previous:From: Michael MonnerieDate: 2009-02-17 16:03:42
Subject: Re: 8.3.5 broken after power fail

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group