RE: FATAL 1: btree: items are out of order (leftmost 0, stack 48, update 2)

From: "Michael Miyabara-McCaskey" <mykarz(at)miyabara(dot)com>
To: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-sql(at)postgresql(dot)org>, <pgsql-admin(at)postgresql(dot)org>
Subject: RE: FATAL 1: btree: items are out of order (leftmost 0, stack 48, update 2)
Date: 2001-02-08 06:22:17
Message-ID: 000201c09197$7ca12a40$c700a8c0@ncc1701e
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-sql

Tom,

Once again you are a lifesaver.

Thank you. I ended up just dropping all the indexes on the table in
question, and life is now good.

-Michael

> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
> Sent: Wednesday, February 07, 2001 4:42 PM
> To: mykarz(at)miyabara(dot)com
> Cc: pgsql-sql(at)postgresql(dot)org; pgsql-admin(at)postgresql(dot)org
> Subject: Re: [ADMIN] FATAL 1: btree: items are out of order
> (leftmost 0,
> stack 48, update 2)
>
>
> "Michael Miyabara-McCaskey" <mykarz(at)miyabara(dot)com> writes:
> > FATAL 1: btree: items are out of order (leftmost 0, stack
> 48, update 2)
>
> This appears to indicate that you've got a corrupted index,
> possibly due
> to carelessness about starting the postmaster always in the
> same locale
> (see past discussions about effects of locale on index sort order).
>
> If you can determine which index is broken, dropping and rebuilding it
> should get you out of trouble.
>
> regards, tom lane
>

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Víctor López 2001-02-08 14:12:37 Error with LEX code generation on hpux10.20
Previous Message Tom Lane 2001-02-08 00:41:31 Re: FATAL 1: btree: items are out of order (leftmost 0, stack 48, update 2)

Browse pgsql-sql by date

  From Date Subject
Next Message Jan Wieck 2001-02-08 09:38:44 Re: Hrm...why is this wrong?
Previous Message Nathan Myers 2001-02-08 05:33:47 Re: PL/pgsql EXECUTE 'SELECT INTO ...'