Added missing nodes to InnoDB section (2f7f0982) · Commits · Software / OSDI20 Artifacts / mariadb

Docs/manual.texi

+18 −13

Original line number	Diff line number	Diff line
		@@ -39498,6 +39498,9 @@ transaction.
		* InnoDB Locks set:: Locks Set by Different SQL Statements in InnoDB
		* InnoDB Deadlock detection:: Deadlock Detection and Rollback
		* InnoDB Consistent read example:: An Example of How the Consistent Read Works in InnoDB
		* Innodb deadlocks::
		* Innodb tuning::
		* Innodb Monitor::
		@end menu


		@@ -39718,7 +39721,7 @@ set by the SQL statement may be preserved. This is because InnoDB
		stores row locks in a format where it cannot afterwards know which was
		set by which SQL statement.

		@node InnoDB Consistent read example, , InnoDB Deadlock detection, InnoDB transaction model
		@node InnoDB Consistent read example, Innodb deadlocks, InnoDB Deadlock detection, InnoDB transaction model
		@subsubsection An Example of How the Consistent Read Works in InnoDB

		When you issue a consistent read, that is, an ordinary @code{SELECT}
		@@ -39767,6 +39770,7 @@ use a locking read:
		SELECT * FROM t LOCK IN SHARE MODE;
		@end example

		@node Innodb deadlocks, Innodb tuning, InnoDB Consistent read example, InnoDB transaction model
		@subsubsection How to cope with deadlocks?

		Deadlocks are a classic problem in transactional databases,
		@@ -39811,7 +39815,8 @@ and @code{UNLOCK TABLES} implicitly ends the transaction in a
		@code{COMMIT}.
		@end itemize

		@subsection Performance Tuning Tips
		@node Innodb tuning, Innodb Monitor, Innodb deadlocks, InnoDB transaction model
		@subsubsection Performance Tuning Tips

		@strong{1.}
		If the Unix @file{top} or the Windows @file{Task Manager} shows that
		@@ -39898,11 +39903,12 @@ INSERT INTO yourtable VALUES (1, 2), (5, 5);

		This tip is of course valid for inserts into any table type, not just InnoDB.

		@node Innodb Monitor, , Innodb tuning, InnoDB transaction model
		@subsubsection The InnoDB Monitor

		Starting from version 3.23.41 InnoDB includes the InnoDB
		Monitor which prints information on the InnoDB internal state.
		When swithed on, InnoDB Monitor
		When switched on, InnoDB Monitor
		will make the MySQL server @file{mysqld} to print data
		(note: the MySQL client will not print anything)
		to the standard
		@@ -40149,13 +40155,12 @@ index. Note that if the primary key is long, the secondary indexes
		will use more space.

		@menu
		* InnoDB physical structure:: Physical Structure of an Index
		* InnoDB Insert buffering:: Insert Buffering
		* InnoDB Adaptive hash:: Adaptive Hash Indexes
		* InnoDB Physical record:: Physical Record Structure
		* InnoDB physical structure::
		* InnoDB Insert buffering::
		* InnoDB Adaptive hash::
		* InnoDB Physical record::
		@end menu


		@node InnoDB physical structure, InnoDB Insert buffering, Table and index, Table and index
		@subsubsection Physical Structure of an Index

		@@ -46131,7 +46136,7 @@ is not the case, you should run the script

		@menu
		* UDF calling:: UDF Calling Sequences
		* UDF aggr. calling :: UDF Calling Sequences for aggregate functions
		* UDF aggr. calling::
		* UDF arguments:: Argument Processing
		* UDF return values:: Return Values and Error Handling
		* UDF compiling:: Compiling and Installing User-definable Functions
		@@ -47661,7 +47666,7 @@ limits! In this case you should start @code{safe_mysqld} with @code{sh}!
		@menu
		* Link errors:: Problems When Linking with the MySQL Client Library
		* Changing MySQL user:: How to Run MySQL As a Normal User
		* File permissions :: Problems with File Permissions
		* File permissions::
		@end menu

		@node Link errors, Changing MySQL user, Installation Issues, Installation Issues