From 66241d5a8d8e2fda6639e261da1ed2853b4f8c39 Mon Sep 17 00:00:00 2001
From: osku <Unknown>
Date: Mon, 28 Aug 2006 06:15:42 +0000
Subject: [PATCH] btr_cur_search_to_nth_level(): Document where cursor is left
 at in PAGE_CUR_LE searches.

page_validate(): Add missing space to error print.
---
 btr/btr0cur.c    | 7 ++++++-
 page/page0page.c | 2 +-
 2 files changed, 7 insertions(+), 2 deletions(-)

diff --git a/btr/btr0cur.c b/btr/btr0cur.c
index 7d62571284f..0d22a04e803 100644
--- a/btr/btr0cur.c
+++ b/btr/btr0cur.c
@@ -237,7 +237,12 @@ NOTE: n_fields_cmp in tuple must be set so that it cannot be compared
 to node pointer page number fields on the upper levels of the tree!
 Note that if mode is PAGE_CUR_LE, which is used in inserts, then
 cursor->up_match and cursor->low_match both will have sensible values.
-If mode is PAGE_CUR_GE, then up_match will a have a sensible value. */
+If mode is PAGE_CUR_GE, then up_match will a have a sensible value.
+
+If mode is PAGE_CUR_LE , cursor is left at the place where an insert of the
+search tuple should be performed in the B-tree. InnoDB does an insert
+immediately after the cursor. Thus, the cursor may end up on a user record,
+or on a page infimum record. */
 
 void
 btr_cur_search_to_nth_level(
diff --git a/page/page0page.c b/page/page0page.c
index a7a0dd4b788..39d1d6749f2 100644
--- a/page/page0page.c
+++ b/page/page0page.c
@@ -1811,7 +1811,7 @@ page_validate(
 			if (!(1 == cmp_rec_rec(rec, old_rec,
 					offsets, old_offsets, index))) {
 				fprintf(stderr,
-				"InnoDB: Records in wrong order on page %lu",
+				"InnoDB: Records in wrong order on page %lu" ,
 					(ulong) buf_frame_get_page_no(page));
 				dict_index_name_print(stderr, NULL, index);
 				fputs("\nInnoDB: previous record ", stderr);