From: | Greg Sabino Mullane <greg(at)endpoint(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Btree or not btree? That is the question |
Date: | 2012-06-06 20:09:46 |
Message-ID: | 20120606200945.GW10277@tinybird.home |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jun 04, 2012 at 02:09:44PM -0400, Tom Lane wrote:
> Greg Sabino Mullane <greg(at)endpoint(dot)com> writes:
> > We have a 8.3.18 system (yes, the same one from the previous
> > thread, finally upgraded!) that gave us this error yesterday:
>
> > ERROR: index "pg_class_oid_index" is not a btree
>
> That means you got bogus data while reading the metapage.
> I'm beginning to wonder about the hardware on this server ...
Thanks for the reply. Me too. This is on a cluster[1], so we
do have the luxury of testing the hardware on each box and
shuffling things around. I'm also thinking we need to get away
from the near-constant updating of pg_class, just as a good
measure.
[1] Bruce, yet another usage! :)
--
Greg Sabino Mullane greg(at)endpoint(dot)com
End Point Corporation
PGP Key: 0x14964AC8
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2012-06-06 20:13:33 | Re: Inconsistency in libpq connection parameters, and extension thereof |
Previous Message | Magnus Hagander | 2012-06-06 20:08:26 | Re: Inconsistency in libpq connection parameters, and extension thereof |