Re: unable to dump database, toast errors
От | Jan Wieck |
---|---|
Тема | Re: unable to dump database, toast errors |
Дата | |
Msg-id | 3E90C649.B2D350DB@Yahoo.com обсуждение исходный текст |
Ответ на | Re: unable to dump database, toast errors (Lonni Friedman <lfriedman@vasoftware.com>) |
Ответы |
Re: unable to dump database, toast errors
|
Список | 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 по дате отправления: