I had this problem a few weeks ago.
What I did was isolate it into an individual row that was causing the problem, then going over the fields one by one, till I located the free text field that was responsible.
Then I repopulated it with the value in the latest backup I could find.
I wasn’t able to find any better techniques on the web.
For locating the faulty row, you might want to write a procedural routine that will query rows sequentially.
I did it in a very crude way by using LIMIT statements till I hit the mark.
As to why this happens, the suggestion I got here was faulty hardware.
Good luck
From: pgsql-general-owner@postgresql.org [mailto:pgsql-general-owner@postgresql.org] On Behalf Of Andrzej Folek
Sent: Saturday, August 26, 2006 3:47 AM
To: pgsql-general@postgresql.org
Subject: [GENERAL] mising chunk
I've got a problem with conversion.
Database is running on pg8.1.3
I've 2 tables, in one there is mediabinary collumn of bytea type. And during conversion to another table / conversion only move data from timestamp type to timestamptz but mediabinary in botha are the same. And during query which move data I recieve ' MISSING CHUNK NUMBER 0 FOR TOAST VALUE .. I've re-index this table, vacumed and nothing. Everytime I get this info.
Please give me some advice how to fix this or even drop data to file I don't know, any suggestion????