Search Results
https://dev.mysql.com/doc/refman/8.4/en/replication-semisync.html
Compared to asynchronous replication, semisynchronous replication provides improved data integrity, because when a commit returns successfully, it is known that the data exists in at least two places. In addition to the built-in asynchronous ...
https://dev.mysql.com/doc/refman/8.4/en/replication-solutions-unexpected-replica-halt.html
Note that this setting ignores the existing relay log files, in case they are corrupted or inconsistent. In order for replication to be resilient to unexpected halts of the server (sometimes described as crash-safe) it must be possible for the ...
https://dev.mysql.com/doc/refman/8.4/en/reset.html
Also resets the relay log by deleting any existing relay log files and beginning a new one. reset_option: { BINARY LOGS AND GTIDS | REPLICA } The RESET statement is used to clear the state of various server operations. For information about the ...
https://dev.mysql.com/doc/refman/8.4/en/reusing-ssl-sessions.html
MySQL client programs may elect to resume a prior SSL session, provided that the server has the session in its runtime cache. This section describes the conditions that are favorable for SSL session reuse, the server variables used for managing and ...
https://dev.mysql.com/doc/refman/8.4/en/row-subqueries.html
Scalar or column subqueries return a single value or a column of values. A row subquery is a subquery variant that returns a single row and can thus return more than one column value. If this row has col3 and col4 values equal to the col1 and col2 ...
https://dev.mysql.com/doc/refman/8.4/en/secure-client-programming.html
Client applications that access MySQL should use the following guidelines to avoid interpreting external data incorrectly or exposing sensitive information. Handle External Data Properly Handle MySQL Error Messages Properly Handle External Data ...
https://dev.mysql.com/doc/refman/8.4/en/security-against-attack.html
INTO OUTFILE do not overwrite existing files and are writable by everyone. When you connect to a MySQL server, you should use a password. All other information is transferred as text, and can be read by anyone who is able to watch the connection.
https://dev.mysql.com/doc/refman/8.4/en/security-plugins.html
MySQL Enterprise Data Masking and De-Identification functions enable masking existing data using several methods such as obfuscation (removing identifying characteristics), generation of formatted random data, and data replacement or substitution.
https://dev.mysql.com/doc/refman/8.4/en/select-into.html
file_name cannot be an existing file, which among other things prevents files such as /etc/passwd and database tables from being modified. INTO form of SELECT enables a query result to be stored in variables or written to a file: SELECT ... Column ...
https://dev.mysql.com/doc/refman/8.4/en/set-default-role.html
role [, role ] ...: Set the default to the named roles, which must exist and be granted to the account at the time SET DEFAULT ROLE is executed. SET DEFAULT ROLE {NONE | ALL | role [, role ] ...} TO user [, user ] ... For each user named ...