mirror of
https://github.com/MariaDB/server.git
synced 2025-01-25 00:04:33 +01:00
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.
This commit is contained in:
parent
42a77e858b
commit
66241d5a8d
2 changed files with 7 additions and 2 deletions
|
@ -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(
|
||||
|
|
|
@ -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);
|
||||
|
|
Loading…
Add table
Reference in a new issue