Skip site navigation (1) Skip section navigation (2)

Toast "unexpected chunk number" error

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Toast "unexpected chunk number" error
Date: 2004-08-30 17:52:43
Message-ID: 200408301052.43054.josh@agliodbs.com (view raw or flat)
Thread:
Lists: pgsql-bugs
Summary:  User gets "unexpected chunk number" error on pg_dump
Serverity:  Serious
Version:  7.4.5
Platform: Not yet known
Description:
One of my clients has received an "unexpected chunk number" error on pg_dump 
with a TOASTed column of a table.   This sounds suspiciously like an error 
you dealt with on 7.3 last year (8/03) but the list archives are down and I 
can't retrieve what Tom did to fix it/whether it was related to a PG bug.

ERROR:  unexpected chunk number 1 (expected 0) for toast value 126990852

We did some digging, and the problem does not appear to be the index on 
pg_toast:

friend=# select chunk_seq,length(chunk_data) from pg_toast.pg_toast_17165
where chunk_id = 126990852; set enable_indexscan= false; select
chunk_seq,length(chunk_data) from pg_toast.pg_toast_17165 where chunk_id =
126990852;
 chunk_seq | length
-----------+--------
         1 |    608
(1 row)

SET
 chunk_seq | length
-----------+--------
         1 |    608


Thanks for advice.

-- 
Josh Berkus
Aglio Database Solutions
San Francisco

pgsql-bugs by date

Next:From: Tom LaneDate: 2004-08-30 21:31:34
Subject: Re: "pg_restore -d base" cumstom format broken in CVS head?
Previous:From: Tom LaneDate: 2004-08-30 16:38:07
Subject: Re: "pg_restore -d base" cumstom format broken in CVS head?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group