Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f180fpx22803; Wed, 7 Feb 2001 19:41:51 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f180fV909843; Wed, 7 Feb 2001 19:41:31 -0500 (EST) To: mykarz@miyabara.com cc: pgsql-sql@postgresql.org, pgsql-admin@postgresql.org Subject: Re: FATAL 1: btree: items are out of order (leftmost 0, stack 48, update 2) In-reply-to: <000601c09157$2488eef0$8600a8c0@hubstorm.com> References: <000601c09157$2488eef0$8600a8c0@hubstorm.com> Comments: In-reply-to "Michael Miyabara-McCaskey" message dated "Wed, 07 Feb 2001 14:41:41 -0800" Date: Wed, 07 Feb 2001 19:41:31 -0500 Message-ID: <9840.981592891@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200102/59 X-Sequence-Number: 659 "Michael Miyabara-McCaskey" 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