The standard binary distributions are ready to run at any installation location, but you might require even more flexibility to place MySQL components where you want.
You want to configure mysqld with features that might not be included in the standard binary distributions. Here is a list of the most common extra options used to ensure feature availability:. For additional information, see Section 2. You want to configure mysqld without some features that are included in the standard binary distributions. For example, distributions normally are compiled with support for all character sets.
If you want a smaller MySQL server, you can recompile it with support for only the character sets you need. For this purpose, obtain a source distribution. Source distributions contain more tests and examples than binary distributions. General Installation Guidance. Verifying the MD5 Checksum. Signature Checking Using Gpg4win for Windows.
Compiler-Specific Build Characteristics. Choosing an Installation Package. Extracting the Install Archive. The audit log plugin included in MySQL Enterprise Edition now has the capability of filtering audited events based on user account and event status. Several new system variables provide DBAs with filtering control. In addition, audit log plugin reporting capability has been improved by the addition of several status variables. These functions enable Enterprise applications to perform the following operations:.
Implement added data protection using public-key asymmetric cryptography. Use cryptographic hashing for digital signing and data verification and validation.
This helps harden MySQL Server against attacks such as SQL injection or attempts to exploit applications by using them outside of their legitimate query workload characteristics.
Changes to server defaults. Beginning with MySQL 5. The motivation for these changes is to provide better out-of-box performance and to reduce the need for database administrators to change settings manually. For more information, see Section 5. InnoDB enhancements. These InnoDB enhancements were added:. These enhancements are known collectively as online DDL. This enhancement provides the flexibility to createtables in locations that better suit your server environment.
After copying the. This enhancement provides the flexibility to move tables that reside in file-per-table tablespaces around to better suit your server environment. You specify the size when creating the MySQL instance. All InnoDB tablespaces within an instance share the same page size. The new algorithm and default configuration values are expected to improve performance and concurrency for most users.
These simple operations to store and retrieve data avoid the SQL overhead such as parsing and constructing a query execution plan. Optimizer statistics for InnoDB tables are gathered at more predictable intervals and can persist across server restarts, for improved plan stability. You can also control the amount of sampling done for InnoDB indexes, to make the optimizer statistics more accurate and improve the query execution plan. New optimizations apply to read-only transactions , improving performance and concurrency for ad-hoc queries and report-generating applications.
See Section 8. You can move the InnoDB undo log out of the system tablespace into one or more separate tablespaces. For details, see Section The --innodb-read-only option lets you run a MySQL server in read-only mode. You can access InnoDB tables on read-only media such as a DVD or CD, or set up a data warehouse with multiple instances all sharing the same data directory. You can also control whether compressed pages in the buffer pool are stored in the redo log when an update operation causes pages to be compressed again.
Data blocks in an InnoDB compressed table contain a certain amount of empty space padding to allow DML operations to modify the row data without re-compressing the new values. Too much padding can increase the chance of a compression failure, requiring a page split, when the data does need to be re-compressed after extensive changes.
The amount of padding can now be adjusted dynamically, so that DBAs can reduce the rate of compression failures without re-creating the entire table with new parameters, or re-creating the entire instance with a different page size. To ease the memory load on systems with huge numbers of tables, InnoDB now frees up the memory associated with an opened table using an LRU algorithm to select tables that have gone the longest without being accessed.
InnoDB has several internal performance enhancements, including reducing contention by splitting the kernel mutex, moving flushing operations from the main thread to a separate thread, enabling multiple purge threads, and reducing contention for the buffer pool on large-memory systems. InnoDB uses a new, faster algorithm to detect deadlocks. To avoid a lengthy warmup period after restarting the server, particularly for instances with large InnoDB buffer pools , you can reload pages into the buffer pool immediately after a restart.
MySQL can dump a compact data file at shutdown, then consult that data file to find the pages to reload on the next restart. You can also manually dump or reload the buffer pool at any time, for example during benchmarking or after complex report-generation queries. As of MySQL 5. Previously, innochecksum only supported files up to 2GB in size.
Enabling and disabling monitors for periodic output by creating and dropping specially named tables is deprecated and may be removed in a future release. For additional information, see Section MySQL implements compression with the help of the zlib library.
If you use InnoDB compressed tables, see Section 2. The maximum number of partitions is increased to Active development for MySQL 5. See Section For the syntax required to perform multiple-table updates, see Section END block. Does MySQL 5. See Fedora 26 End of Life announcement ». See Windows lifecycle fact sheet ». See Fedora 25 End of Life announcement ».
See Fedora 24 End of Life announcement ». See Ubuntu See Oracle Linux v5 End of Life announcement ». See Fedora 23 End of Life announcement ». See Fedora 22 End of Life announcement ». See Debian 6 End of Life announcement ». Users are requested to upgrade to recent versions of OS X See Fedora 21 End of Life announcement ».
See Fedora 20 End of Life announcement ». See Fedora 19 End of Life announcement ». Per the MySQL Support Lifecycle policy regarding ending support for OS versions that are obsolete, have reached end of life, or have little usage pattern, we plan to discontinue building all MySQL binaries for the following platforms.
0コメント