From 0b746a7d0505e9086a8ce457a75bd38b786fdbbe Mon Sep 17 00:00:00 2001 From: "Marc G. Fournier" Date: Fri, 10 Apr 1998 18:43:30 +0000 Subject: [PATCH] See if I can determine where the BTP_CHAIN error is coming from... --- src/backend/access/nbtree/nbtsearch.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/src/backend/access/nbtree/nbtsearch.c b/src/backend/access/nbtree/nbtsearch.c index 5729cafe71..fd046a4e82 100644 --- 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))