PDF (US Ltr)
- 35.1Mb
PDF (A4)
- 35.2Mb
Man Pages (TGZ)
- 256.4Kb
Man Pages (Zip)
- 361.2Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/partitioning-overview.html
Partition selection is also supported for the data modification statements DELETE, INSERT, REPLACE, UPDATE, and LOAD DATA, LOAD XML. This section provides a conceptual overview of partitioning in MySQL 5.7. For information on partitioning ...
https://dev.mysql.com/doc/refman/5.7/en/password-hashing.html
To accommodate longer password hashes, the Password column in the user table was changed at this point to be 41 bytes, its current length. If the column has not been updated and still has the pre-4.1 width of 16 bytes, the server notices that long ... Note The information in this section applies fully only before MySQL 5.7.5, and only for accounts that use the mysql_native_password or mysql_old_password authentication ...
https://dev.mysql.com/doc/refman/5.7/en/password-management.html
Password expiration according to policy is automatic and is based on password age, which for a given account is assessed from the date and time of its most recent password change. MySQL enables database administrators to expire account passwords ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-build-configuration.html
If you install MySQL over a previous installation that was configured without the Performance Schema (or with an older version of the Performance Schema that has missing or out-of-date tables). It is possible to exclude certain parts of the ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-instrumentation-checking.html
This information is always up to date for your version of MySQL, also includes instrumentation for instrumented plugins you might have installed that are not part of the core server, and can be used by automated tools. It is always possible to ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-statement-digests.html
A normalized statement does not retain information such as names, passwords, dates, and so forth. The MySQL server is capable of maintaining statement digest information. The digesting process converts each SQL statement to normalized form (the ...
https://dev.mysql.com/doc/refman/5.7/en/point-in-time-recovery.html
(The full backup can be made in several ways, such as those listed in Section 7.2, “Database Backup Methods”.) Point-in-time recovery then brings the server up to date incrementally from the time of the full backup to a more recent time.
https://dev.mysql.com/doc/refman/5.7/en/problems-with-null.html
When reading data with LOAD DATA, empty or missing columns are updated with ''. Under certain conditions, if you insert NULL into a TIMESTAMP column, the current date and time is inserted; this behavior depends in part on the server SQL mode (see ...
https://dev.mysql.com/doc/refman/5.7/en/replication-options-source.html
An unexpected exit of the source and failover to the replica is lossless because the replica is up to date. This section describes the server options and system variables that you can use on replication source servers. You can specify the options ...
https://dev.mysql.com/doc/refman/5.7/en/replication-solutions-switch.html
If you are not using GTIDs for replication, then the replicas should also be run with --log-slave-updates=OFF (logging replica updates is the default). Each MySQL replica (Replica 1, Replica 2, and Replica 3) is a replica running with binary logging ... You can tell a replica to change to a new source using the CHANGE MASTER TO ...