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/locking-issues.html
External locking occurs when the server and other programs lock MyISAM table files to coordinate among themselves which program can access the tables at which time. MySQL manages contention for table contents using locking: Internal locking is ...
https://dev.mysql.com/doc/refman/8.0/en/memory-use.html
A buffer pool that is too small may cause excessive churning as pages are flushed from the buffer pool only to be required again a short time later. The memory is only allocated when needed, but it might be used if your replication topology handles ... MySQL allocates buffers and caches to improve performance of database ...
https://dev.mysql.com/doc/refman/8.0/en/monitoring-performance-schema.html
You can query the tables in the performance_schema database to see real-time information about the performance characteristics of your server and the applications it is running.
https://dev.mysql.com/doc/refman/8.0/en/multiple-server-clients.html
If you normally use a specific socket file or port number, you can place commands to set these environment variables in your .login file so that they apply each time you log in. Start the client with --protocol=TCP to connect using TCP/IP, ...
https://dev.mysql.com/doc/refman/8.0/en/myisam-check.html
This may take a long time for a large table that has many indexes. To check a MyISAM table, use the following commands: myisamchk tbl_name This finds 99.99% of all errors. What it cannot find is corruption that involves only the data file (which is ...
https://dev.mysql.com/doc/refman/8.0/en/myisam-key-cache.html
To make this choice easier, the key cache module maintains all used blocks in a special list (LRU chain) ordered by time of use. To minimize disk I/O, the MyISAM storage engine exploits a strategy that is used by many database management systems.
https://dev.mysql.com/doc/refman/8.0/en/myisam-repair.html
Stage 1: Checking your tables Run myisamchk *.MYI or myisamchk -e *.MYI if you have more time. The discussion in this section describes how to use myisamchk on MyISAM tables (extensions .MYI and .MYD). You can also use the CHECK TABLE and REPAIR ...
https://dev.mysql.com/doc/refman/8.0/en/myisam-start.html
If the repair fails because of an error in the data file (for example, a duplicate-key error), the server tries again, this time re-creating the data file. The following options to mysqld can be used to change the behavior of MyISAM tables.
https://dev.mysql.com/doc/refman/8.0/en/myisam-table-maintenance.html
With myisamchk, you must make sure that the server does not use the tables at the same time so that there is no unwanted interaction between myisamchk and the server. This section discusses how to use myisamchk to check or repair MyISAM tables ...
https://dev.mysql.com/doc/refman/8.0/en/myisamchk-other-options.html
(The first time you use this option to sort a table, it may be very slow.) To determine a table's index numbers, use SHOW INDEX, which displays a table's indexes in the same order that myisamchk sees them. myisamchk supports the following options ...