See if I can determine where the BTP_CHAIN error is coming from...

diff --git a/src/backend/access/nbtree/nbtsearch.c b/src/backend/access/nbtree/nbtsearch.c
index 5729cafe71f128dcf66e1bf5f5dcf4119d916ecf..fd046a4e82da1fcf4fb0ccbe58f63e43b109f4e2 100644 (file)
--- a/src/backend/access/nbtree/nbtsearch.c
+++ b/src/backend/access/nbtree/nbtsearch.c
@@ -7,7 +7,7 @@
  *
  *
  * IDENTIFICATION
- *       $Header: /cvsroot/pgsql/src/backend/access/nbtree/nbtsearch.c,v 1.31 1998/02/26 04:29:50 momjian Exp $
+ *       $Header: /cvsroot/pgsql/src/backend/access/nbtree/nbtsearch.c,v 1.32 1998/04/10 18:43:30 scrappy Exp $
  *
  *-------------------------------------------------------------------------
  */
@@ -219,7 +219,8 @@ _bt_moveright(Relation rel,
                                                if (_bt_skeycmp(rel, keysz, scankey, page,
                                                                                PageGetItemId(page, P_FIRSTKEY),
                                                                                BTEqualStrategyNumber))
-                                                       elog(FATAL, "btree: BTP_CHAIN flag was expected");
+                                                       elog(FATAL, "btree: BTP_CHAIN flag was expected (access = %d)", 
+                                                                               access);
                                                if (_bt_skeycmp(rel, keysz, scankey, page,
                                                                                PageGetItemId(page, offmax),
                                                                                BTEqualStrategyNumber))