From: | Richard Broersma Jr <rabroersma(at)yahoo(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | General PostgreSQL List <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pg_dumpall failing from possible corrupted shared memory |
Date: | 2006-10-27 21:28:08 |
Message-ID: | 728090.94812.qm@web31813.mail.mud.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> Richard Broersma Jr <rabroersma(at)yahoo(dot)com> writes:
> >> Are you interested in dumping out the page of pg_index that
> >> contains this record, using pg_filedump?
>
> > I've attached the results.log to the email.
>
> Well, there's our smoking gun:
> 1bfc: 74746e6f 00000000 00000000 1c000000 ttno............
> ^^^^^^^^^^^^^^^^^^^^^^^^^^
> 1c0c: 01000000 00000000 1a000000 6d6f6420 ............mod
> ^^^^^^^^^^^^^^^^^^^^^^^^^^
> The underlined stuff has overwritten what should be expression dump
> text.
>
> Seeing that the corruption begins at page offset 1c00 --- that is,
> exactly on a 1K boundary --- I'm a bit inclined to suspect a disk
> I/O glitch. You might want to run some hardware diagnostics on
> your machine.
Thanks Tom for helping me through this mental exercise. Yes, I would agree my server hardware is
suspect and should be replaced concidering with the above evidence.
Regards,
Richard Broersma Jr.
From | Date | Subject | |
---|---|---|---|
Next Message | John Cobo | 2006-10-27 21:35:06 | Wrong record type - caused by SELECT order ??? |
Previous Message | Russ Brown | 2006-10-27 21:22:36 | Re: Simple OUTER JOIN doubt |