Re: pg_dump error... Follow up

On 7/9/05 10:50 am, "Adam Witney" <awitney(at)sgul(dot)ac(dot)uk> wrote:

>
> Hi,
>
> I just ran into an error from pg_dump:
>
> /usr/local/pgsql/bin/pg_dump -F p my_db
>
> pg_dump: ERROR: unexpected chunk number 3292 (expected 5) for toast value
> 144391872
> pg_dump: SQL command to dump the contents of table "measured_bioassay_base"
> failed: PQendcopy() failed.
> pg_dump: Error message from server: ERROR: unexpected chunk number 3292
> (expected 5) for toast value 144391872
> pg_dump: The command was: COPY public.measured_bioassay_base (bioassay_id,
> name, owner_id, writer_id, readers_id, is_deleted, delete_time, expt_id,
> protocol_application_id, source_bioassay_id, filename, fileheader, format,
> date_uploaded) TO stdout;
>
> Any ideas whats happened here? It looks like one of my tables hasn't backed
> up correctly. This table has a text field which contains large amounts of
> data per field. The dump file is much smaller than last nights dump.
>
> (PostgreSQL 7.4.8 on i686-pc-linux-gnu, compiled by GCC 2.95.4)

I think I have found the offending row in measured_bioassay_base... The
entry in its toast table looks like this

bugasbase2=# select chunk_id, chunk_seq, length(chunk_data) from
pg_toast.pg_toast_134401982 where chunk_id = 144391872;
chunk_id | chunk_seq | length
-----------+-----------+--------
144391872 | 0 | 1998
144391872 | 1 | 1998
144391872 | 2 | 1998
144391872 | 3 | 1998
144391872 | 4 | 1998
7625296 | 3292 | 24
7625297 | 3292 | 24
7625298 | 3292 | 24
7625299 | 3292 | 24
7625308 | 3292 | 19
7625309 | 3292 | 16
7625310 | 3292 | 16
7625311 | 3292 | 20
7625320 | 3292 | 20
7625321 | 3292 | 19
7625322 | 3292 | 19
7625323 | 3292 | 20
7625332 | 3292 | 19
7625333 | 3292 | 19
7625334 | 3292 | 19
7625335 | 3292 | 19
7625344 | 3292 | 20
7625345 | 3292 | 20
7625346 | 3292 | 18
7625347 | 3292 | 18
7625356 | 3292 | 19
7625357 | 3292 | 19
7625358 | 3292 | 18
7625359 | 3292 | 20
7625368 | 3292 | 19
7625369 | 3292 | 20
7625370 | 3292 | 20
7625371 | 3292 | 20
7625380 | 3292 | 19
7625381 | 3292 | 19
7625382 | 3292 | 19
7625383 | 3292 | 19
144391872 | 37 | 1998
144391872 | 38 | 1998
144391872 | 39 | 1998
.. 200 more rows..

I can delete the row in measured_bioassay_base and reload the data for it,
but i'd like to know if it is a symptom of a bigger problem, any ideas how
this might have happened?

Thanks for any help

Adam

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.