Re: unable to dump database, toast errors - Mailing list pgsql-general

From Jan Wieck
Subject Re: unable to dump database, toast errors
Date
Msg-id 3E90C649.B2D350DB@Yahoo.com
Whole thread Raw
In response to Re: unable to dump database, toast errors  (Lonni Friedman <lfriedman@vasoftware.com>)
Responses Re: unable to dump database, toast errors  (Lonni Friedman <lfriedman@vasoftware.com>)
List pgsql-general
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?


Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #


pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Consecutive queries
Next
From: Bruce Momjian
Date:
Subject: Re: PHP as PL