Search Results
https://dev.mysql.com/doc/internals/en/selectexplain.html
For an EXPLAIN statement, for every SELECT, mysql_select will be called with option SELECT_DESCRIBE. For every SELECT in a given union, mysql_explain_union will call mysql_explain_select. mysql_select creates a JOIN for select if it does not ...
https://dev.mysql.com/doc/internals/en/semi-sync-replication.html
The clients COMMIT (or in auto-commit mode the current statement) waits until _one_ slave acknowledged that it received (not neccesarilly executed) the transaction or a timeout is reached. In MySQL 5.5 replication can optionally be made ...
https://dev.mysql.com/doc/internals/en/sleep.html
One solution is to use the 'sleep' command of 'mysqltest' in front of the SQL statement that drives the remaining thread into the critical code. In some cases race conditions can be repeated when all but one thread are blocked (for example waiting ...
https://dev.mysql.com/doc/internals/en/storage-engine-options.html
A shared module must be installed using the INSTALL PLUGIN statement or the --plugin-load option before it can be used. Storage engines are plugins, so the options that control plugin building specify which storage engines to build. The ...
https://dev.mysql.com/doc/internals/en/store-lock.html
The idea with handler::store_lock() is the following: The statement decided which locks we should need for the table for updates/deletes/inserts we get WRITE locks, for SELECT... Synopsis virtual THR_LOCK_DATA ** store_lock ( thd, to, lock_type); ...
https://dev.mysql.com/doc/internals/en/stored-procedures.html
In MySQL 5.0 the protocol was extended to handle: multi-resultset multi-statement .
https://dev.mysql.com/doc/internals/en/support-for-insert.html
Once you have read support in your storage engine, the next feature to implement is support for INSERT statements. With INSERT support in place, your storage engine can handle WORM (write once, read many) applications such as logging and archiving ...
https://dev.mysql.com/doc/internals/en/test-faults-usage.html
SET SESSION debug="+d,function_crash_return"; will crash the server while returning from function.
https://dev.mysql.com/doc/internals/en/traceable-queries.html
If one of those statements is prepared and executed in separate steps, preparation and execution are separately traced. They are: SELECT; INSERT or REPLACE (with VALUES or SELECT); UPDATE/DELETE and their multi-table variants; all the previous ones ...
https://dev.mysql.com/doc/internals/en/transaction-management.html
In each client connection, MySQL maintains two transactional states: A statement transaction A standard transaction, also called a normal transaction .