Commit 44b670f6 authored by unknown's avatar unknown

Small fixes in the manual.


BitKeeper/etc/ignore:
  Added sql-bench/compare-results-all sql-bench/template.html to the ignore list
Docs/manual.texi:
  Changed innodb_unix_file_flush_method -> innodb_flush_method.
parent 14289d42
...@@ -284,3 +284,5 @@ support-files/mysql.spec ...@@ -284,3 +284,5 @@ support-files/mysql.spec
tags tags
tmp/* tmp/*
sql-bench/gif/* sql-bench/gif/*
sql-bench/compare-results-all
sql-bench/template.html
...@@ -25727,7 +25727,7 @@ in its own lock table and rolls back the transaction. If you use ...@@ -25727,7 +25727,7 @@ in its own lock table and rolls back the transaction. If you use
than InnoDB in the same transaction, then a deadlock may arise which than InnoDB in the same transaction, then a deadlock may arise which
InnoDB cannot notice. In cases like this the timeout is useful to InnoDB cannot notice. In cases like this the timeout is useful to
resolve the situation. resolve the situation.
@item @code{innodb_unix_file_flush_method} @tab @item @code{innodb_flush_method} @tab
(Available from 3.23.39 up.) (Available from 3.23.39 up.)
The default value for this is @code{fdatasync}. The default value for this is @code{fdatasync}.
Another option is @code{O_DSYNC}. Another option is @code{O_DSYNC}.
...@@ -26338,7 +26338,7 @@ In some versions of Linux and Unix, flushing files to disk with the Unix ...@@ -26338,7 +26338,7 @@ In some versions of Linux and Unix, flushing files to disk with the Unix
@code{fdatasync} and other similar methods is surprisingly slow. @code{fdatasync} and other similar methods is surprisingly slow.
The default method InnoDB uses is the @code{fdatasync} function. The default method InnoDB uses is the @code{fdatasync} function.
If you are not satisfied with the database write performance, you may 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. 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 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 InnoDB does not call the file flush for every write it does to a
...@@ -42520,6 +42520,9 @@ For more information on Object Oriented Programming ...@@ -42520,6 +42520,9 @@ For more information on Object Oriented Programming
@uref{http://language.perl.com/info/documentation.html} @uref{http://language.perl.com/info/documentation.html}
@end example @end example
Note that if you want to use transactions with Perl, you need to have
@code{Msql-Mysql-modules} version 1.2216 or newer.
Installation instructions for @strong{MySQL} Perl support are given in Installation instructions for @strong{MySQL} Perl support are given in
@ref{Perl support}. @ref{Perl support}.
...@@ -45730,7 +45733,8 @@ Our TODO section contains what we plan to have in 4.0. @xref{TODO MySQL 4.0}. ...@@ -45730,7 +45733,8 @@ Our TODO section contains what we plan to have in 4.0. @xref{TODO MySQL 4.0}.
@itemize @bullet @itemize @bullet
@item @item
Added support for symbolic links to @code{MyISAM} tables. Added support for symbolic links to @code{MyISAM} tables. Symlink handling is
now enabled by default for Windows.
@item @item
Added @code{SQL_CALC_FOUND_ROWS} and @code{FOUND_ROWS()}. This makes it Added @code{SQL_CALC_FOUND_ROWS} and @code{FOUND_ROWS()}. This makes it
possible to know how many rows a query would have returned possible to know how many rows a query would have returned
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment