> Alvaro Herrera <[EMAIL PROTECTED]> 08/11/05 9:52 AM >>>
> Anyway I was originally thinking the problem data was 4294879152
> (0xFFFEA7B0), not the 0. Have you tried to manually extract the data
> from the dataset_cache table? You could try figuring out what page
> contains the bad data, and man
On Wed, Aug 10, 2005 at 06:07:24PM -0700, Aaron Harsh wrote:
> > >>> Alvaro Herrera <[EMAIL PROTECTED]> 08/10/05 9:03 AM >>>
> > On Mon, Aug 01, 2005 at 06:02:30AM +0100, Aaron Harsh wrote:
> > > pg_dump: ERROR: unexpected chunk number 0 (expected 1) for toast value
> > > ...
> > Looks very much l
> >>> Alvaro Herrera <[EMAIL PROTECTED]> 08/10/05 9:03 AM >>>
> On Mon, Aug 01, 2005 at 06:02:30AM +0100, Aaron Harsh wrote:
> > pg_dump: ERROR: unexpected chunk number 0 (expected 1) for toast value
> > ...
> Looks very much like the table was corrupted. Maybe you should try to
> test your RAM a
Alvaro Herrera wrote:
> Looks very much like the table was corrupted. Maybe you should try to
> test your RAM and disks. Not sure how to do that on x86-64 though,
> unless the test utility at www.memtest86.com has been ported to it.
x86-64 systems will still boot and run 32-bit code fine (altho
On Mon, Aug 01, 2005 at 06:02:30AM +0100, Aaron Harsh wrote:
> 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: unexp
