| From: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | Laurette Cisneros <laurette(at)nextbus(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: index corruption? |
| Date: | 2003-03-31 22:38:12 |
| Message-ID: | 200303311538.12045.pgsql@bluepolka.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Feb 13, 2003, Tom Lane wrote:
>
> Laurette Cisneros <laurette(at)nextbus(dot)com> writes:
> > This is the error in the pgsql log:
> > 2003-02-13 16:21:42 [8843] ERROR: Index external_signstops_pkey is
> > not a btree
>
> This says that one of two fields that should never change, in fixed
> positions in the first block of a btree index, didn't have the right
> values. I am not aware of any PG bugs that could overwrite those
> fields. I think the most likely bet is that you've got hardware
> issues ... have you run memory and disk diagnostics lately?
I am seeing this same problem on two separate machines, one brand new, one
older. Not sure yet what is causing it, but seems pretty unlikely that it
is hardware-related.
Ed
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ed L. | 2003-03-31 22:41:27 | Re: index corruption? |
| Previous Message | Tatsuo Ishii | 2003-03-31 22:37:26 | optimizer cost calculation problem |