PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 296.5Kb
Man Pages (Zip)
- 401.9Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/innodb-information-schema-examples.html
Identifying Blocking Transactions It is sometimes helpful to identify which transaction blocks another. SELECT THREAD_ID, SQL_TEXT FROM performance_schema.events_statements_history WHERE THREAD_ID = 28 ORDER BY EVENT_ID; Correlating InnoDB ... Note ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-information-schema-internal-data.html
Data retrieved from the lock tables exists when the SELECT is executed, but might be gone or changed by the time the query result is consumed by the client. Note This section describes locking information as exposed by the Performance Schema ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-information-schema-understanding-innodb-locking.html
At any given time, a transaction may request a lock that is held by another transaction, in which case it is blocked by that other transaction. Note This section describes locking information as exposed by the Performance Schema data_locks and ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-init-startup-configuration.html
Normally, InnoDB is initialized when the MySQL server is started for the first time. The first decisions to make about InnoDB configuration involve the configuration of data files, log files, page size, and memory buffers, which should be ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-introduction.html
InnoDB is a general-purpose storage engine that balances high reliability and high performance. Unless you have configured a different default storage engine, issuing a CREATE TABLE statement without an ENGINE clause creates an InnoDB table. Key ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-linux-native-aio.html
With synchronous I/O, query threads queue I/O requests, and InnoDB background threads retrieve the queued requests one at a time, issuing a synchronous I/O call for each. InnoDB uses the asynchronous I/O subsystem (native AIO) on Linux to perform ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-locking-reads.html
Here, FOR SHARE is not a good solution because if two users read the counter at the same time, at least one of them ends up in deadlock when it attempts to update the counter. If you query data and then insert or update related data within the same ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-memcached-porting-memcached.html
Changes to the innodb_memcache.containers table take effect the next time the innodb_memcache.containers table is queried. This is because InnoDB performs best for large-scale insertions if primary key values are added in sorted order (as they are ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-memcached-porting-mysql.html
The results are already converted; # no need to repeat conversion functions and WHERE clauses each time. mysql> INSERT INTO innodb_memcache.containers (name,db_schema,db_table,key_columns,value_columns,flags,cas_column, ... Consider these aspects of ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-migration.html
In conjunction with the MySQL binary log, you can perform point-in-time recovery. This section describes techniques for moving or copying some or all InnoDB tables to a different server or instance. For example, you might move an entire MySQL ...