From: | Lonni Friedman <lfriedman(at)vasoftware(dot)com> |
---|---|
To: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: unable to dump database, toast errors |
Date: | 2003-04-07 03:31:53 |
Message-ID: | 3E90F129.2040302@vasoftware.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 04/06/03 17:28, Jan Wieck wrote:
> Lonni Friedman wrote:
>>
>> On 04/06/03 14:50, Jan Wieck wrote:
>> >>From that I would assume that the row at offset 693 is totally intact
>> > but the one at 694 is the one damaged. LIMIT reads one more row
>> > internally than you asked for.
>> >
>> > Get the key of the row at 694 (and others you might find) and continue
>> > the work using those keys.
>>
>> I'm not sure that I understand what it is that I need to do now:
>>
>> sfee=# select bin_data from artifact_file LIMIT 1 OFFSET 694;
>> ERROR: missing chunk number 1 for toast value 7685119
>> sfee=# select LENGTH(bin_data) from artifact_file LIMIT 1 OFFSET 694;
>> ERROR: missing chunk number 1 for toast value 7685119
>>
>> How would i get the key of row 694?
>
> does that table have any OTHER fields than the one that is knowingly
> corrupted?
yes, its got several other integer & text datatype fields.
From | Date | Subject | |
---|---|---|---|
Next Message | Dennis Gearon | 2003-04-07 05:55:01 | chron scripts and pgsql |
Previous Message | Joel Rees | 2003-04-07 01:52:24 | Re: Single Byte values |