PDF (US Ltr)
- 35.0Mb
PDF (A4)
- 35.1Mb
Man Pages (TGZ)
- 254.9Kb
Man Pages (Zip)
- 359.9Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/replication-options.html
A set of quick-reference tables providing basic information about these options and variables is also included. server_uuid In MySQL 5.7, the server generates a true UUID in addition to the server_id value supplied by the user. Note The presence of ... The following sections contain information about mysqld options and server variables that are used in replication and for controlling the binary ...
https://dev.mysql.com/doc/refman/5.7/en/group-replication-limitations.html
Therefore we recommend setting group_replication_enforce_update_everywhere_checks=ON on server instances used in multi-primary mode groups to avoid undetected conflicts. Note that the limitations and issues described for multi-primary mode groups ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-instrument-filtering.html
The setup_instruments table lists the available instruments: mysql> SELECT * FROM performance_schema.setup_instruments; +---------------------------------------------------+---------+-------+ | NAME | ENABLED | TIMED | ...| wait/io/file/sql/binlog ...| stage/sql/end | NO | NO | | stage/sql/executing | NO | NO | | stage/sql/init | NO | NO | | stage/sql/insert | NO | NO | ...
https://dev.mysql.com/doc/refman/5.7/en/replication-gtids-concepts.html
In addition, the table is compressed periodically at a user-configurable rate; see mysql.gtid_executed Table Compression, for more information. For example, the values stored by the gtid_executed and gtid_purged system variables are GTID sets. The ...If a client transaction is not written to the binary log (for example, because the transaction was filtered out, or the transaction was read-only), it is not assigned a GTID on the server of ...
https://dev.mysql.com/doc/refman/5.7/en/privilege-changes.html
Any user can connect and perform any operation, which is insecure. The in-memory tables become effective for access control at that point. Thus, if you change the grant tables directly but forget to reload them, the changes have no effect until you ... If the mysqld server is started without the --skip-grant-tables option, it reads all grant table contents into memory during its startup ...
https://dev.mysql.com/doc/refman/5.7/en/backup-strategy-example.html
Information about this recovery process is conveyed to the user through the MySQL error log. Assume that data is stored in the InnoDB storage engine, which has support for transactions and automatic crash recovery. For cases of operating system ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-performance-schema.html
This type of tuning is primarily for expert users who evaluate optimization strategies to overcome performance bottlenecks. To view InnoDB-related instruments, you can query the setup_instruments table for instrument names that contain 'innodb'.
https://dev.mysql.com/doc/refman/5.7/en/macos-installation-prefpane.html
You may be prompted for the username and password of a user with administrator privileges to start the MySQL server. You may be prompted for the username and password of a user with administrator privileges to stop the MySQL server. The preference ... The MySQL Installation Package includes a MySQL preference pane that enables you to start, stop, and control automated startup during boot of your MySQL ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-startup-configuration.html
To enable or disable it explicitly, start the server with the performance_schema variable set to an appropriate value. For example, use these lines in your my.cnf file: [mysqld] performance_schema=ON If the server is unable to allocate any internal ... To use the MySQL Performance Schema, it must be enabled at server startup to enable event collection to ...
https://dev.mysql.com/doc/refman/5.7/en/table-locking.html
The automatic row-level locking makes these tables suitable for your busiest databases with your most important data, while also simplifying application logic since you do not need to lock and unlock tables. For this storage engine, avoid using the ... InnoDB tables use row-level locking so that multiple sessions and applications can read from and write to the same table simultaneously, without making each other wait or producing inconsistent ...