Received: from trends.net (root@clio.trends.ca [209.47.148.2]) by hub.org (8.9.3/8.9.1) with ESMTP id XAA00714 for ; Tue, 27 Apr 1999 23:17:21 -0400 (EDT) (envelope-from vadim@krs.ru) Received: from sunpine.krs.ru (SunPine.krs.ru [195.161.16.37]) by trends.net (8.8.8/8.8.8) with ESMTP id WAA27175 for ; Tue, 27 Apr 1999 22:58:27 -0400 (EDT) Received: from krs.ru (dune.krs.ru [195.161.16.38]) by sunpine.krs.ru (8.8.8/8.8.8) with ESMTP id KAA26796; Wed, 28 Apr 1999 10:51:43 +0800 (KRSS) Sender: root@sunpine.krs.ru Message-ID: <372677BF.C05E1E25@krs.ru> Date: Wed, 28 Apr 1999 10:51:43 +0800 From: Vadim Mikheev Organization: OJSC Rostelecom (Krasnoyarsk) X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-RELEASE i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: Matthew Hagerty CC: pgsql-interfaces@postgresql.org Subject: Re: [INTERFACES] Error message btree: BTP_CHAIN References: <4.1.19990427173747.00bba100@mail.venux.net> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Matthew Hagerty wrote: > > Can someone explain this error I get in my postgres.log while trying to run > a simple query (select * from table) on a table that has this index: > > FATAL 1: btree: BTP_CHAIN flag was expected in site_login_user (access = > bt_read) > > What is the BTP_CHAIN and how did it get set? I'm trying to figure out > what the user could have done to cause this (and how I can fix it.) We have fix for that from Hiroshi Inoue. Patch for 6.4.2 will appear in a few days... Rebuild your index. Vadim