| From: | "Aaron Harsh" <ajh(at)rentrak(dot)com> |
|---|---|
| To: | <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #1800: "unexpected chunk number" during pg_dump |
| Date: | 2005-08-11 20:41:01 |
| Message-ID: | s2fb5591.095@rtk_mail_1.rentrak.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> 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 manually peek into it using pg_filedump.
Unfortunately, the table doesn't show any problems now (I truncated it after the pg_dump failed)and so there's not a lot of further detail I can give you. I suppose this means that we'll have to wait until such time as the problem shows up again before we can continue.
Thanks for your help.
--
Aaron Harsh
ajh(at)rentrak(dot)com
503-284-7581 x347
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bernard | 2005-08-11 23:18:49 | BUG #1820: Installation: Dependency failure |
| Previous Message | Tom Lane | 2005-08-11 18:20:39 | Re: [8.0.0] out of memory on large UPDATE |