| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
| Cc: | Henrik Steffen <steffen(at)city-map(dot)de>, Andrew Sullivan <andrew(at)libertyrms(dot)info>, pg <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Serious Crash last Friday |
| Date: | 2002-07-10 15:56:03 |
| Message-ID: | 25607.1026316563@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Jan Wieck <JanWieck(at)Yahoo(dot)com> writes:
> The fact that the backend cannot open a segment of a TOAST table raises
> the question "how did it get removed?".
I am guessing that the segment never existed, and that the real problem
is corruption of an entry in the TOAST table's index. A bad record
number in an index tuple's heap pointer could produce this symptom.
It might be worth dumping the TOAST index with pg_filedump or some such
tool and looking for silly block numbers. Examining the pattern of
corruption on the bad page, once found, might give us some hint how it
happened.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2002-07-10 15:56:27 | Re: (A) native Windows port |
| Previous Message | Hannu Krosing | 2002-07-10 15:54:15 | Re: (A) native Windows port |