From: | "Aaron Harsh" <ajh(at)rentrak(dot)com> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | BUG #1800: "unexpected chunk number" during pg_dump |
Date: | 2005-08-01 05:02:30 |
Message-ID: | 20050801050230.EECDAF0B09@svr2.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The following bug has been logged online:
Bug reference: 1800
Logged by: Aaron Harsh
Email address: ajh(at)rentrak(dot)com
PostgreSQL version: 7.4.6
Operating system: RedHat ES release 3, x86_64
Description: "unexpected chunk number" during pg_dump
Details:
Our regular pg_dump aborted this afternoon with this output:
pg_dump: ERROR: unexpected chunk number 0 (expected 1) for toast value
4294879152
pg_dump: SQL command to dump the contents of table "dataset_cache" failed:
PQendcopy() failed.
pg_dump: Error message from server: ERROR: unexpected chunk number 0
(expected 1) for toast value 4294879152
pg_dump: The command was: COPY public.dataset_cache (checksum, version_no,
bind_params, sql_statement, serialized_value, date_created) TO stdout;
pg_dump: *** aborted because of error
We saw the same message when we tried to cluster the effective table. The
problem went away after truncating the table.
I've searched the pgsql-bugs archives and found reports of this problem, but
haven't seen a solution. Is there a solution to keep this from happening in
the future? (Version upgrade maybe?)
From | Date | Subject | |
---|---|---|---|
Next Message | Sivaraman K.G | 2005-08-01 05:24:53 | postmaster graceful shutdown time !!! |
Previous Message | Brian Herlihy | 2005-08-01 03:38:23 | Problem with large number of index conditions |