Re: [GENERAL] "FATAL 1: my bits moved right off the end of theworld!"

From: Ed Loehr <ELOEHR(at)austin(dot)rr(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] "FATAL 1: my bits moved right off the end of theworld!"
Date: 1999-12-01 00:06:27
Message-ID: 38446682.4746C051@austin.rr.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Peter Eisentraut wrote:

> This is getting to be our favourite error message...
>
> It is caused by a corrupted B-Tree index. Drop and recreate that one.

Thanks. Unfortunately, the lack of context to the error message makes it difficult
to identify which index is "that one." The message was last showing up during the
process of dropping/recreating a series of triggers and functions via "psql -f"
without any table inserts/updates.

Cheers.
Ed Loehr

>
>
> On Tue, 30 Nov 1999, Ed Loehr wrote:
>
> > I have run into this error message a few times now in various circumstances
> > (using pgsql v6.5.2 on Linux 2.2.5-15smp):
> >
> > "FATAL 1: my bits moved right off the end of the world!"
> >
> > Does anyone have a clue as to what scenarios cause this? (It apparently comes
> > from line 506 of .../src/backend/access/nbtree/nbtpage.c)
> >
> > I've had the luxury of being early in development and being able to rebuild my
> > DB to remove the symptom, but that will soon change.
> >
> > Thanks in advance,
> > Ed Loehr
> >
> >
> > ************
> >
> >
>
> --
> Peter Eisentraut Sernanders vaeg 10:115
> peter_e(at)gmx(dot)net 75262 Uppsala
> http://yi.org/peter-e/ Sweden
>
> ************

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ed Loehr 1999-12-01 00:10:09 Re: [GENERAL] Date & Time
Previous Message kaiq 1999-12-01 00:04:30 Re: [GENERAL] Date & Time