page0cur.ic Fix a bug in insert buffer and multiversioning

monty@hundin.mysql.fi

heikki@donna.mysql.fi

than InnoDB in the same transaction, then a deadlock may arise which

InnoDB cannot notice. In cases like this the timeout is useful to

resolve the situation.

@item @code{innodb_unix_file_flush_method} @tab

@item @code{innodb_flush_method} @tab

(Available from 3.23.39 up.)

The default value for this is @code{fdatasync}.

Another option is @code{O_DSYNC}.

@code{fdatasync} and other similar methods is surprisingly slow.

The default method InnoDB uses is the @code{fdatasync} function.

If you are not satisfied with the database write performance, you may

try setting @code{innodb_unix_file_flush_method} in @file{my.cnf}

try setting @code{innodb_flush_method} in @file{my.cnf}

to @code{O_DSYNC}, though O_DSYNC seems to be slower on most systems.

You can also try setting it to @code{littlesync}, which means that

InnoDB does not call the file flush for every write it does to a

	ut_ad(dtuple_check_typed(tuple));

	page_cur_search_with_match(page, tuple, mode,

					&low_matched_fields,

					&low_matched_bytes,

					&up_matched_fields,

					&up_matched_bytes,

					&low_matched_fields,

					&low_matched_bytes,

					cursor);

	return(low_matched_fields);

}