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/events-configuration.html
row *************************** Id: 2 User: event_scheduler Host: localhost db: NULL Command: Daemon Time: 3 State: Waiting for next activation Info: NULL 2 rows in set (0.00 sec) Event scheduling can be stopped by setting the value of ...When ...
https://dev.mysql.com/doc/refman/5.7/en/version-tokens-usage.html
Suppose that a management application communicates with a set of servers that are queried by clients to access employee and product databases (named emp and prod, respectively). In the token list for a given server, token names represent database ...
https://dev.mysql.com/doc/refman/5.7/en/implicit-commit.html
ALTER USER, CREATE USER, DROP USER, GRANT, RENAME USER, REVOKE, SET PASSWORD. This means that a ROLLBACK from the user does not undo CREATE TABLE statements the user made during that transaction. The statements listed in this section (and any ...
https://dev.mysql.com/doc/refman/5.7/en/replica-logs-status.html
Access to the replica's connection metadata repository file or table should be restricted to the database administrator, because it contains the replication user account name and password for connecting to the source. The metadata in this repository ...Updates to the replica's applier metadata repository table are committed together with the transactions, meaning that the replica's progress information recorded in that repository is always consistent with what has been applied to the database, even in the event of an unexpected server ...
https://dev.mysql.com/doc/refman/5.7/en/group-replication-enterprise-backup.html
The following instructions assume that you are already familiar with how to use MySQL Enterprise Backup to perform a backup; if that is not the case, please review the MySQL Enterprise Backup 4.1 User's Guide, especially Backing Up a Database Server. Connect to the restored server with a mysql client and reset the source and replica information with the following commands: mysql> RESET MASTER;mysql> RESET SLAVE ALL; For the restored server to be able to recover automatically using Group Replication's built-in mechanism for distributed recovery, configure the server's gtid_executed ...
https://dev.mysql.com/doc/refman/5.7/en/optimizing-innodb-diskio.html
(It is necessary to use the mount option rather than setting innodb_flush_method if you want direct I/O for the log files.) Users of the Veritas file system VxFS should use the convosync=direct mount option. If database write performance is an ...If ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-programs-ndb-waiter.html
SINGLE USER MODE: This is shown for all cluster data nodes when the cluster is in single user mode. --single-user The program waits for the cluster to enter single user mode. --ndb-connectstring Command-Line Format ...By default, it waits for the ...
https://dev.mysql.com/doc/refman/5.7/en/upgrade-binary-package.html
For example: mysqld_safe --user=mysql --datadir=/path/to/5.7-datadir & Reset the root password: $> mysql -u root -p Enter password: **** <- enter temporary root password mysql> ALTER USER USER() IDENTIFIED BY 'your new password'; Load the previously ...For example: mysqladmin -u root -p shutdown mysqld_safe --user=mysql --datadir=/path/to/existing-datadir & Logical Upgrade A logical upgrade involves exporting SQL from the old MySQL instance using a backup or export utility such as mysqldump or mysqlpump, installing the new MySQL server, and applying the SQL to your new MySQL ...
https://dev.mysql.com/doc/refman/5.7/en/installing-source-distribution.html
Note The procedure shown here does not set up any passwords for MySQL accounts. Then perform the following steps as the mysql user, except as noted. Perform Postinstallation Setup The remainder of the installation process involves setting up the ...
https://dev.mysql.com/doc/refman/5.7/en/get-diagnostics.html
This instance of GET DIAGNOSTICS assigns the number of available conditions and the rows-affected count to the user variables @p1 and @p2: GET DIAGNOSTICS @p1 = NUMBER, @p2 = ROW_COUNT; To obtain condition information, specify the condition number ...This instance of GET DIAGNOSTICS assigns the SQLSTATE value and error message to the user variables @p3 and @p4: GET DIAGNOSTICS CONDITION 1 @p3 = RETURNED_SQLSTATE, @p4 = MESSAGE_TEXT; The retrieval list specifies one or more target = item_name assignments, separated by ...