diff --git a/README.md b/README.md index 90e5c4b..2b35be1 100644 --- a/README.md +++ b/README.md @@ -1,4 +1,43 @@ -website +Website ======= -OLTP-Bench Web Site +OLTP-Bench Website is an intermediate between the client's database and OtterTune (DBMS Auto-tuning system) + +Dependencies +======== +* Python +2.7 +* [Tensorflow](https://www.tensorflow.org/versions/r0.10/get_started/os_setup.html#pip-installation) +* Django == 1.9 (currently does not support Django 1.10) +* django-debug-toolbar +1.5 +* celery +3.1.23 +* django-celery +3.1.17 +* rabbitmq-server +* python packages: python-mysqldb, sklearn, poster, numpy + + +Quick Start +===== +###1. Install Dependencies + sudo apt-get install python-pip python-dev python-sklearn python-mysqldb rabbitmq-server + sudo pip install django==1.9 numpy poster celery django-celery django-debug-toolbar +###2. Revise the setting.py file. + + Set the BasePath of your website (line 8) + + Set your database access (line 54) . (Name, User, Password ...) + +###3. Migrate the models into the database + + python manage.py makemigrations website + python manage.py migrate + +###4.Preload the parameters + python manage.py loaddata ./preload/* + +###5.Run the rabbitmq and celery worker + rabbitmq-server & + python manage.py celery worker --loglevel=info +###6. Run the website server + python manage.py runserver 0.0.0.0:8000 + + diff --git a/data/media/info.txt b/data/media/info.txt new file mode 100644 index 0000000..ee7f4e9 --- /dev/null +++ b/data/media/info.txt @@ -0,0 +1 @@ +The website stores the uploaded files in this directory diff --git a/preload/knobs.json b/preload/knobs.json new file mode 100644 index 0000000..0221ece --- /dev/null +++ b/preload/knobs.json @@ -0,0 +1,38757 @@ +[ + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"slave_compressed_protocol", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for slave_compressed_protocol", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1", + "unit":"NULL", + "description":"If this option is set to 1 use compression for theslave/master protocol if both the slave and the mastersupport it. The default is 0 (no compression)." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"init_slave", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for init_slave", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"2", + "unit":"NULL", + "description":"This variable is similar toGinit_connect but is astring to be executed by a slave server each time the SQLthread starts. The format of the string is the same as forthe init_connect variable." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"relay_log", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for relay-log", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"3", + "unit":"NULL", + "description":"The name of the relay log file." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"*host_name*-relay-bin.index", + "name":"relay_log_index", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for relay_log_index", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"4", + "unit":"NULL", + "description":"The name of the relay log index file. The default name ishost_name-relay-bin.indexin the data directory wherehost_name is the name of theslave server." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"relay-log.info", + "name":"relay_log_info_file", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for relay_log_info_file", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"5", + "unit":"NULL", + "description":"The name of the file in which the slave records informationabout the relay logs. The default name isrelay-log.info in the data directory." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"FALSE", + "name":"relay_log_recovery", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for relay_log_recovery", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"6", + "unit":"NULL", + "description":"Enables automatic relay log recovery immediately followingserver startup which means that the replication slavediscards all unprocessed relay logs and retrieves them fromthe replication master. This should be used following acrash on the replication slave to ensure that no possiblycorrupted relay logs are processed. The default value is 0(disabled). This global variable can be changed dynamicallyor by starting the slave with the--relay-log-recovery option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"rpl_recovery_rank", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"7", + "unit":"NULL", + "description":"This variable is unused and is removed in MySQL 5.6." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":" (NDB)", + "name":"slave_exec_mode", + "deprecated":"f", + "valid_vals":"IDEMPOTENT,STRICT", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for slave_exec_mode", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"8", + "unit":"NULL", + "description":"Controls how a slave thread resolves conflicts and errorsduring replication. IDEMPOTENT modecauses suppression of duplicate-key and no-key-found errors.This mode should be employed in multi-master replicationcircular replication and some other special replicationscenarios. STRICT mode is the defaultand is suitable for most other cases.This mode is needed for multi-master replication circularreplication and some other special replication scenariosfor MySQL Cluster Replication. (SeeSection 18.6.10 MySQL Cluster Replication: Multi-Master and Circular ReplicationandSection 18.6.11 MySQL Cluster Replication Conflict Resolutionfor more information.) The mysqldsupplied with MySQL Cluster ignores any value explicitly setfor slave_exec_mode andalways treats it as IDEMPOTENT.In MySQL Server 5.5 STRICTmode is the default value. This should not be changed;currently IDEMPOTENT mode is supportedonly by NDB." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"/tmp", + "name":"slave_load_tmpdir", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for slave-load-tmpdir", + "vartype":"directory name", + "max_value":"NULL", + "scope":"{Global}", + "id":"9", + "unit":"NULL", + "description":"The name of the directory where the slave creates temporaryfiles for replicatingLOAD DATAINFILE statements." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1073741824", + "name":"slave_max_allowed_packet", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1024", + "dynamic":"t", + "rank":"-1", + "summary":"Options for slave_max_allowed_packet", + "vartype":"integer", + "max_value":"1073741824", + "scope":"{Global}", + "id":"10", + "unit":"NULL", + "description":"In MySQL 5.5.26 and later this variable sets the maximumpacket size for the slave SQL and I/O threads so that largeupdates using row-based replication do not cause replicationto fail because an update exceededmax_allowed_packet.This global variable always has a value that is a positiveinteger multiple of 1024; if you set it to some value thatis not the value is rounded down to the next highestmultiple of 1024 for it is stored or used; settingslave_max_allowed_packet to 0 causes 1024to be used. (A truncation warning is issued in all suchcases.) The default and maximum value is 1073741824 (1 GB);the minimum is 1024.slave_max_allowed_packet can also be setat startup using the--slave-max-allowed-packetoption." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"3600", + "name":"slave_net_timeout", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for slave-net-timeout", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"11", + "unit":"NULL", + "description":"The number of seconds to wait for more data from amaster/slave connection before aborting the read." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"slave_skip_errors", + "deprecated":"f", + "valid_vals":"OFF,[list of error codes],all,ddl_exist_errors", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for slave-skip-errors", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"12", + "unit":"NULL", + "description":"Normally replication stops when an error occurs on theslave. This gives you the opportunity to resolve theinconsistency in the data manually. This variable tells theslave SQL thread to continue replication when a statementreturns any of the errors listed in the variable value." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"10", + "name":"slave_transaction_retries", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for slave_transaction_retries", + "vartype":"integer", + "max_value":"18446744073709547520", + "scope":"{Global}", + "id":"13", + "unit":"NULL", + "description":"If a replication slave SQL thread fails to execute atransaction because of anInnoDB deadlock or because thetransaction's execution time exceededInnoDB'sinnodb_lock_wait_timeout orNDBCLUSTER'sTransactionDeadlockDetectionTimeoutorTransactionInactiveTimeoutit automatically retriesslave_transaction_retriestimes before stopping with an error. The default value is10" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"slave_type_conversions", + "deprecated":"f", + "valid_vals":"ALL_LOSSY,ALL_NON_LOSSY", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for slave_type_conversions", + "vartype":"set", + "max_value":"NULL", + "scope":"{Global}", + "id":"14", + "unit":"NULL", + "description":"Controls the type conversion mode in effect on the slavewhen using row-based replication including MySQL ClusterReplication. Its value is a comma-delimited set of zero ormore elements from the list: ALL_LOSSYALL_NON_LOSSY. Set this variable to anempty string to disallow type conversions between the masterand the slave. Changes require a restart of the slave totake effect.For additional information on type conversion modesapplicable to attribute promotion and demotion in row-basedreplication seeRow-based replication: attribute promotion and demotion.This variable was added in MySQL 5.5.3." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"sql_slave_skip_counter", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sql_slave_skip_counter", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"15", + "unit":"NULL", + "description":"The number of events from the master that a slave servershould skip." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"sync_master_info", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sync_master_info", + "vartype":"integer", + "max_value":"18446744073709547520", + "scope":"{Global}", + "id":"16", + "unit":"NULL", + "description":"If the value of this variable is greater than 0 areplication slave synchronizes itsmaster.info file to disk (usingfdatasync()) after everysync_master_info events.The default value is 0 (recommended in most situations)which does not force any synchronization to disk by theMySQL server; in this case the server relies on theoperating system to flush themaster.info file's contents fromtime to time as for any other file." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"sync_relay_log", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sync_relay_log", + "vartype":"integer", + "max_value":"18446744073709547520", + "scope":"{Global}", + "id":"17", + "unit":"NULL", + "description":"If the value of this variable is greater than 0 the MySQLserver synchronizes its relay log to disk (usingfdatasync()) after everysync_relay_log events are written to therelay log.The default value of sync_relay_log is 0which does no synchronizing to disk; in this case theserver relies on the operating system to flush the relaylog's contents from time to time as for any other file.A value of 1 is the safest choice because in the event of acrash you lose at most one event from the relay log.However it is also the slowest choice (unless the disk hasa battery-backed cache which makes synchronization veryfast)." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"sync_relay_log_info", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sync_relay_log_info", + "vartype":"integer", + "max_value":"18446744073709547520", + "scope":"{Global}", + "id":"18", + "unit":"NULL", + "description":"If the value of this variable is greater than 0 areplication slave synchronizes itsrelay-log.info file to disk (usingfdatasync()) after everysync_relay_log_infotransactions. A value of 1 is the generally the best choice.The default value ofsync_relay_log_info is 0which does not force any synchronization to disk by theMySQL serverin this case the server relies on theoperating system to flush therelay-log.info file's contentsfrom time to time as for any other file." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"basedir", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for basedir", + "vartype":"directory name", + "max_value":"NULL", + "scope":"{Global}", + "id":"19", + "unit":"NULL", + "description":"The path to the MySQL installation directory. All paths areusually resolved relative to this directory." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"datadir", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for datadir", + "vartype":"directory name", + "max_value":"NULL", + "scope":"{Global}", + "id":"20", + "unit":"NULL", + "description":"The path to the data directory." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"d:t:i:o/tmp/mysqld.trace", + "name":"debug", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for debug", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"21", + "unit":"NULL", + "description":"If MySQL is configured with the-DWITH_DEBUG=1CMake option you can use this option toget a trace file of what mysqld is doing. Atypical debug_options string isd:t:ofile_name.The default is d:t:i:o/tmp/mysqld.trace onUnix and d:t:i:Omysqld.trace on Windows.Using -DWITH_DEBUG=1 toconfigure MySQL with debugging support enables you to use the--debug=dparser_debug optionwhen you start the server. This causes the Bison parser thatis used to process SQL statements to dump a parser trace tothe server's standard error output. Typically this output iswritten to the error log.This option may be given multiple times. Values that beginwith + or - are added toor subtracted from the previous value. For example--debug=T--debug=+P sets the value toP:T.For more information see Section 24.5.3 The DBUG Package." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"flush", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for flush", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"22", + "unit":"NULL", + "description":"Flush (synchronize) all changes to disk after each SQLstatement. Normally MySQL does a write of all changes to diskonly after each SQL statement and lets the operating systemhandle the synchronizing to disk. SeeSection B.5.3.3 What to Do If MySQL Keeps Crashing." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"/usr/local/mysql/share/mysql/english/", + "name":"language", + "deprecated":"t", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for language", + "vartype":"directory name", + "max_value":"NULL", + "scope":"{Global}", + "id":"23", + "unit":"NULL", + "description":"The language to use for error messages.lang_name can be given as thelanguage name or as the full path name to the directory wherethe language files are installed. SeeSection 10.2 Setting the Error Message Language.As of MySQL 5.5--lc-messages-dir and--lc-messages should be usedrather than --language whichis deprecated and handled as an alias for--lc-messages-dir." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"latin1_swedish_ci", + "name":"collation_server", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for collation-server", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"45", + "unit":"NULL", + "description":"The server's default collation." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"INTERNAL", + "name":"identity", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"integer", + "max_value":"NULL", + "scope":"{NA}", + "id":"88", + "unit":"NULL", + "description":"This variable is a synonym for thelast_insert_id variable. Itexists for compatibility with other database systems. You canread its value with SELECT @@identity andset it using SET identity." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"log", + "deprecated":"t", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for log", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"24", + "unit":"NULL", + "description":"This option enables logging to the general query log whichcontains entries that record client connections and SQLstatements received from clients. The log output destinationcan be selected with the--log-output option. If youomit the file name MySQL useshost_name.logas the file name. See Section 5.4.1 Selecting General Query and Slow Query Log Output Destinations andSection 5.4.3 The General Query Log.The --log option is deprecatedand is removed (along with thelog system variable) in MySQL5.6. Instead use the--general_log option to enablethe general query log and the--general_log_file=file_nameoption to set the general query log file name." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"min-examined-row-limit", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for min-examined-row-limit", + "vartype":"integer", + "max_value":"18446744073709547520", + "scope":"{GlobalSession}", + "id":"25", + "unit":"NULL", + "description":"When this option is set queries which examine fewer thannumber rows are not written to theslow query log. The default is 0." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"3306", + "name":"port", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"Options for port", + "vartype":"integer", + "max_value":"65535", + "scope":"{Global}", + "id":"26", + "unit":"NULL", + "description":"The port number to use when listening for TCP/IP connections.On Unix and Unix-like systems the port number must be 1024 orhigher unless the server is started by theroot system user." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"/tmp/mysql.sock", + "name":"socket", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for socket", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"27", + "unit":"NULL", + "description":"On Unix this option specifies the Unix socket file to usewhen listening for local connections. The default value is/tmp/mysql.sock. If this option is giventhe server creates the file in the data directory unless anabsolute path name is given to specify a different directory.On Windows the option specifies the pipe name to use whenlistening for local connections that use a named pipe. Thedefault value is MySQL (not casesensitive)." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"tmpdir", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for tmpdir", + "vartype":"directory name", + "max_value":"NULL", + "scope":"{Global}", + "id":"28", + "unit":"NULL", + "description":"The path of the directory to use for creating temporary files.It might be useful if your default /tmpdirectory resides on a partition that is too small to holdtemporary tables. This option accepts several paths that areused in round-robin fashion. Paths should be separated bycolon characters (:) on Unixand semicolon characters (;)on Windows. If the MySQL server is acting as a replicationslave you should not set--tmpdir to point to adirectory on a memory-based file system or to a directory thatis cleared when the server host restarts. For more informationabout the storage location of temporary files seeSection B.5.3.5 Where MySQL Stores Temporary Files. A replication slave needssome of its temporary files to survive a machine restart sothat it can replicate temporary tables orLOAD DATAINFILE operations. If files in the temporary filedirectory are lost when the server restarts replicationfails." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"version", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"29", + "unit":"NULL", + "description":"Display version information and exit." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"autocommit", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for autocommit", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"30", + "unit":"NULL", + "description":"The autocommit mode. If set to 1 all changes to a table takeeffect immediately. If set to 0 you must useCOMMIT to accept a transactionor ROLLBACKto cancel it. If autocommitis 0 and you change it to 1 MySQL performs an automaticCOMMIT of any open transaction.Another way to begin a transaction is to use aSTARTTRANSACTION orBEGINstatement. See Section 13.3.1 START TRANSACTION COMMIT and ROLLBACK Syntax.By default client connections begin withautocommit set to 1. To causeclients to begin with a default of 0 set the globalautocommit value by startingthe server with the--autocommit=0 option. To setthe variable using an option file include these lines:Before MySQL 5.5.8 the globalautocommit value cannot beset at startup. As a workaround set theinit_connect system variable:The init_connect variable canalso be set on the command line or in an option file. To setthe variable as just shown using an option file include theselines:The content of init_connectis not executed for users that have theSUPER privilege (unlike theeffect of setting the globalautocommit value at startup)." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"TRUE", + "name":"automatic_sp_privileges", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for automatic_sp_privileges", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"31", + "unit":"NULL", + "description":"When this variable has a value of 1 (the default) the serverautomatically grants theEXECUTE andALTER ROUTINE privileges to thecreator of a stored routine if the user cannot alreadyexecute and alter or drop the routine. (TheALTER ROUTINE privilege isrequired to drop the routine.) The server also automaticallydrops those privileges from the creator when the routine isdropped. Ifautomatic_sp_privileges is 0the server does not automatically add or drop theseprivileges.The creator of a routine is the account used to execute theCREATE statement for it. This might not bethe same as the account named as theDEFINER in the routine definition.See also Section 20.2.2 Stored Routines and MySQL Privileges." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1000", + "name":"delayed_queue_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for delayed_queue_size", + "vartype":"integer", + "max_value":"18446744073709547520", + "scope":"{Global}", + "id":"57", + "unit":"NULL", + "description":"This is a per-table limit on the number of rows to queue whenhandling INSERT DELAYEDstatements. If the queue becomes full any client that issuesan INSERT DELAYED statementwaits until there is room in the queue again." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"18446744073709547520", + "name":"max_write_lock_count", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_write_lock_count", + "vartype":"integer", + "max_value":"18446744073709547520", + "scope":"{Global}", + "id":"138", + "unit":"NULL", + "description":"After this many write locks permit some pending read lockrequests to be processed in between." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"50", + "name":"back_log", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1", + "dynamic":"f", + "rank":"-1", + "summary":"Options for back_log", + "vartype":"integer", + "max_value":"65535", + "scope":"{Global}", + "id":"32", + "unit":"NULL", + "description":"The number of outstanding connection requests MySQL can have.This comes into play when the main MySQL thread gets very manyconnection requests in a very short time. It then takes sometime (although very little) for the main thread to check theconnection and start a new thread. Theback_log value indicates howmany requests can be stacked during this short time beforeMySQL momentarily stops answering new requests. You need toincrease this only if you expect a large number of connectionsin a short period of time.In other words this value is the size of the listen queue forincoming TCP/IP connections. Your operating system has its ownlimit on the size of this queue. The manual page for the Unixlisten() system call should have moredetails. Check your OS documentation for the maximum value forthis variable. back_logcannot be set higher than your operating system limit." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"big_tables", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for big-tables", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global,Session}", + "id":"33", + "unit":"NULL", + "description":"If set to 1 all temporary tables are stored on disk ratherthan in memory. This is a little slower but the errorThe table tbl_name isfull does not occur forSELECT operations that requirea large temporary table. The default value for a newconnection is 0 (use in-memory temporary tables). Normallyyou should never need to set this variable because in-memorytables are automatically converted to disk-based tables asrequired." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"8388608", + "name":"bulk_insert_buffer_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for bulk_insert_buffer_size", + "vartype":"integer", + "max_value":"18446744073709547520", + "scope":"{GlobalSession}", + "id":"34", + "unit":"NULL", + "description":"MyISAM uses a special tree-like cache tomake bulk inserts faster forINSERT ...SELECT INSERT ... VALUES (...) (...)... andLOAD DATAINFILE when adding data to nonempty tables. Thisvariable limits the size of the cache tree in bytes perthread. Setting it to 0 disables this optimization. Thedefault value is 8MB." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"CHARSET", + "name":"character_set_client", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for character_set_client", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"35", + "unit":"NULL", + "description":"The character set for statements that arrive from the client.The session value of this variable is set using the characterset requested by the client when the client connects to theserver. (Many clients support a--default-character-set option to enable thischaracter set to be specified explicitly. See alsoSection 10.1.5 Connection Character Sets and Collations.) The global value of thevariable is used to set the session value in cases when theclient-requested value is unknown or not available or theserver is configured to ignore client requests:ucs2 utf16 andutf32 cannot be used as a client characterset which means that they also do not work for SETNAMES or SET CHARACTER SET." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"CHARSET", + "name":"character_set_connection", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for character_set_connection", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"36", + "unit":"NULL", + "description":"The character set used for literals that do not have acharacter set introducer and for number-to-string conversion." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"CHARSET", + "name":"character_set_database", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for character_set_database", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"37", + "unit":"NULL", + "description":"The character set used by the default database. The serversets this variable whenever the default database changes. Ifthere is no default database the variable has the same valueas character_set_server." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"binary", + "name":"character_set_filesystem", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for character-set-filesystem", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"38", + "unit":"NULL", + "description":"The file system character set. This variable is used tointerpret string literals that refer to file names such as inthe LOAD DATAINFILE andSELECT ... INTOOUTFILE statements and theLOAD_FILE() function. Such filenames are converted fromcharacter_set_client tocharacter_set_filesystembefore the file opening attempt occurs. The default value isbinary which means that no conversionoccurs. For systems on which multibyte file names arepermitted a different value may be more appropriate. Forexample if the system represents file names using UTF-8 setcharacter_set_filesystem to'utf8'." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"CHARSET", + "name":"character_set_results", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for character_set_results", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"39", + "unit":"NULL", + "description":"The character set used for returning query results such asresult sets or error messages to the client." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"latin1", + "name":"character_set_server", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for character-set-server", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"40", + "unit":"NULL", + "description":"The server's default character set." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"utf8", + "name":"character_set_system", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for character_set_system", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"41", + "unit":"NULL", + "description":"The character set used by the server for storing identifiers.The value is always utf8." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"character_sets_dir", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for character-sets-dir", + "vartype":"directory name", + "max_value":"NULL", + "scope":"{Global}", + "id":"42", + "unit":"NULL", + "description":"The directory where character sets are installed." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"COLLATION", + "name":"collation_connection", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for collation_connection", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"43", + "unit":"NULL", + "description":"The collation of the connection character set." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"COLLATION", + "name":"collation_database", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for collation_database", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"44", + "unit":"NULL", + "description":"The collation used by the default database. The server setsthis variable whenever the default database changes. If thereis no default database the variable has the same value ascollation_server." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"completion_type", + "deprecated":"f", + "valid_vals":"0,1,2", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for completion_type", + "vartype":"integer", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"46", + "unit":"NULL", + "description":"The transaction completion type. This variable can take thevalues shown in the following table. As of MySQL 5.5.3 thevariable can be assigned using either the name values orcorresponding integer values. Before 5.5.3 only the integervalues can be used.completion_type affectstransactions that begin withSTARTTRANSACTION orBEGIN andend with COMMIT orROLLBACK. Itdoes not apply to implicit commits resulting from execution ofthe statements listed in Section 13.3.3 Statements That Cause an Implicit Commit. Italso does not apply forXACOMMITXAROLLBACK or whenautocommit=1." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1", + "name":"concurrent_insert", + "deprecated":"f", + "valid_vals":"0,1,2", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for concurrent_insert", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"47", + "unit":"NULL", + "description":"If AUTO (the default) MySQL permitsINSERT andSELECT statements to runconcurrently for MyISAM tables that have nofree blocks in the middle of the data file. If you startmysqld with--skip-newthis variable is set to NEVER.This variable can take the values shown in the followingtable. As of MySQL 5.5.3 the variable can be assigned usingeither the name values or corresponding integer values. Before5.5.3 only the integer values can be used.See also Section 8.11.3 Concurrent Inserts." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"10", + "name":"connect_timeout", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"2", + "dynamic":"t", + "rank":"-1", + "summary":"Options for connect_timeout", + "vartype":"integer", + "max_value":"31536000", + "scope":"{Global}", + "id":"48", + "unit":"NULL", + "description":"The number of seconds that the mysqldserver waits for a connect packet before responding withBad handshake. The default value is 10seconds.Increasing theconnect_timeout value mighthelp if clients frequently encounter errors of the formLost connection to MySQL server at'XXX' system error:errno." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"%Y-%m-%d", + "name":"date_format", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"49", + "unit":"NULL", + "description":"This variable is unused." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"%Y-%m-%d %H:%i:%s", + "name":"datetime_format", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"50", + "unit":"NULL", + "description":"This variable is unused." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"debug_sync", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for debug_sync", + "vartype":"string", + "max_value":"NULL", + "scope":"{Session}", + "id":"51", + "unit":"NULL", + "description":"This variable is the user interface to the Debug Syncfacility. Use of Debug Sync requires that MySQL be configuredwith the -DENABLE_DEBUG_SYNC=1CMake option (seeSection 2.9.4 MySQL Source-Configuration Options). If Debug Syncis not compiled in this system variable is not available.The global variable value is read only and indicates whetherthe facility is enabled. By default Debug Sync is disabledand the value of debug_syncis OFF. If the server is started with--debug-sync-timeout=Nwhere N is a timeout value greaterthan 0 Debug Sync is enabled and the value ofdebug_sync is ON -current signal followed by the signal name. AlsoN becomes the default timeout forindividual synchronization points.The session value can be read by any user and will have thesame value as the global variable. The session value can beset by users that have theSUPER privilege to controlsynchronization points.For a description of the Debug Sync facility and how to usesynchronization points seeMySQLInternals: Test Synchronization." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"MyISAM", + "name":"default_storage_engine", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for default-storage-engine", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"52", + "unit":"NULL", + "description":"The default storage engine. To set the storage engine atserver startup use the--default-storage-engineoption. See Section 5.1.3 Server Command Options.To see which storage engines are available and enabled usethe SHOW ENGINES statement orquery the INFORMATION_SCHEMAENGINES table.If you disable the default storage engine at server startupyou must set the default engine to a different engine or theserver will not start.This variable was added in MySQL 5.5.3 to be used inpreference to storage_enginewhich is now deprecated." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"default_week_format", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for default_week_format", + "vartype":"integer", + "max_value":"7", + "scope":"{GlobalSession}", + "id":"53", + "unit":"NULL", + "description":"The default mode value to use for theWEEK() function. SeeSection 12.7 Date and Time Functions." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"ON", + "name":"delay_key_write", + "deprecated":"f", + "valid_vals":"ON,OFF,ALL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for delay-key-write", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"54", + "unit":"NULL", + "description":"This option applies only to MyISAM tables.It can have one of the following values to affect handling ofthe DELAY_KEY_WRITE table option that canbe used in CREATE TABLEstatements.If DELAY_KEY_WRITE is enabled for a tablethe key buffer is not flushed for the table on every indexupdate but only when the table is closed. This speeds upwrites on keys a lot but if you use this feature you shouldadd automatic checking of all MyISAM tablesby starting the server with the--myisam-recover-options option(for example--myisam-recover-options=BACKUPFORCE).See Section 5.1.3 Server Command Options andSection 15.3.1 MyISAM Startup Options." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"100", + "name":"delayed_insert_limit", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for delayed_insert_limit", + "vartype":"integer", + "max_value":"18446744073709547520", + "scope":"{Global}", + "id":"55", + "unit":"NULL", + "description":"After insertingdelayed_insert_limit delayedrows the INSERT DELAYEDhandler thread checks whether there are anySELECT statements pending. Ifso it permits them to execute before continuing to insertdelayed rows." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"300", + "name":"delayed_insert_timeout", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for delayed_insert_timeout", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"56", + "unit":"NULL", + "description":"How many seconds an INSERTDELAYED handler thread should wait forINSERT statements beforeterminating." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"4", + "name":"div_precision_increment", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for div_precision_increment", + "vartype":"integer", + "max_value":"30", + "scope":"{GlobalSession}", + "id":"58", + "unit":"NULL", + "description":"This variable indicates the number of digits by which toincrease the scale of the result of division operationsperformed with the/ operator.The default value is 4. The minimum and maximum values are 0and 30 respectively. The following example illustrates theeffect of increasing the default value." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"engine_condition_pushdown", + "deprecated":"t", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for engine-condition-pushdown", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"59", + "unit":"NULL", + "description":"The engine condition pushdown optimization enables processingfor certain comparisons to be pushed down tothe storage engine level for more efficient execution. Formore information seeSection 8.2.1.5 Engine Condition Pushdown Optimization.Engine condition pushdown is used only by theNDBCLUSTER storage engine.Enabling this optimization on a MySQL Server acting as a MySQLCluster SQL node causes WHERE conditions onunindexed columns to be evaluated on the cluster's data nodesand only the rows that match to be sent back to the SQL nodethat issued the query. This greatly reduces the amount ofcluster data that must be sent over the network increasingthe efficiency with which results are returned.The engine_condition_pushdownvariable controls whether engine condition pushdown isenabled. By default this variable is ON(1). Setting it to OFF (0) disablespushdown.This variable is deprecated as of MySQL 5.5.3 and is removedin MySQL 5.6. Use theengine_condition_pushdown flag of theoptimizer_switch variableinstead. See Section 8.9.2 Controlling Switchable Optimizations." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"INTERNAL", + "name":"error_count", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"integer", + "max_value":"NULL", + "scope":"{NA}", + "id":"60", + "unit":"NULL", + "description":"The number of errors that resulted from the last statementthat generated messages. This variable is read only. SeeSection 13.7.5.18 SHOW ERRORS Syntax." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"event_scheduler", + "deprecated":"f", + "valid_vals":"ON,OFF,DISABLED", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for event-scheduler", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"61", + "unit":"NULL", + "description":"This variable indicates the status of the Event Scheduler;possible values are ONOFF and DISABLED withthe default being OFF. This variable andits effects on the Event Scheduler's operation are discussedin greater detail in theOverview sectionof the Events chapter." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"expire_logs_days", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for expire_logs_days", + "vartype":"integer", + "max_value":"99", + "scope":"{Global}", + "id":"62", + "unit":"NULL", + "description":"The number of days for automatic binary log file removal. Thedefault is 0 which means no automatic removal.Possible removals happen at startup and when the binary log isflushed. Log flushing occurs as indicated inSection 5.4 MySQL Server Logs.To remove binary log files manually use thePURGE BINARY LOGS statement.See Section 13.4.1.1 PURGE BINARY LOGS Syntax." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"external_user", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for external_user", + "vartype":"string", + "max_value":"NULL", + "scope":"{Session}", + "id":"63", + "unit":"NULL", + "description":"The external user name used during the authentication processas set by the plugin used to authenticate the client. Withnative (built-in) MySQL authentication or if the plugin doesnot set the value this variable is NULL.See Section 6.3.7 Proxy Users.This variable was added in MySQL 5.5.7." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"flush_time", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for flush_time", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"64", + "unit":"NULL", + "description":"If this is set to a nonzero value all tables are closed everyflush_time seconds to free upresources and synchronize unflushed data to disk. This optionis best used only on systems with minimal resources." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"foreign_key_checks", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{NA}", + "id":"65", + "unit":"NULL", + "description":"If set to 1 (the default) foreign key constraints forInnoDB tables are checked. If set to 0foreign key constraints are ignored with a couple ofexceptions. When re-creating a table that was dropped anerror is returned if the table definition does not conform tothe foreign key constraints referencing the table. Likewisean ALTER TABLE operationreturns an error if a foreign key definition is incorrectlyformed. For more information seeSection 13.1.17.3 Using FOREIGN KEY Constraints.Disabling foreign key checking can be useful for reloadingInnoDB tables in an order different fromthat required by their parent/child relationships. SeeSection 14.9.6 InnoDB and FOREIGN KEY Constraints.Setting foreign_key_checks to0 also affects data definition statements:DROPSCHEMA drops a schema even if it contains tablesthat have foreign keys that are referred to by tables outsidethe schema and DROP TABLEdrops tables that have foreign keys that are referred to byother tables." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"+ -><()~*:&|", + "name":"ft_boolean_syntax", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for ft_boolean_syntax", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"66", + "unit":"NULL", + "description":"The list of operators supported by boolean full-text searchesperformed using IN BOOLEAN MODE. SeeSection 12.9.2 Boolean Full-Text Searches.The default variable value is'+ -><()~*:&|'. The rulesfor changing the value are as follows:" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"84", + "name":"ft_max_word_len", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"10", + "dynamic":"f", + "rank":"-1", + "summary":"Options for ft_max_word_len", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"67", + "unit":"NULL", + "description":"The maximum length of the word to be included in aFULLTEXT index." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"4", + "name":"ft_min_word_len", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1", + "dynamic":"f", + "rank":"-1", + "summary":"Options for ft_min_word_len", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"68", + "unit":"NULL", + "description":"The minimum length of the word to be included in aFULLTEXT index." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"20", + "name":"ft_query_expansion_limit", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"Options for ft_query_expansion_limit", + "vartype":"integer", + "max_value":"1000", + "scope":"{Global}", + "id":"69", + "unit":"NULL", + "description":"The number of top matches to use for full-text searchesperformed using WITH QUERY EXPANSION." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"ft_stopword_file", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for ft_stopword_file", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"70", + "unit":"NULL", + "description":"The file from which to read the list of stopwords forfull-text searches. The server looks for the file in the datadirectory unless an absolute path name is given to specify adifferent directory. All the words from the file are used;comments are not honored. By default abuilt-in list of stopwords is used (as defined in thestorage/myisam/ft_static.c file). Settingthis variable to the empty string ('')disables stopword filtering. See alsoSection 12.9.4 Full-Text Stopwords." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"general_log", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for general-log", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"71", + "unit":"NULL", + "description":"Whether the general query log is enabled. The value can be 0(or OFF) to disable the log or 1 (orON) to enable the log. The default valuedepends on whether the--general_log option is given.The destination for log output is controlled by thelog_output system variable;if that value is NONE no log entries arewritten even if the log is enabled." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"host_name.log", + "name":"general_log_file", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for general_log_file", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"72", + "unit":"NULL", + "description":"The name of the general query log file. The default value ishost_name.logbut the initial value can be changed with the--general_log_file option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1024", + "name":"group_concat_max_len", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"4", + "dynamic":"t", + "rank":"-1", + "summary":"Options for group_concat_max_len", + "vartype":"integer", + "max_value":"18446744073709547520", + "scope":"{GlobalSession}", + "id":"73", + "unit":"NULL", + "description":"The maximum permitted result length in bytes for theGROUP_CONCAT() function. Thedefault is 1024." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"have_compress", + "deprecated":"f", + "valid_vals":"YES,NO,DISABLED", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"74", + "unit":"NULL", + "description":"YES if the zlibcompression library is available to the serverNO if not. If not theCOMPRESS() andUNCOMPRESS() functions cannotbe used." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"have_crypt", + "deprecated":"f", + "valid_vals":"YES,NO,DISABLED", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"75", + "unit":"NULL", + "description":"YES if the crypt()system call is available to the server NOif not. If not the ENCRYPT()function cannot be used." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"have_csv", + "deprecated":"f", + "valid_vals":"YES,NO,DISABLED", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"76", + "unit":"NULL", + "description":"YES if mysqld supportsCSV tables NO if not.This variable is deprecated and is removed in MySQL 5.6. UseSHOW ENGINES instead." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"have_dynamic_loading", + "deprecated":"f", + "valid_vals":"YES,NO,DISABLED", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"77", + "unit":"NULL", + "description":"YES if mysqld supportsdynamic loading of plugins NO if not." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"have_geometry", + "deprecated":"f", + "valid_vals":"YES,NO,DISABLED", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"78", + "unit":"NULL", + "description":"YES if the server supports spatial datatypes NO if not." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"have_innodb", + "deprecated":"f", + "valid_vals":"YES,NO,DISABLED", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"79", + "unit":"NULL", + "description":"YES if mysqld supportsInnoDB tables. DISABLEDif--skip-innodbis used.This variable is deprecated and is removed in MySQL 5.6. UseSHOW ENGINES instead." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"have_openssl", + "deprecated":"f", + "valid_vals":"YES,NO,DISABLED", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"80", + "unit":"NULL", + "description":"This variable is an alias forhave_ssl." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"have_partitioning", + "deprecated":"f", + "valid_vals":"YES,NO,DISABLED", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"81", + "unit":"NULL", + "description":"YES if mysqld supportspartitioning.This variable is deprecated and is removed in MySQL 5.6. UseSHOW PLUGINS instead. For moreinformation see Chapter 19 Partitioning." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"have_profiling", + "deprecated":"f", + "valid_vals":"YES,NO,DISABLED", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"82", + "unit":"NULL", + "description":"YES if statement profiling capability ispresent NO if not. If present theprofiling system variable controls whetherthis capability is enabled or disabled. SeeSection 13.7.5.32 SHOW PROFILES Syntax." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"have_query_cache", + "deprecated":"f", + "valid_vals":"YES,NO,DISABLED", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"83", + "unit":"NULL", + "description":"YES if mysqld supportsthe query cache NO if not." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"have_rtree_keys", + "deprecated":"f", + "valid_vals":"YES,NO,DISABLED", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"84", + "unit":"NULL", + "description":"YES if RTREE indexes areavailable NO if not. (These are used forspatial indexes in MyISAM tables.)" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"have_ssl", + "deprecated":"f", + "valid_vals":"YES,NO,DISABLED", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"85", + "unit":"NULL", + "description":"YES if mysqld supportsSSL connections NO if not.DISABLED indicates that the server wascompiled with SSL support but was not started with theappropriate--ssl-xxx options.For more information seeSection 6.3.8.2 Building MySQL with Support for Secure Connections." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"have_symlink", + "deprecated":"f", + "valid_vals":"YES,NO,DISABLED", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"86", + "unit":"NULL", + "description":"YES if symbolic link support is enabledNO if not. This is required on Unix forsupport of the DATA DIRECTORY andINDEX DIRECTORY table options and onWindows for support of data directory symlinks. If the serveris started with the--skip-symbolic-linksoption the value is DISABLED." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"hostname", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for hostname", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"87", + "unit":"NULL", + "description":"The server sets this variable to the server host name atstartup." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"init_connect", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for init_connect", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"89", + "unit":"NULL", + "description":"A string to be executed by the server for each client thatconnects. The string consists of one or more SQL statementsseparated by semicolon characters. For example each clientsession begins by default with autocommit mode enabled. Forolder servers (before MySQL 5.5.8) there is no globalautocommit system variable tospecify that autocommit should be disabled by default but asa workaround init_connect canbe used to achieve the same effect:The init_connect variable canalso be set on the command line or in an option file. To setthe variable as just shown using an option file include theselines:The content of init_connectis not executed for users that have theSUPER privilege. This is doneso that an erroneous value forinit_connect does not preventall clients from connecting. For example the value mightcontain a statement that has a syntax error thus causingclient connections to fail. Not executinginit_connect for users thathave the SUPER privilegeenables them to open a connection and fix theinit_connect value.The server discards any result sets produced by statements inthe value of of init_connect." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"init_file", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for init-file", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"90", + "unit":"NULL", + "description":"The name of the file specified with the--init-file option when youstart the server. This should be a file containing SQLstatements that you want the server to execute when it starts.Each statement must be on a single line and should not includecomments. For more information see the description of--init-file." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"INTERNAL", + "name":"insert_id", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"integer", + "max_value":"NULL", + "scope":"{NA}", + "id":"91", + "unit":"NULL", + "description":"The value to be used by the followingINSERT orALTER TABLE statement wheninserting an AUTO_INCREMENT value. This ismainly used with the binary log." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"28800", + "name":"interactive_timeout", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for interactive_timeout", + "vartype":"integer", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"92", + "unit":"NULL", + "description":"The number of seconds the server waits for activity on aninteractive connection before closing it. An interactiveclient is defined as a client that uses theCLIENT_INTERACTIVE option tomysql_real_connect(). See alsowait_timeout." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"131072", + "name":"join_buffer_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"8228", + "dynamic":"t", + "rank":"-1", + "summary":"Options for join_buffer_size", + "vartype":"integer", + "max_value":"18446744073709547520", + "scope":"{GlobalSession}", + "id":"93", + "unit":"NULL", + "description":"The minimum size of the buffer that is used for plain indexscans range index scans and joins that do not use indexesand thus perform full table scans. Normally the best way toget fast joins is to add indexes. Increase the value ofjoin_buffer_size to get afaster full join when adding indexes is not possible. One joinbuffer is allocated for each full join between two tables. Fora complex join between several tables for which indexes arenot used multiple join buffers might be necessary.There is no gain from setting the buffer larger than requiredto hold each matching row and all joins allocate at least theminimum size so use caution in setting this variable to alarge value globally. It is better to keep the global settingsmall and change to a larger setting only in sessions that aredoing large joins. Memory allocation time can causesubstantial performance drops if the global size is largerthan needed by most queries that use it.The maximum permissible setting forjoin_buffer_size is4GB1. Larger values are permitted for 64-bit platforms(except 64-bit Windows for which large values are truncatedto 4GB1 with a warning).Prior to MySQL 5.5.3 the minimum allowed value for thisvariable was 8200 for 32-bit platforms and 8228 for 64-bitplatforms. In MySQL 5.5.3 and later the minimum is 128 forall platforms.For additional information about join buffering seeSection 8.2.1.8 Nested-Loop Join Algorithms." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"keep_files_on_create", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for keep_files_on_create", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"94", + "unit":"NULL", + "description":"If a MyISAM table is created with noDATA DIRECTORY option the.MYD file is created in the databasedirectory. By default if MyISAM finds anexisting .MYD file in this case itoverwrites it. The same applies to .MYIfiles for tables created with no INDEXDIRECTORY option. To suppress this behavior set thekeep_files_on_create variableto ON (1) in which caseMyISAM will not overwrite existing filesand returns an error instead. The default value isOFF (0).If a MyISAM table is created with aDATA DIRECTORY or INDEXDIRECTORY option and an existing.MYD or .MYI file isfound MyISAM always returns an error. It will not overwrite afile in the specified directory." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"8388608", + "name":"key_buffer_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"8", + "dynamic":"t", + "rank":"-1", + "summary":"Options for key_buffer_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"95", + "unit":"NULL", + "description":"Index blocks for MyISAM tables are bufferedand are shared by all threads.key_buffer_size is the sizeof the buffer used for index blocks. The key buffer is alsoknown as the key cache.The maximum permissible setting forkey_buffer_size is4GB1 on 32-bit platforms. Larger values are permittedfor 64-bit platforms. The effective maximum size might beless depending on your available physical RAM and per-processRAM limits imposed by your operating system or hardwareplatform. The value of this variable indicates the amount ofmemory requested. Internally the server allocates as muchmemory as possible up to this amount but the actualallocation might be less.You can increase the value to get better index handling forall reads and multiple writes; on a system whose primaryfunction is to run MySQL using theMyISAM storage engine 25% of themachine's total memory is an acceptable value for thisvariable. However you should be aware that if you make thevalue too large (for example more than 50% of themachine's total memory) your system might start to pageand become extremely slow. This is because MySQL relies on theoperating system to perform file system caching for datareads so you must leave some room for the file system cache.You should also consider the memory requirements of any otherstorage engines that you may be using in addition toMyISAM.For even more speed when writing many rows at the same timeuse LOCK TABLES. SeeSection 8.2.2.1 Speed of INSERT Statements.You can check the performance of the key buffer by issuing aSHOW STATUS statement andexamining theKey_read_requestsKey_readsKey_write_requests andKey_writes status variables.(See Section 13.7.5 SHOW Syntax.) TheKey_reads/Key_read_requests ratio shouldnormally be less than 0.01. TheKey_writes/Key_write_requests ratio isusually near 1 if you are using mostly updates and deletesbut might be much smaller if you tend to do updates thataffect many rows at the same time or if you are using theDELAY_KEY_WRITE table option.The fraction of the key buffer in use can be determined usingkey_buffer_size inconjunction with theKey_blocks_unused statusvariable and the buffer block size which is available fromthe key_cache_block_sizesystem variable:This value is an approximation because some space in the keybuffer is allocated internally for administrative structures.Factors that influence the amount of overhead for thesestructures include block size and pointer size. As block sizeincreases the percentage of the key buffer lost to overheadtends to decrease. Larger blocks results in a smaller numberof read operations (because more keys are obtained per read)but conversely an increase in reads of keys that are notexamined (if not all keys in a block are relevant to a query).It is possible to create multiple MyISAMkey caches. The size limit of 4GB applies to each cacheindividually not as a group. SeeSection 8.10.2 The MyISAM Key Cache." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"300", + "name":"key_cache_age_threshold", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"100", + "dynamic":"t", + "rank":"-1", + "summary":"Options for key_cache_age_threshold", + "vartype":"integer", + "max_value":"18446744073709547520", + "scope":"{Global}", + "id":"96", + "unit":"NULL", + "description":"This value controls the demotion of buffers from the hotsublist of a key cache to the warm sublist. Lower values causedemotion to happen more quickly. The minimum value is 100. Thedefault value is 300. See Section 8.10.2 The MyISAM Key Cache." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1024", + "name":"key_cache_block_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"512", + "dynamic":"t", + "rank":"-1", + "summary":"Options for key_cache_block_size", + "vartype":"integer", + "max_value":"16384", + "scope":"{Global}", + "id":"97", + "unit":"NULL", + "description":"The size in bytes of blocks in the key cache. The defaultvalue is 1024. See Section 8.10.2 The MyISAM Key Cache." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"INTERNAL", + "name":"warning_count", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"integer", + "max_value":"NULL", + "scope":"{NA}", + "id":"258", + "unit":"NULL", + "description":"The number of errors warnings and notes that resulted fromthe last statement that generated messages. This variable isread only. See Section 13.7.5.41 SHOW WARNINGS Syntax." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"100", + "name":"key_cache_division_limit", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for key_cache_division_limit", + "vartype":"integer", + "max_value":"100", + "scope":"{Global}", + "id":"98", + "unit":"NULL", + "description":"The division point between the hot and warm sublists of thekey cache buffer list. The value is the percentage of thebuffer list to use for the warm sublist. Permissible valuesrange from 1 to 100. The default value is 100. SeeSection 8.10.2 The MyISAM Key Cache." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"large_files_support", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for large_files_support", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"99", + "unit":"NULL", + "description":"Whether mysqld was compiled with optionsfor large file support." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"FALSE", + "name":"large_pages", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for large-pages", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"100", + "unit":"NULL", + "description":"Whether large page support is enabled (via the--large-pages option). SeeSection 8.12.5.2 Enabling Large Page Support." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"large_page_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for large_page_size", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"101", + "unit":"NULL", + "description":"If large page support is enabled this shows the size ofmemory pages. Large memory pages are supported only on Linux;on other platforms the value of this variable is always 0.See Section 8.12.5.2 Enabling Large Page Support." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"INTERNAL", + "name":"last_insert_id", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"integer", + "max_value":"NULL", + "scope":"{NA}", + "id":"102", + "unit":"NULL", + "description":"The value to be returned fromLAST_INSERT_ID(). This isstored in the binary log when you useLAST_INSERT_ID() in a statementthat updates a table. Setting this variable does not updatethe value returned by themysql_insert_id() C APIfunction." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"en_US", + "name":"lc_messages", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for lc-messages", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"103", + "unit":"NULL", + "description":"The locale to use for error messages. The default isen_US. The server converts the argument toa language name and combines it with the value oflc_messages_dir to producethe location for the error message file. SeeSection 10.2 Setting the Error Message Language." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"lc_messages_dir", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for lc-messages-dir", + "vartype":"directory name", + "max_value":"NULL", + "scope":"{Global}", + "id":"104", + "unit":"NULL", + "description":"The directory where error messages are located. The serveruses the value together with the value oflc_messages to produce thelocation for the error message file. SeeSection 10.2 Setting the Error Message Language." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"LOCALE", + "name":"lc_time_names", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for lc_time_names", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"105", + "unit":"NULL", + "description":"This variable specifies the locale that controls the languageused to display day and month names and abbreviations. Thisvariable affects the output from theDATE_FORMAT()DAYNAME() andMONTHNAME() functions. Localenames are POSIX-style values such as'ja_JP' or 'pt_BR'. Thedefault value is 'en_US' regardless of yoursystem's locale setting. For further information seeSection 10.7 MySQL Server Locale Support." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"GPL", + "name":"license", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for license", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"106", + "unit":"NULL", + "description":"The type of license the server has." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"local_infile", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for local_infile", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"107", + "unit":"NULL", + "description":"Whether LOCAL is supported forLOAD DATAINFILE statements. If this variable is disabledclients cannot use LOCAL inLOAD DATA statements. SeeSection 6.1.6 Security Issues with LOAD DATA LOCAL." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"31536000", + "name":"lock_wait_timeout", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for lock_wait_timeout", + "vartype":"integer", + "max_value":"31536000", + "scope":"{GlobalSession}", + "id":"108", + "unit":"NULL", + "description":"This variable specifies the timeout in seconds for attempts toacquire metadata locks. The permissible values range from 1 to31536000 (1 year). The default is 31536000.This timeout applies to all statements that use metadatalocks. These include DML and DDL operations on tables viewsstored procedures and stored functions as well asLOCK TABLESFLUSH TABLES WITH READLOCK and HANDLERstatements.This timeout does not apply to implicit accesses to systemtables in the mysql database such as granttables modified by GRANT orREVOKE statements or tablelogging statements. The timeout does apply to system tablesaccessed directly such as withSELECT orUPDATE.The timeout value applies separately for each metadata lockattempt. A given statement can require more than one lock soit is possible for the statement to block for longer than thelock_wait_timeout valuebefore reporting a timeout error. When lock timeout occursER_LOCK_WAIT_TIMEOUT isreported.lock_wait_timeout does notapply to delayed inserts which always execute with a timeoutof 1 year. This is done to avoid unnecessary timeouts becausea session that issues a delayed insert receives nonotification of delayed insert timeouts.This variable was added in MySQL 5.5.3." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"locked_in_memory", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for locked_in_memory", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"109", + "unit":"NULL", + "description":"Whether mysqld was locked in memory with--memlock." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1024", + "name":"metadata_locks_cache_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1", + "dynamic":"f", + "rank":"-1", + "summary":"Options for metadata_locks_cache_size", + "vartype":"integer", + "max_value":"1048576", + "scope":"{Global}", + "id":"139", + "unit":"NULL", + "description":"The size of the metadata locks cache. The server uses thiscache to avoid creation and destruction of synchronizationobjects. This is particularly helpful on systems where suchoperations are expensive such as Windows XP. This variablewas added in MySQL 5.5.19." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"6", + "name":"innodb_compression_level", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_compression_level", + "vartype":"integer", + "max_value":"9", + "scope":"{Global}", + "id":"485", + "unit":"NULL", + "description":"Specifies the level of zlib compression to use forInnoDBcompressed tables andindexes.For more information seeSection 14.7.6 Compression for OLTP Workloads." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"FALSE", + "name":"log_bin_trust_function_creators", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for log-bin-trust-function-creators", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"110", + "unit":"NULL", + "description":"This variable applies when binary logging is enabled. Itcontrols whether stored function creators can be trusted notto create stored functions that will cause unsafe events to bewritten to the binary log. If set to 0 (the default) usersare not permitted to create or alter stored functions unlessthey have the SUPER privilegein addition to the CREATEROUTINE or ALTERROUTINE privilege. A setting of 0 also enforces therestriction that a function must be declared with theDETERMINISTIC characteristic or with theREADS SQL DATA or NO SQLcharacteristic. If the variable is set to 1 MySQL does notenforce these restrictions on stored function creation. Thisvariable also applies to trigger creation. SeeSection 20.7 Binary Logging of Stored Programs." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"FALSE", + "name":"log_bin_trust_routine_creators", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{NA}", + "id":"111", + "unit":"NULL", + "description":"This is the old name forlog_bin_trust_function_creators.This variable is deprecated and was removed in MySQL 5.5.3." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"log_error", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for log-error", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"112", + "unit":"NULL", + "description":"The location of the error log or empty if the server iswriting error message to the standard error output. SeeSection 5.4.2 The Error Log." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"FILE", + "name":"log_output", + "deprecated":"f", + "valid_vals":"TABLE,FILE,NONE", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for log-output", + "vartype":"set", + "max_value":"NULL", + "scope":"{Global}", + "id":"113", + "unit":"NULL", + "description":"The destination for general query log and slow query logoutput. The value can be a comma-separated list of one or moreof the words TABLE (log to tables)FILE (log to files) orNONE (do not log to tables or files). Thedefault value is FILE.NONE if present takes precedence over anyother specifiers. If the value is NONE logentries are not written even if the logs are enabled. If thelogs are not enabled no logging occurs even if the value oflog_output is notNONE. For more information seeSection 5.4.1 Selecting General Query and Slow Query Log Output Destinations." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"log_queries_not_using_indexes", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for log-queries-not-using-indexes", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"114", + "unit":"NULL", + "description":"Whether queries that do not use indexes are logged to the slowquery log. See Section 5.4.5 The Slow Query Log." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"log_slow_queries", + "deprecated":"t", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for log-slow-queries", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"115", + "unit":"NULL", + "description":"Whether slow queries should be logged. Slow isdetermined by the value of thelong_query_time variable. SeeSection 5.4.5 The Slow Query Log.This variable is deprecated and is removed in MySQL 5.6. Useslow_query_log instead." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"log_warnings", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for log-warnings", + "vartype":"integer", + "max_value":"18446744073709547520", + "scope":"{GlobalSession}", + "id":"116", + "unit":"NULL", + "description":"Whether to produce additional warning messages to the errorlog. This variable is enabled (1) by default and can bedisabled by setting it to 0. The server logs messages aboutstatements that are unsafe for statement-based logging if thevalue is greater than 0. Aborted connections and access-deniederrors for new connection attempts are logged if the value isgreater than 1." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"10", + "name":"long_query_time", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for long_query_time", + "vartype":"numeric", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"117", + "unit":"NULL", + "description":"If a query takes longer than this many seconds the serverincrements the Slow_queriesstatus variable. If the slow query log is enabled the queryis logged to the slow query log file. This value is measuredin real time not CPU time so a query that is under thethreshold on a lightly loaded system might be above thethreshold on a heavily loaded one. The minimum and defaultvalues of long_query_time are0 and 10 respectively. The value can be specified to aresolution of microseconds. For logging to a file times arewritten including the microseconds part. For logging totables only integer times are written; the microseconds partis ignored. See Section 5.4.5 The Slow Query Log." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"FALSE", + "name":"low_priority_updates", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for low-priority-updates", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"118", + "unit":"NULL", + "description":"If set to 1 allINSERTUPDATEDELETE and LOCK TABLEWRITE statements wait until there is no pendingSELECT or LOCK TABLEREAD on the affected table. This affects onlystorage engines that use only table-level locking (such asMyISAM MEMORY andMERGE). This variable previously was namedsql_low_priority_updates." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"lower_case_file_system", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for lower_case_file_system", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"119", + "unit":"NULL", + "description":"This variable describes the case sensitivity of file names onthe file system where the data directory is located.OFF means file names are case sensitiveON means they are not case sensitive. Thisvariable is read only because it reflects a file systemattribute and setting it would have no effect on the filesystem." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"256", + "name":"multi_range_count", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for multi_range_count", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{GlobalSession}", + "id":"140", + "unit":"NULL", + "description":"The maximum number of ranges to send to a table handler atonce during range selects. The default value is 256. Sendingmultiple ranges to a handler at once can improve theperformance of certain selects dramatically. This isespecially true for theNDBCLUSTER table handler whichneeds to send the range requests to all nodes. Sending a batchof those requests at once reduces communication costssignificantly.This variable is deprecated in MySQL 5.1 and is no longersupported in MySQL 5.5 in which arbitrarily long lists ofranges can be processed." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"lower_case_table_names", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"Options for lower_case_table_names", + "vartype":"integer", + "max_value":"2", + "scope":"{Global}", + "id":"120", + "unit":"NULL", + "description":"If set to 0 table names are stored as specified andcomparisons are case sensitive. If set to 1 table names arestored in lowercase on disk and comparisons are not casesensitive. If set to 2 table names are stored as given butcompared in lowercase. This option also applies to databasenames and table aliases. For additional information seeSection 9.2.2 Identifier Case Sensitivity.On Windows the default value is 1. On OS X the default valueis 2.You should not setlower_case_table_names to 0if you are running MySQL on a system where the data directoryresides on a case-insensitive file system (such as on Windowsor OS X). It is an unsupported combination that could resultin a hang condition when running an INSERT INTO ...SELECT ... FROM tbl_nameoperation with the wrong tbl_nameletter case. With MyISAM accessing tablenames using different letter cases could cause indexcorruption.As of MySQL 5.5.46 an error message is printed and the serverexits if you attempt to start the server with--lower_case_table_names=0 ona case-insensitive file system.If you are using InnoDB tables you shouldset this variable to 1 on all platforms to force names to beconverted to lowercase.The setting of this variable has no effect on replicationfiltering options. This is a known issue which is fixed inMySQL 5.6. See Section 17.2.3 How Servers Evaluate Replication Filtering Rulesfor more information.You should not use different settings forlower_case_table_names on replicationmasters and slaves. In particular you should not do this whenthe slave uses a case-sensitive file system as this can causereplication to fail. This is a known issue which is fixed inMySQL 5.6. For more information seeSection 17.4.1.38 Replication and Variables." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1048576", + "name":"max_allowed_packet", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1024", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_allowed_packet", + "vartype":"integer", + "max_value":"1073741824", + "scope":"{GlobalSession}", + "id":"121", + "unit":"NULL", + "description":"The maximum size of one packet or any generated/intermediatestring.The packet message buffer is initialized tonet_buffer_length bytes butcan grow up tomax_allowed_packet bytes whenneeded. This value by default is small to catch large(possibly incorrect) packets.You must increase this value if you are using largeBLOB columns or long strings.It should be as big as the largestBLOB you want to use. Theprotocol limit formax_allowed_packet is 1GB.The value should be a multiple of 1024; nonmultiples arerounded down to the nearest multiple.When you change the message buffer size by changing the valueof the max_allowed_packetvariable you should also change the buffer size on the clientside if your client program permits it. The defaultmax_allowed_packet valuebuilt in to the client library is 1GB but individual clientprograms might override this. For examplemysql and mysqldump havedefaults of 16MB and 24MB respectively. They also enable youto change the client-side value by settingmax_allowed_packet on thecommand line or in an option file.The session value of this variable is read only. The clientcan receive up to as many bytes as the session value. Howeverthe server will not send to the client more bytes than thecurrent globalmax_allowed_packet value.(The global value could be less than the session value if theglobal value is changed after the client connects.)" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"10", + "name":"max_connect_errors", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_connect_errors", + "vartype":"integer", + "max_value":"18446744073709547520", + "scope":"{Global}", + "id":"122", + "unit":"NULL", + "description":"If more than this many successive connection requests from ahost are interrupted without a successful connection theserver blocks that host from further connections. You canunblock blocked hosts by flushing the host cache. To do soissue a FLUSHHOSTS statement or execute a mysqladminflush-hosts command. If a connection is establishedsuccessfully within fewer thanmax_connect_errors attemptsafter a previous connection was interrupted the error countfor the host is cleared to zero. However once a host isblocked flushing the host cache is the only way to unblockit." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"151", + "name":"max_connections", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_connections", + "vartype":"integer", + "max_value":"100000", + "scope":"{Global}", + "id":"123", + "unit":"NULL", + "description":"The maximum permitted number of simultaneous clientconnections. By default this is 151. SeeSection B.5.2.7 Too many connections for more information.Increasing this value increases the number of file descriptorsthat mysqld requires. SeeSection 8.4.3.1 How MySQL Opens and Closes Tables for comments on file descriptorlimits." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"20", + "name":"max_delayed_threads", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_delayed_threads", + "vartype":"integer", + "max_value":"16384", + "scope":"{GlobalSession}", + "id":"124", + "unit":"NULL", + "description":"Do not start more than this number of threads to handleINSERT DELAYED statements. Ifyou try to insert data into a new table after allINSERT DELAYED threads are inuse the row is inserted as if the DELAYEDattribute was not specified. If you set this to 0 MySQL nevercreates a thread to handle DELAYED rows; ineffect this disables DELAYED entirely.For the SESSION value of this variable theonly valid values are 0 or the GLOBALvalue." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"64", + "name":"max_error_count", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_error_count", + "vartype":"integer", + "max_value":"65535", + "scope":"{GlobalSession}", + "id":"125", + "unit":"NULL", + "description":"The maximum number of error warning and note messages to bestored for display by the SHOWERRORS and SHOWWARNINGS statements." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"16777216", + "name":"max_heap_table_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"16384", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_heap_table_size", + "vartype":"integer", + "max_value":"1844674407370954752", + "scope":"{GlobalSession}", + "id":"126", + "unit":"NULL", + "description":"This variable sets the maximum size to which user-createdMEMORY tables are permitted to grow. Thevalue of the variable is used to calculateMEMORY table MAX_ROWSvalues. Setting this variable has no effect on any existingMEMORY table unless the table isre-created with a statement such asCREATE TABLE or altered withALTER TABLE orTRUNCATE TABLE. A serverrestart also sets the maximum size of existingMEMORY tables to the globalmax_heap_table_size value.This variable is also used in conjunction withtmp_table_size to limit thesize of internal in-memory tables. SeeSection 8.4.4 Internal Temporary Table Use in MySQL.max_heap_table_size is not replicated. SeeSection 17.4.1.23 Replication and MEMORY Tables andSection 17.4.1.38 Replication and Variables for moreinformation." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"20", + "name":"max_insert_delayed_threads", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_insert_delayed_threads", + "vartype":"integer", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"127", + "unit":"NULL", + "description":"This variable is a synonym formax_delayed_threads." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"6", + "name":"myisam_data_pointer_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"2", + "dynamic":"t", + "rank":"-1", + "summary":"Options for myisam_data_pointer_size", + "vartype":"integer", + "max_value":"7", + "scope":"{Global}", + "id":"141", + "unit":"NULL", + "description":"The default pointer size in bytes to be used byCREATE TABLE forMyISAM tables when noMAX_ROWS option is specified. This variablecannot be less than 2 or larger than 7. The default value is6. See Section B.5.2.12 The table is full." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"character_sets_dir", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for character-sets-dir", + "vartype":"directory name", + "max_value":"NULL", + "scope":"{Global}", + "id":"599", + "unit":"NULL", + "description":"The directory where character sets are installed." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"18446744073709551615", + "name":"max_join_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_join_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{GlobalSession}", + "id":"128", + "unit":"NULL", + "description":"Do not permit statements that probably need to examine morethan max_join_size rows (forsingle-table statements) or row combinations (formultiple-table statements) or that are likely to do more thanmax_join_size disk seeks. Bysetting this value you can catch statements where keys arenot used properly and that would probably take a long time.Set it if your users tend to perform joins that lack aWHERE clause that take a long time orthat return millions of rows.Setting this variable to a value other thanDEFAULT resets the value ofsql_big_selects to0. If you set thesql_big_selects value againthe max_join_size variable isignored.If a query result is in the query cache no result size checkis performed because the result has previously been computedand it does not burden the server to send it to the client.This variable previously was namedsql_max_join_size." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1024", + "name":"max_length_for_sort_data", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"4", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_length_for_sort_data", + "vartype":"integer", + "max_value":"8388608", + "scope":"{GlobalSession}", + "id":"129", + "unit":"NULL", + "description":"The cutoff on the size of index values that determines whichfilesort algorithm to use. SeeSection 8.2.1.11 ORDER BY Optimization." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1048576", + "name":"max_long_data_size", + "deprecated":"t", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1024", + "dynamic":"f", + "rank":"-1", + "summary":"Options for max_long_data_size", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{Global}", + "id":"130", + "unit":"NULL", + "description":"The maximum size of parameter values that can be sent with themysql_stmt_send_long_data() CAPI function. If not set at server startup the default is thevalue of themax_allowed_packet systemvariable. This variable is deprecated. In MySQL 5.6 it isremoved and the maximum parameter size is controlled bymax_allowed_packet." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"16382", + "name":"max_prepared_stmt_count", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_prepared_stmt_count", + "vartype":"integer", + "max_value":"1048576", + "scope":"{Global}", + "id":"131", + "unit":"NULL", + "description":"This variable limits the total number of prepared statementsin the server. (The sum of the number of prepared statementsacross all sessions.) It can be used in environments wherethere is the potential for denial-of-service attacks based onrunning the server out of memory by preparing huge numbers ofstatements. If the value is set lower than the current numberof prepared statements existing statements are not affectedand can be used but no new statements can be prepared untilthe current number drops below the limit. The default value is16382. The permissible range of values is from 0 to 1million. Setting the value to 0 disables prepared statements." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"max_relay_log_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_relay_log_size", + "vartype":"integer", + "max_value":"1073741824", + "scope":"{Global}", + "id":"132", + "unit":"NULL", + "description":"If a write by a replication slave to its relay log causes thecurrent log file size to exceed the value of this variablethe slave rotates the relay logs (closes the current file andopens the next one). Ifmax_relay_log_size is 0 theserver uses max_binlog_sizefor both the binary log and the relay log. Ifmax_relay_log_size is greaterthan 0 it constrains the size of the relay log which enablesyou to have different sizes for the two logs. You must setmax_relay_log_size to between4096 bytes and 1GB (inclusive) or to 0. The default value is0. See Section 17.2.1 Replication Implementation Details." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"18446744073709547520", + "name":"max_seeks_for_key", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_seeks_for_key", + "vartype":"integer", + "max_value":"18446744073709547520", + "scope":"{GlobalSession}", + "id":"133", + "unit":"NULL", + "description":"Limit the assumed maximum number of seeks when looking up rowsbased on a key. The MySQL optimizer assumes that no more thanthis number of key seeks are required when searching formatching rows in a table by scanning an index regardless ofthe actual cardinality of the index (seeSection 13.7.5.23 SHOW INDEX Syntax). By setting this to a low value(say 100) you can force MySQL to prefer indexes instead oftable scans." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1024", + "name":"max_sort_length", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"4", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_sort_length", + "vartype":"integer", + "max_value":"8388608", + "scope":"{GlobalSession}", + "id":"134", + "unit":"NULL", + "description":"The number of bytes to use when sorting data values. Theserver uses only the firstmax_sort_length bytes of eachvalue and ignores the rest. Consequently values that differonly after the firstmax_sort_length bytes compareas equal for GROUP BY ORDERBY and DISTINCT operations.Increasing the value ofmax_sort_length may requireincreasing the value ofsort_buffer_size as well. Fordetails see Section 8.2.1.11 ORDER BY Optimization" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"max_sp_recursion_depth", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_sp_recursion_depth", + "vartype":"integer", + "max_value":"255", + "scope":"{GlobalSession}", + "id":"135", + "unit":"NULL", + "description":"The number of times that any given stored procedure may becalled recursively. The default value for this option is 0which completely disables recursion in stored procedures. Themaximum value is 255.Stored procedure recursion increases the demand on threadstack space. If you increase the value ofmax_sp_recursion_depth itmay be necessary to increase thread stack size by increasingthe value of thread_stack atserver startup." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"max_tmp_tables", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"integer", + "max_value":"NULL", + "scope":"{NA}", + "id":"136", + "unit":"NULL", + "description":"This variable is unused." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"max_user_connections", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_user_connections", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{GlobalSession}", + "id":"137", + "unit":"NULL", + "description":"The maximum number of simultaneous connections permitted toany given MySQL user account. A value of 0 (the default) meansno limit.This variable has a global value that can be set at serverstartup or runtime. It also has a read-only session value thatindicates the effective simultaneous-connection limit thatapplies to the account associated with the current session.The session value is initialized as follows:Account resource limits are specified using theGRANT statement. SeeSection 6.3.4 Setting Account Resource Limits and Section 13.7.1.3 GRANT Syntax." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"9223372036854775807", + "name":"myisam_max_sort_file_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for myisam_max_sort_file_size", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"142", + "unit":"NULL", + "description":"The maximum size of the temporary file that MySQL is permittedto use while re-creating a MyISAM index(during REPAIR TABLEALTER TABLE orLOAD DATAINFILE). If the file size would be larger than thisvalue the index is created using the key cache instead whichis slower. The value is given in bytes.If MyISAM index files exceed this size anddisk space is available increasing the value may helpperformance. The space must be available in the file systemcontaining the directory where the original index file islocated." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"18446744073709547520", + "name":"myisam_mmap_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"7", + "dynamic":"f", + "rank":"-1", + "summary":"Options for myisam_mmap_size", + "vartype":"integer", + "max_value":"18446744073709547520", + "scope":"{Global}", + "id":"143", + "unit":"NULL", + "description":"The maximum amount of memory to use for memory mappingcompressed MyISAM files. If manycompressed MyISAM tables are used thevalue can be decreased to reduce the likelihood ofmemory-swapping problems. This variable was added in MySQL5.5.1." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"BACKUP", + "name":"myisam_recover_options", + "deprecated":"f", + "valid_vals":"OFF,DEFAULT,BACKUP,FORCE,QUICK,", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for myisam_recover_options", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"144", + "unit":"NULL", + "description":"The value of the--myisam-recover-optionsoption. See Section 5.1.3 Server Command Options." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"myisam_repair_threads", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for myisam_repair_threads", + "vartype":"integer", + "max_value":"18446744073709547520", + "scope":"{Global,Session}", + "id":"145", + "unit":"NULL", + "description":"If this value is greater than 1 MyISAMtable indexes are created in parallel (each index in its ownthread) during the Repair by sortingprocess. The default value is 1." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"8388608", + "name":"myisam_sort_buffer_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"4096", + "dynamic":"t", + "rank":"-1", + "summary":"Options for myisam_sort_buffer_size", + "vartype":"integer", + "max_value":"18446744073709547520", + "scope":"{GlobalSession}", + "id":"146", + "unit":"NULL", + "description":"The size of the buffer that is allocated when sortingMyISAM indexes during aREPAIR TABLE or when creatingindexes with CREATE INDEX orALTER TABLE.The maximum permissible setting formyisam_sort_buffer_size is4GB1. Larger values are permitted for 64-bit platforms(except 64-bit Windows prior to MySQL 5.5.222 for which largevalues are truncated to 4GB1 with a warning)." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"nulls_unequal", + "name":"myisam_stats_method", + "deprecated":"f", + "valid_vals":"nulls_equal,nulls_unequal,nulls_ignored", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for myisam_stats_method", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"147", + "unit":"NULL", + "description":"How the server treats NULL values whencollecting statistics about the distribution of index valuesfor MyISAM tables. This variable has threepossible values nulls_equalnulls_unequal andnulls_ignored. Fornulls_equal all NULLindex values are considered equal and form a single valuegroup that has a size equal to the number ofNULL values. Fornulls_unequal NULLvalues are considered unequal and eachNULL forms a distinct value group of size1. For nulls_ignoredNULL values are ignored.The method that is used for generating table statisticsinfluences how the optimizer chooses indexes for queryexecution as described in Section 8.3.7 InnoDB and MyISAM Index Statistics Collection." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"myisam_use_mmap", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for myisam_use_mmap", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"148", + "unit":"NULL", + "description":"Use memory mapping for reading and writingMyISAM tables." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"named_pipe", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for named_pipe", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"149", + "unit":"NULL", + "description":"(Windows only.) Indicates whether the server supportsconnections over named pipes." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"16384", + "name":"net_buffer_length", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1024", + "dynamic":"t", + "rank":"-1", + "summary":"Options for net_buffer_length", + "vartype":"integer", + "max_value":"1048576", + "scope":"{GlobalSession}", + "id":"150", + "unit":"NULL", + "description":"Each client thread is associated with a connection buffer andresult buffer. Both begin with a size given bynet_buffer_length but aredynamically enlarged up tomax_allowed_packet bytes asneeded. The result buffer shrinks tonet_buffer_length after eachSQL statement.This variable should not normally be changed but if you havevery little memory you can set it to the expected length ofstatements sent by clients. If statements exceed this lengththe connection buffer is automatically enlarged. The maximumvalue to whichnet_buffer_length can be setis 1MB.The session value of this variable is read only." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"30", + "name":"net_read_timeout", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for net_read_timeout", + "vartype":"integer", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"151", + "unit":"NULL", + "description":"The number of seconds to wait for more data from a connectionbefore aborting the read. When the server is reading from theclient net_read_timeout isthe timeout value controlling when to abort. When the serveris writing to the clientnet_write_timeout is thetimeout value controlling when to abort. See alsoslave_net_timeout." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"10", + "name":"net_retry_count", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for net_retry_count", + "vartype":"integer", + "max_value":"18446744073709547520", + "scope":"{GlobalSession}", + "id":"152", + "unit":"NULL", + "description":"If a read or write on a communication port is interruptedretry this many times before giving up. This value should beset quite high on FreeBSD because internal interrupts are sentto all threads." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"60", + "name":"net_write_timeout", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for net_write_timeout", + "vartype":"integer", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"153", + "unit":"NULL", + "description":"The number of seconds to wait for a block to be written to aconnection before aborting the write. See alsonet_read_timeout." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"ssl_cert", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for ssl-cert", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"223", + "unit":"NULL", + "description":"The name of the SSL certificate file to use for establishing asecure connection." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"FALSE", + "name":"new", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for new", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"154", + "unit":"NULL", + "description":"This variable was used in MySQL 4.0 to turn on some 4.1behaviors and is retained for backward compatibility. Itsvalue is always OFF.In MySQL Cluster setting this variable toON makes it possible to employ partitioningtypes other than KEY or LINEARKEY with NDB tables.This feature is experimental only and not supportedin production. For additional information seeUser-defined partitioning and the NDB storage engine (MySQL Cluster)." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"old", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for old", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"155", + "unit":"NULL", + "description":"old is a compatibilityvariable. It is disabled by default but can be enabled atstartup to revert the server to behaviors present in olderversions.When old is enabled itchanges the default scope of index hints to that used prior toMySQL 5.1.17. That is index hints with noFOR clause apply only to how indexes areused for row retrieval and not to resolution of ORDERBY or GROUP BY clauses. (SeeSection 8.9.3 Index Hints.) Take care about enabling thisin a replication setup. With statement-based binary logginghaving different modes for the master and slaves might lead toreplication errors." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"old_alter_table", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for old-alter-table", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"156", + "unit":"NULL", + "description":"When this variable is enabled the server does not use theoptimized method of processing an ALTERTABLE operation. It reverts to using a temporarytable copying over the data and then renaming the temporarytable to the original as used by MySQL 5.0 and earlier. Formore information on the operation ofALTER TABLE seeSection 13.1.7 ALTER TABLE Syntax." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"old_passwords", + "deprecated":"f", + "valid_vals":"1,0", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for old_passwords", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global,Session}", + "id":"157", + "unit":"NULL", + "description":"This variable controls the password hashing method used by thePASSWORD() function. It alsoinfluences password hashing performed byCREATE USER andGRANT statements that specify apassword using an IDENTIFIED BY clause.The following table shows the permitted values ofold_passwords the passwordhashing method for each value and which authenticationplugins use passwords hashed with each method.If old_passwords=1PASSWORD(str)returns the same value asOLD_PASSWORD(str).The latter function is not affected by the value ofold_passwords.For additional information about authentication plugins andhashing formats seeSection 6.3.6 Pluggable Authentication andSection 6.1.2.4 Password Hashing in MySQL." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"open_files_limit", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"Options for open-files-limit", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"158", + "unit":"NULL", + "description":"The number of files that the operating system permitsmysqld to open. This is the real valuepermitted by the system and might be different from the valueyou gave using the--open-files-limit option tomysqld or mysqld_safe.The value is 0 on systems where MySQL cannot change the numberof open files." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"optimizer_prune_level", + "deprecated":"f", + "valid_vals":"1,0", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for optimizer_prune_level", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"159", + "unit":"NULL", + "description":"Controls the heuristics applied during query optimization toprune less-promising partial plans from the optimizer searchspace. A value of 0 disables heuristics so that the optimizerperforms an exhaustive search. A value of 1 causes theoptimizer to prune plans based on the number of rows retrievedby intermediate plans." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"62", + "name":"optimizer_search_depth", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for optimizer_search_depth", + "vartype":"integer", + "max_value":"63", + "scope":"{GlobalSession}", + "id":"160", + "unit":"NULL", + "description":"The maximum depth of search performed by the query optimizer.Values larger than the number of relations in a query resultin better query plans but take longer to generate anexecution plan for a query. Values smaller than the number ofrelations in a query return an execution plan quicker but theresulting plan may be far from being optimal. If set to 0 thesystem automatically picks a reasonable value. If set to 63the optimizer switches to the algorithm used in MySQL 5.0.0(and previous versions) for performing searches. The value of63 is deprecated and will be treated as invalid in a futureMySQL release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"index_merge=onindex_merge_union=on index_merge_sort_union=onindex_merge_intersection=on engine_condition_pushdown=on", + "name":"optimizer_switch", + "deprecated":"f", + "valid_vals":"index_merge=on|off,index_merge_intersection=on|off,index_merge_sort_union=on|off,index_merge_union=on|off", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for optimizer_switch", + "vartype":"set", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"161", + "unit":"NULL", + "description":"The optimizer_switch systemvariable enables control over optimizer behavior. The value ofthis variable is a set of flags each of which has a value ofon or off to indicatewhether the corresponding optimizer behavior is enabled ordisabled. This variable has global and session values and canbe changed at runtime. The global default can be set at serverstartup.To see the current set of optimizer flags select the variablevalue:For more information about the syntax of this variable and theoptimizer behaviors that it controls seeSection 8.9.2 Controlling Switchable Optimizations." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"pid_file", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for pid-file", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"162", + "unit":"NULL", + "description":"The path name of the process ID (PID) file. This variable canbe set with the --pid-fileoption." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"ssl_cipher", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for ssl-cipher", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"224", + "unit":"NULL", + "description":"A list of permissible ciphers to use for SSL encryption." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"ssl_key", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for ssl-key", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"225", + "unit":"NULL", + "description":"The name of the SSL key file to use for establishing a secureconnection." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"BASEDIR/lib/mysql/plugin", + "name":"plugin_dir", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for plugin_dir", + "vartype":"directory name", + "max_value":"NULL", + "scope":"{Global}", + "id":"163", + "unit":"NULL", + "description":"The path name of the plugin directory.If the plugin directory is writable by the server it may bepossible for a user to write executable code to a file in thedirectory using SELECT... INTO DUMPFILE. This can be prevented by makingplugin_dir read only to theserver or by setting--secure-file-priv to adirectory where SELECT writescan be made safely." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"32768", + "name":"preload_buffer_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1024", + "dynamic":"t", + "rank":"-1", + "summary":"Options for preload_buffer_size", + "vartype":"integer", + "max_value":"1073741824", + "scope":"{GlobalSession}", + "id":"164", + "unit":"NULL", + "description":"The size of the buffer that is allocated when preloadingindexes." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"profiling", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{NA}", + "id":"165", + "unit":"NULL", + "description":"If set to 0 or OFF (the default) statementprofiling is disabled. If set to 1 or ONstatement profiling is enabled and theSHOW PROFILE andSHOW PROFILES statementsprovide access to profiling information. SeeSection 13.7.5.32 SHOW PROFILES Syntax." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"15", + "name":"profiling_history_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"integer", + "max_value":"100", + "scope":"{NA}", + "id":"166", + "unit":"NULL", + "description":"The number of statements for which to maintain profilinginformation if profiling isenabled. The default value is 15. The maximum value is 100.Setting the value to 0 effectively disables profiling. SeeSection 13.7.5.32 SHOW PROFILES Syntax." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"protocol_version", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for protocol_version", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"167", + "unit":"NULL", + "description":"The version of the client/server protocol used by the MySQLserver." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"proxy_user", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for proxy_user", + "vartype":"string", + "max_value":"NULL", + "scope":"{Session}", + "id":"168", + "unit":"NULL", + "description":"If the current client is a proxy for another user thisvariable is the proxy user account name. Otherwise thisvariable is NULL. SeeSection 6.3.7 Proxy Users.This variable was added in MySQL 5.5.7." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"INTERNAL", + "name":"pseudo_slave_mode", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for pseudo_slave_mode", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Session}", + "id":"169", + "unit":"NULL", + "description":"This variable is for internal server use. It was added inMySQL 5.5.30." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"INTERNAL", + "name":"pseudo_thread_id", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for pseudo_thread_id", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Session}", + "id":"170", + "unit":"NULL", + "description":"This variable is for internal server use." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"8192", + "name":"query_alloc_block_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1024", + "dynamic":"t", + "rank":"-1", + "summary":"Options for query_alloc_block_size", + "vartype":"integer", + "max_value":"18446744073709547520", + "scope":"{GlobalSession}", + "id":"171", + "unit":"1024", + "description":"The allocation size of memory blocks that are allocated forobjects created during statement parsing and execution. If youhave problems with memory fragmentation it might help toincrease this parameter." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1048576", + "name":"query_cache_limit", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for query_cache_limit", + "vartype":"integer", + "max_value":"18446744073709547520", + "scope":"{Global}", + "id":"172", + "unit":"NULL", + "description":"Do not cache results that are larger than this number ofbytes. The default value is 1MB." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"4096", + "name":"query_cache_min_res_unit", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"512", + "dynamic":"t", + "rank":"-1", + "summary":"Options for query_cache_min_res_unit", + "vartype":"integer", + "max_value":"18446744073709547520", + "scope":"{Global}", + "id":"173", + "unit":"NULL", + "description":"The minimum size (in bytes) for blocks allocated by the querycache. The default value is 4096 (4KB). Tuning information forthis variable is given inSection 8.10.3.3 Query Cache Configuration." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"query_cache_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for query_cache_size", + "vartype":"integer", + "max_value":"18446744073709547520", + "scope":"{Global}", + "id":"174", + "unit":"NULL", + "description":"The amount of memory allocated for caching query results. Thedefault value is 0 which disables the query cache. To reduceoverhead significantly you should also start the server withquery_cache_type=0 if youwill not be using the query cache. The permissible values aremultiples of 1024; other values are rounded down to thenearest multiple.query_cache_size bytes ofmemory are allocated even ifquery_cache_type is set to 0.See Section 8.10.3.3 Query Cache Configuration for moreinformation.The query cache needs a minimum size of about 40KB to allocateits structures. (The exact size depends on systemarchitecture.) If you set the value ofquery_cache_size too small awarning will occur as described inSection 8.10.3.3 Query Cache Configuration." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1", + "name":"query_cache_type", + "deprecated":"f", + "valid_vals":"0,1,2", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for query_cache_type", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"175", + "unit":"NULL", + "description":"Set the query cache type. Setting theGLOBAL value sets the type for all clientsthat connect thereafter. Individual clients can set theSESSION value to affect their own use ofthe query cache. Possible values are shown in the followingtable.This variable defaults to ON.If the server is started withquery_cache_type set to 0 it does notacquire the query cache mutex at all which means that thequery cache cannot be enabled at runtime and there is reducedoverhead in query execution." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"FALSE", + "name":"query_cache_wlock_invalidate", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for query_cache_wlock_invalidate", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"176", + "unit":"NULL", + "description":"Normally when one client acquires a WRITElock on a MyISAM table other clients arenot blocked from issuing statements that read from the tableif the query results are present in the query cache. Settingthis variable to 1 causes acquisition of aWRITE lock for a table to invalidate anyqueries in the query cache that refer to the table. Thisforces other clients that attempt to access the table to waitwhile the lock is in effect." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"0.2", + "name":"autovacuum_vacuum_scale_factor", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Number of tuple updates or deletes prior to vacuum as a fraction of reltuples.", + "vartype":"real", + "max_value":"100", + "scope":"{Global}", + "id":"1471", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"8192", + "name":"query_prealloc_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"8192", + "dynamic":"t", + "rank":"-1", + "summary":"Options for query_prealloc_size", + "vartype":"integer", + "max_value":"18446744073709547520", + "scope":"{GlobalSession}", + "id":"177", + "unit":"1024", + "description":"The size of the persistent buffer used for statement parsingand execution. This buffer is not freed between statements. Ifyou are running complex queries a largerquery_prealloc_size valuemight be helpful in improving performance because it canreduce the need for the server to perform memory allocationduring query execution operations." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"rand_seed1", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"integer", + "max_value":"NULL", + "scope":"{NA}", + "id":"178", + "unit":"NULL", + "description":"The rand_seed1 andrand_seed2 variables exist assession variables only and can be set but not read. Thevariablesbut not their valuesare shown in theoutput of SHOW VARIABLES.The purpose of these variables is to support replication ofthe RAND() function. Forstatements that invoke RAND()the master passes two values to the slave where they are usedto seed the random number generator. The slave uses thesevalues to set the session variablesrand_seed1 andrand_seed2 so thatRAND() on the slave generatesthe same value as on the master." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"rand_seed2", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"integer", + "max_value":"NULL", + "scope":"{NA}", + "id":"179", + "unit":"NULL", + "description":"See the description forrand_seed1." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"4096", + "name":"range_alloc_block_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"4096", + "dynamic":"t", + "rank":"-1", + "summary":"Options for range_alloc_block_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{GlobalSession}", + "id":"180", + "unit":"1024", + "description":"The size of blocks that are allocated when doing rangeoptimization." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"131072", + "name":"read_buffer_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"8200", + "dynamic":"t", + "rank":"-1", + "summary":"Options for read_buffer_size", + "vartype":"integer", + "max_value":"2147479552", + "scope":"{GlobalSession}", + "id":"181", + "unit":"NULL", + "description":"Each thread that does a sequential scan for aMyISAM table allocates a buffer of thissize (in bytes) for each table it scans. If you do manysequential scans you might want to increase this value whichdefaults to 131072. The value of this variable should be amultiple of 4KB. If it is set to a value that is not amultiple of 4KB its value will be rounded down to the nearestmultiple of 4KB.This option is also used in the following context for allstorage engines:and in one other storage engine-specific way: to determine thememory block size for MEMORYtables.The maximum permissible setting forread_buffer_size is 2GB.For more information about memory use during differentoperations see Section 8.12.5.1 How MySQL Uses Memory." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"read_only", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for read_only", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"182", + "unit":"NULL", + "description":"When the read_only systemvariable is enabled the server permits no client updatesexcept from users who have theSUPER privilege. This variableis disabled by default.Even with read_only enabledthe server permits these operations:read_only exists only as aGLOBAL variable so changes to its valuerequire the SUPER privilege.Changes to read_only on amaster server are not replicated to slave servers. The valuecan be set on a slave server independent of the setting on themaster.The following conditions apply to attempts to enableread_only:" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"262144", + "name":"read_rnd_buffer_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"8200", + "dynamic":"t", + "rank":"-1", + "summary":"Options for read_rnd_buffer_size", + "vartype":"integer", + "max_value":"2147483647", + "scope":"{GlobalSession}", + "id":"183", + "unit":"NULL", + "description":"When reading rows from a MyISAM table insorted order following a key-sorting operation the rows areread through this buffer to avoid disk seeks. SeeSection 8.2.1.11 ORDER BY Optimization. Setting the variableto a large value can improve ORDER BYperformance by a lot. However this is a buffer allocated foreach client so you should not set the global variable to alarge value. Instead change the session variable only fromwithin those clients that need to run large queries.The maximum permissible setting forread_rnd_buffer_size is 2GB.For more information about memory use during differentoperations see Section 8.12.5.1 How MySQL Uses Memory." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"TRUE", + "name":"relay_log_purge", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for relay_log_purge", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"184", + "unit":"NULL", + "description":"Disables or enables automatic purging of relay log files assoon as they are not needed any more. The default value is 1(ON)." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"relay_log_space_limit", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"Options for relay_log_space_limit", + "vartype":"integer", + "max_value":"18446744073709547520", + "scope":"{Global}", + "id":"185", + "unit":"NULL", + "description":"The maximum amount of space to use for all relay logs." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"report_host", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for report-host", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"186", + "unit":"NULL", + "description":"The value of the --report-hostoption." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"report_password", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for report-password", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"187", + "unit":"NULL", + "description":"The value of the--report-password option. Notthe same as the password used for the MySQL replication useraccount." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"report_port", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"Options for report-port", + "vartype":"integer", + "max_value":"65535", + "scope":"{Global}", + "id":"188", + "unit":"NULL", + "description":"The value of the --report-portoption." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"report_user", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for report-user", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"189", + "unit":"NULL", + "description":"The value of the --report-useroption. Not the same as the name for the MySQL replicationuser account." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"rpl_semi_sync_master_enabled", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for rpl_semi_sync_master_enabled", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"190", + "unit":"NULL", + "description":"Controls whether semisynchronous replication is enabled on themaster. To enable or disable the plugin set this variable toON or OFF (or 1 or 0)respectively. The default is OFF.This variable is available only if the master-sidesemisynchronous replication plugin is installed." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"10000", + "name":"rpl_semi_sync_master_timeout", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for rpl_semi_sync_master_timeout", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"191", + "unit":"NULL", + "description":"A value in milliseconds that controls how long the masterwaits on a commit for acknowledgment from a slave beforetiming out and reverting to asynchronous replication. Thedefault value is 10000 (10 seconds).This variable is available only if the master-sidesemisynchronous replication plugin is installed." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"32", + "name":"rpl_semi_sync_master_trace_level", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for rpl_semi_sync_master_trace_level", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"192", + "unit":"NULL", + "description":"The semisynchronous replication debug trace level on themaster. Four levels are defined:This variable is available only if the master-sidesemisynchronous replication plugin is installed." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"rpl_semi_sync_master_wait_no_slave", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for rpl_semi_sync_master_wait_no_slave", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"193", + "unit":"NULL", + "description":"With semisynchronous replication for each transaction themaster waits until timeout for acknowledgment of receipt fromsome semisynchronous slave. If no response occurs during thisperiod the master reverts to normal replication. Thisvariable controls whether the master waits for the timeout toexpire before reverting to normal replication even if theslave count drops to zero during the timeout period.If the value is ON (the default) it ispermissible for the slave count to drop to zero during thetimeout period (for example if slaves disconnect). The masterstill waits for the timeout so as long as some slavereconnects and acknowledges the transaction within the timeoutinterval semisynchronous replication continues.If the value is OFF the master reverts tonormal replication if the slave count drops to zero during thetimeout period.This variable is available only if the master-sidesemisynchronous replication plugin is installed." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"rpl_semi_sync_slave_enabled", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for rpl_semi_sync_slave_enabled", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"194", + "unit":"NULL", + "description":"Controls whether semisynchronous replication is enabled on theslave. To enable or disable the plugin set this variable toON or OFF (or 1 or 0)respectively. The default is OFF.This variable is available only if the slave-sidesemisynchronous replication plugin is installed." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"32", + "name":"rpl_semi_sync_slave_trace_level", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for rpl_semi_sync_slave_trace_level", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"195", + "unit":"NULL", + "description":"The semisynchronous replication debug trace level on theslave. Seerpl_semi_sync_master_trace_levelfor the permissible values.This variable is available only if the slave-sidesemisynchronous replication plugin is installed." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"secure_auth", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for secure-auth", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"196", + "unit":"NULL", + "description":"If this variable is enabled the server blocks connections byclients that attempt to use accounts that have passwordsstored in the old (pre-4.1) format.Enable this variable to prevent all use of passwords employingthe old format (and hence insecure communication over thenetwork).Server startup fails with an error if this variable is enabledand the privilege tables are in pre-4.1 format. SeeSection B.5.2.4 Client does not support authentication protocol." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"empty", + "name":"secure_file_priv", + "deprecated":"f", + "valid_vals":"empty,dirname", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for secure-file-priv", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"197", + "unit":"NULL", + "description":"This variable is used to limit the effect of data import andexport operations such as those performed by theLOAD DATA andSELECT ... INTOOUTFILE statements and theLOAD_FILE() function. Bydefault this variable is empty. If set to the name of adirectory it limits import and export operations to work onlywith files in that directory." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"server_id", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for server-id", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{Global}", + "id":"198", + "unit":"NULL", + "description":"The server ID used in replication to give each master andslave a unique identity. This variable is set by the--server-id option. For eachserver participating in replication you should pick apositive integer in the range from 1 to2321 to act as thatserver's ID." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"FALSE", + "name":"shared_memory", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for shared_memory", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"199", + "unit":"NULL", + "description":"(Windows only.) Whether the server permits shared-memoryconnections." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"MYSQL", + "name":"shared_memory_base_name", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for shared_memory_base_name", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"200", + "unit":"NULL", + "description":"(Windows only.) The name of shared memory to use forshared-memory connections. This is useful when runningmultiple MySQL instances on a single physical machine. Thedefault name is MYSQL. The name is casesensitive." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"skip_external_locking", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for skip_external_locking", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"201", + "unit":"NULL", + "description":"This is OFF if mysqlduses external locking (system locking) ONif external locking is disabled. This affects onlyMyISAM table access.This variable is set by the--external-locking or--skip-external-lockingoption. External locking is disabled by default.External locking affects onlyMyISAM table access. For moreinformation including conditions under which it can andcannot be used see Section 8.11.5 External Locking." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"MyISAM", + "name":"storage_engine", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for storage_engine", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"226", + "unit":"NULL", + "description":"The default storage engine (table type). To set the storageengine at server startup use the--default-storage-engineoption. See Section 5.1.3 Server Command Options.This variable is deprecated as of MySQL 5.5.3. Usedefault_storage_engineinstead." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"skip_name_resolve", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for skip-name-resolve", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"202", + "unit":"NULL", + "description":"This variable is set from the value of the--skip-name-resolve option. Ifit is OFF mysqldresolves host names when checking client connections. If it isON mysqld uses only IPnumbers; in this case all Host columnvalues in the grant tables must be IP addresses orlocalhost. SeeSection 8.12.6.2 DNS Lookup Optimization and the Host Cache.This variable was added in MySQL 5.5.5." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"skip_networking", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for skip-networking", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"203", + "unit":"NULL", + "description":"This is ON if the server permits only local(non-TCP/IP) connections. On Unix local connections use aUnix socket file. On Windows local connections use a namedpipe or shared memory. This variable can be set toON with the--skip-networking option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"skip_show_database", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for skip-show-database", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"204", + "unit":"NULL", + "description":"This prevents people from using the SHOWDATABASES statement if they do not have theSHOW DATABASES privilege. Thiscan improve security if you have concerns about users beingable to see databases belonging to other users. Its effectdepends on the SHOW DATABASESprivilege: If the variable value is ON theSHOW DATABASES statement ispermitted only to users who have the SHOWDATABASES privilege and the statement displays alldatabase names. If the value is OFFSHOW DATABASES is permitted toall users but displays the names of only those databases forwhich the user has the SHOWDATABASES or other privilege. (Note thatany global privilege is considered aprivilege for the database.)" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"2", + "name":"slow_launch_time", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for slow_launch_time", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"205", + "unit":"NULL", + "description":"If creating a thread takes longer than this many seconds theserver increments theSlow_launch_threads statusvariable." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"slow_query_log", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for slow-query-log", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"206", + "unit":"NULL", + "description":"Whether the slow query log is enabled. The value can be 0 (orOFF) to disable the log or 1 (orON) to enable the log. The default valuedepends on whether the--slow_query_log option isgiven. The destination for log output is controlled by thelog_output system variable;if that value is NONE no log entries arewritten even if the log is enabled.Slow is determined by the value of thelong_query_time variable. SeeSection 5.4.5 The Slow Query Log." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"host_name-slow.log", + "name":"slow_query_log_file", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for slow_query_log_file", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"207", + "unit":"NULL", + "description":"The name of the slow query log file. The default value ishost_name-slow.logbut the initial value can be changed with the--slow_query_log_file option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"2097144", + "name":"sort_buffer_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"32768", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sort_buffer_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{GlobalSession}", + "id":"208", + "unit":"NULL", + "description":"Each session that must perform a sort allocates a buffer ofthis size. sort_buffer_sizeis not specific to any storage engine and applies in a generalmanner for optimization. At minimum thesort_buffer_size value mustbe large enough to accommodate fifteen tuples in the sortbuffer. Also increasing the value ofmax_sort_length may requireincreasing the value ofsort_buffer_size. For moreinformation see Section 8.2.1.11 ORDER BY OptimizationIf you see manySort_merge_passes per secondin SHOW GLOBALSTATUS output you can consider increasing thesort_buffer_size value tospeed up ORDER BY or GROUPBY operations that cannot be improved with queryoptimization or improved indexing. The entire buffer isallocated even if it is not all needed so setting it largerthan required globally will slow down most queries that sort.It is best to increase it as a session setting and only forthe sessions that need a larger size. On Linux there arethresholds of 256KB and 2MB where larger values maysignificantly slow down memory allocation so you shouldconsider staying below one of those values. Experiment to findthe best value for your workload. SeeSection B.5.3.5 Where MySQL Stores Temporary Files.The maximum permissible setting forsort_buffer_size is4GB1. Larger values are permitted for 64-bit platforms(except 64-bit Windows for which large values are truncatedto 4GB1 with a warning)." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"sql_auto_is_null", + "deprecated":"f", + "valid_vals":"1,0", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sql_auto_is_null", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"209", + "unit":"NULL", + "description":"If this variable is set to 1 then after a statement thatsuccessfully inserts an automatically generatedAUTO_INCREMENT value you can find thatvalue by issuing a statement of the following form:If the statement returns a row the value returned is the sameas if you invoked theLAST_INSERT_ID() function. Fordetails including the return value after a multiple-rowinsert see Section 12.14 Information Functions. If noAUTO_INCREMENT value was successfullyinserted the SELECT statementreturns no row.The behavior of retrieving anAUTO_INCREMENT value by using anIS NULL comparison is used bysome ODBC programs such as Access. SeeObtaining Auto-Increment Values.This behavior can be disabled by settingsql_auto_is_null to 0.The default value ofsql_auto_is_null is 0 as ofMySQL 5.5.3 and 1 for earlier versions." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"thread_pool_algorithm", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"Options for thread_pool_algorithm", + "vartype":"integer", + "max_value":"1", + "scope":"{Global}", + "id":"237", + "unit":"NULL", + "description":"This variable controls which algorithm the thread pool pluginuses:" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"COLLATION", + "name":"collation_connection", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for collation_connection", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"600", + "unit":"NULL", + "description":"The collation of the connection character set." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"sql_big_selects", + "deprecated":"f", + "valid_vals":"1,0", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sql_big_selects", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"210", + "unit":"NULL", + "description":"If set to 0 MySQL abortsSELECT statements that arelikely to take a very long time to execute (that isstatements for which the optimizer estimates that the numberof examined rows exceeds the value ofmax_join_size). This isuseful when an inadvisable WHERE statementhas been issued. The default value for a new connection is 1which permits all SELECTstatements.If you set the max_join_sizesystem variable to a value other thanDEFAULTsql_big_selects is set to 0." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"sql_buffer_result", + "deprecated":"f", + "valid_vals":"1,0", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sql_buffer_result", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"211", + "unit":"NULL", + "description":"If set to 1sql_buffer_result forcesresults from SELECT statementsto be put into temporary tables. This helps MySQL free thetable locks early and can be beneficial in cases where ittakes a long time to send results to the client. The defaultvalue is 0." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"sql_log_bin", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sql_log_bin", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Session}", + "id":"212", + "unit":"NULL", + "description":"This variable controls whether logging to the binary log isdone. The default value is 1 (do logging). To change loggingfor the current session change the session value of thisvariable. The session user must have theSUPER privilege to set thisvariable.Beginning with MySQL 5.5.5 it is no longer possible to set@@session.sql_log_bin within a transactionor subquery. (Bug #53437)" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"sql_log_off", + "deprecated":"f", + "valid_vals":"1,0", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sql_log_off", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"213", + "unit":"NULL", + "description":"This variable controls whether logging to the general querylog is done. The default value is 0 (do logging). To changelogging for the current session change the session value ofthis variable. The session user must have theSUPER privilege to set thisoption. The default value is 0." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"sql_log_update", + "deprecated":"t", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sql_log_update", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Session}", + "id":"214", + "unit":"NULL", + "description":"This variable is deprecated and is mapped tosql_log_bin. It was removedin MySQL 5.5.3." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"''", + "name":"sql_mode", + "deprecated":"f", + "valid_vals":"ALLOW_INVALID_DATES,ANSI_QUOTES,ERROR_FOR_DIVISION_BY_ZERO,HIGH_NOT_PRECEDENCE,IGNORE_SPACE,NO_AUTO_CREATE_USER,NO_AUTO_VALUE_ON_ZERO,NO_BACKSLASH_ESCAPES,NO_DIR_IN_CREATE,NO_ENGINE_SUBSTITUTION,NO_FIELD_OPTIONS,NO_KEY_OPTIONS,NO_TABLE_OPTIONS,NO_UNSIGNED_SUBTRACTION,NO_ZERO_DATE,NO_ZERO_IN_DATE,ONLY_FULL_GROUP_BY,PAD_CHAR_TO_FULL_LENGTH,PIPES_AS_CONCAT,REAL_AS_FLOAT,STRICT_ALL_TABLES,STRICT_TRANS_TABLES", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sql-mode", + "vartype":"set", + "max_value":"NULL", + "scope":"{Global,Session}", + "id":"215", + "unit":"NULL", + "description":"The current server SQL mode which can be set dynamically. Fordetails see Section 5.1.7 Server SQL Modes." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"sql_notes", + "deprecated":"f", + "valid_vals":"1,0", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{NA}", + "id":"216", + "unit":"NULL", + "description":"If set to 1 (the default) warnings of Notelevel increment warning_count and theserver records them. If set to 0 Notewarnings do not incrementwarning_count and the serverdoes not record them. mysqldump includesoutput to set this variable to 0 so that reloading the dumpfile does not produce warnings for events that do not affectthe integrity of the reload operation." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"sql_quote_show_create", + "deprecated":"f", + "valid_vals":"1,0", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{NA}", + "id":"217", + "unit":"NULL", + "description":"If set to 1 (the default) the server quotes identifiers forSHOW CREATE TABLE andSHOW CREATE DATABASEstatements. If set to 0 quoting is disabled. This option isenabled by default so that replication works for identifiersthat require quoting. See Section 13.7.5.12 SHOW CREATE TABLE Syntaxand Section 13.7.5.8 SHOW CREATE DATABASE Syntax." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"sql_safe_updates", + "deprecated":"f", + "valid_vals":"1,0", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{NA}", + "id":"218", + "unit":"NULL", + "description":"If set to 1 MySQL abortsUPDATE orDELETE statements that do notuse a key in the WHERE clause or aLIMIT clause. (SpecificallyUPDATE statements must have aWHERE clause that uses a key or aLIMIT clause or both.DELETE statements must haveboth.) This makes it possible to catchUPDATE orDELETE statements where keysare not used properly and that would probably change or deletea large number of rows. The default value is 0." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"18446744073709551615", + "name":"sql_select_limit", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sql_select_limit", + "vartype":"integer", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"219", + "unit":"NULL", + "description":"The maximum number of rows to return fromSELECT statements. The defaultvalue for a new connection is the maximum number of rows thatthe server permits per table. Typical default values are(232)1 or(264)1. If you have changedthe limit the default value can be restored by assigning avalue of DEFAULT.If a SELECT has aLIMIT clause the LIMITtakes precedence over the value ofsql_select_limit." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"sql_warnings", + "deprecated":"f", + "valid_vals":"1,0", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{NA}", + "id":"220", + "unit":"NULL", + "description":"This variable controls whether single-rowINSERT statements produce aninformation string if warnings occur. The default is 0. Setthe value to 1 to produce an information string." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"ssl_ca", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for ssl-ca", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"221", + "unit":"NULL", + "description":"The path to a file with a list of trusted SSL CAs." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"ssl_capath", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for ssl-capath", + "vartype":"directory name", + "max_value":"NULL", + "scope":"{Global}", + "id":"222", + "unit":"NULL", + "description":"The path to a directory that contains trusted SSL CAcertificates in PEM format." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"50", + "name":"autovacuum_vacuum_threshold", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Minimum number of tuple updates or deletes prior to vacuum.", + "vartype":"integer", + "max_value":"2147483647", + "scope":"{Global}", + "id":"1472", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"256", + "name":"stored_program_cache", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"256", + "dynamic":"t", + "rank":"-1", + "summary":"Options for stored_program_cache", + "vartype":"integer", + "max_value":"524288", + "scope":"{Global}", + "id":"227", + "unit":"NULL", + "description":"Sets a soft upper limit for the number of cached storedroutines per connection. The value of this variable isspecified in terms of the number of stored routines held ineach of the two caches maintained by the MySQL Server forrespectively stored procedures and stored functions.Whenever a stored routine is executed this cache size ischecked before the first or top-level statement in the routineis parsed; if the number of routines of the same type (storedprocedures or stored functions according to which is beingexecuted) exceeds the limit specified by this variable thecorresponding cache is flushed and memory previously allocatedfor cached objects is freed. This allows the cache to beflushed safely even when there are dependencies betweenstored routines." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"TRUE", + "name":"sync_frm", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sync_frm", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"228", + "unit":"NULL", + "description":"If this variable is set to 1 when any nontemporary table iscreated its .frm file is synchronized todisk (using fdatasync()). This is slowerbut safer in case of a crash. The default is 1." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"system_time_zone", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for system_time_zone", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"229", + "unit":"NULL", + "description":"The server system time zone. When the server begins executingit inherits a time zone setting from the machine defaultspossibly modified by the environment of the account used forrunning the server or the startup script. The value is used toset system_time_zone.Typically the time zone is specified by theTZ environment variable. It also can bespecified using the--timezone option of themysqld_safe script.The system_time_zone variablediffers from time_zone.Although they might have the same value the latter variableis used to initialize the time zone for each client thatconnects. See Section 10.6 MySQL Server Time Zone Support." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"400", + "name":"table_definition_cache", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"400", + "dynamic":"t", + "rank":"-1", + "summary":"Options for table_definition_cache", + "vartype":"integer", + "max_value":"524288", + "scope":"{Global}", + "id":"230", + "unit":"NULL", + "description":"The number of table definitions (from.frm files) that can be stored in thedefinition cache. If you use a large number of tables you cancreate a large table definition cache to speed up opening oftables. The table definition cache takes less space and doesnot use file descriptors unlike the normal table cache. Theminimum and default values are both 400." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"50", + "name":"table_lock_wait_timeout", + "deprecated":"t", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for table_lock_wait_timeout", + "vartype":"integer", + "max_value":"1073741824", + "scope":"{Global}", + "id":"231", + "unit":"NULL", + "description":"This variable is unused. It was removed in 5.5.3." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"400", + "name":"table_open_cache", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for table_open_cache", + "vartype":"integer", + "max_value":"524288", + "scope":"{Global}", + "id":"232", + "unit":"NULL", + "description":"The number of open tables for all threads. Increasing thisvalue increases the number of file descriptors thatmysqld requires. You can check whether youneed to increase the table cache by checking theOpened_tables statusvariable. See Section 5.1.6 Server Status Variables. Ifthe value of Opened_tablesis large and you do not useFLUSH TABLESoften (which just forces all tables to be closed andreopened) then you should increase the value of thetable_open_cache variable.For more information about the table cache seeSection 8.4.3.1 How MySQL Opens and Closes Tables." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"table_type", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"233", + "unit":"NULL", + "description":"This variable was removed in MySQL 5.5.3. Usestorage_engine instead." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"thread_cache_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for thread_cache_size", + "vartype":"integer", + "max_value":"16384", + "scope":"{Global}", + "id":"234", + "unit":"NULL", + "description":"How many threads the server should cache for reuse. When aclient disconnects the client's threads are put in the cacheif there are fewer thanthread_cache_size threadsthere. Requests for threads are satisfied by reusing threadstaken from the cache if possible and only when the cache isempty is a new thread created. This variable can be increasedto improve performance if you have a lot of new connections.Normally this does not provide a notable performanceimprovement if you have a good thread implementation. Howeverif your server sees hundreds of connections per second youshould normally setthread_cache_size high enoughso that most new connections use cached threads. By examiningthe difference between theConnections andThreads_created statusvariables you can see how efficient the thread cache is. Fordetails see Section 5.1.6 Server Status Variables." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"10", + "name":"thread_concurrency", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1", + "dynamic":"f", + "rank":"-1", + "summary":"Options for thread_concurrency", + "vartype":"integer", + "max_value":"512", + "scope":"{Global}", + "id":"235", + "unit":"NULL", + "description":"This variable is specific to Solaris 8 and earlier systemsfor which mysqld invokes thethr_setconcurrency() function with thevariable value. This function enables applications to give thethreads system a hint about the desired number of threads thatshould be run at the same time. Current Solaris versionsdocument this as having no effect." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"one-thread-per-connection", + "name":"thread_handling", + "deprecated":"f", + "valid_vals":"no-threads,one-thread-per-connection", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for thread_handling", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"236", + "unit":"NULL", + "description":"The thread-handling model used by the server for connectionthreads. The permissible user-settable values areno-threads (the server uses a single threadto handle one connection) andone-thread-per-connection (the server usesone thread to handle each client connection; this is thedefault). no-threads is useful fordebugging under Linux; see Section 24.5 Debugging and Porting MySQL.If the thread pool plugin is enabled the server sets thethread_handling value todynamically-loaded. SeeSection 8.12.7.1 Thread Pool Components and Installation." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"safe_encoding", + "name":"backslash_quote", + "deprecated":"f", + "valid_vals":"safe_encoding,on,off", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Sets whether ' is allowed in string literals.", + "vartype":"enum", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1473", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"thread_pool_high_priority_connection", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for thread_pool_high_priority_connection", + "vartype":"integer", + "max_value":"1", + "scope":"{GlobalSession}", + "id":"238", + "unit":"NULL", + "description":"This variable affects queuing of new statements prior toexecution. If the value is 0 (false the default) statementqueuing uses both the low-priority and high-priority queues.If the value is 1 (true) queued statements always go to thehigh-priority queue.This variable was added in MySQL 5.5.16. It is available onlyif the thread pool plugin is enabled. SeeSection 8.12.7 The Thread Pool Plugin" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"thread_pool_max_unused_threads", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for thread_pool_max_unused_threads", + "vartype":"integer", + "max_value":"4096", + "scope":"{Global}", + "id":"239", + "unit":"NULL", + "description":"The maximum permitted number of unused threads in the threadpool. This variable makes it possible to limit the amount ofmemory used by sleeping threads.A value of 0 (the default) means no limit on the number ofsleeping threads. A value of Nwhere N is greater than 0 means 1consumer thread and N1reserve threads. In this case if a thread is ready to sleepbut the number of sleeping threads is already at the maximumthe thread exits rather than going to sleep.A sleeping thread is either sleeping as a consumer thread or areserve thread. The thread pool permits one thread to be theconsumer thread when sleeping. If a thread goes to sleep andthere is no existing consumer thread it will sleep as aconsumer thread. When a thread must be woken up a consumerthread is selected if there is one. A reserve thread isselected only when there is no consumer thread to wake up.This variable was added in MySQL 5.5.16. It is available onlyif the thread pool plugin is enabled. SeeSection 8.12.7 The Thread Pool Plugin" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1000", + "name":"thread_pool_prio_kickup_timer", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for thread_pool_prio_kickup_timer", + "vartype":"integer", + "max_value":"4294967294", + "scope":"{GlobalSession}", + "id":"240", + "unit":"NULL", + "description":"This variable affects statements waiting for execution in thelow-priority queue. The value is the number of millisecondsbefore a waiting statement is moved to the high-priorityqueue. The default is 1000 (1 second). The range of values is0 to 2322.This variable was added in MySQL 5.5.16. It is available onlyif the thread pool plugin is enabled. SeeSection 8.12.7 The Thread Pool Plugin" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"16", + "name":"thread_pool_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1", + "dynamic":"f", + "rank":"-1", + "summary":"Options for thread_pool_size", + "vartype":"integer", + "max_value":"64", + "scope":"{Global}", + "id":"241", + "unit":"NULL", + "description":"The number of thread groups in the thread pool. This is themost important parameter controlling thread pool performance.It affects how many statements can execute simultaneously. Thedefault value is 16 with a range from 1 to 64 of permissiblevalues. If a value outside this range is specified the threadpool plugin does not load and the server writes a message tothe error log.This variable was added in MySQL 5.5.16. It is available onlyif the thread pool plugin is enabled. SeeSection 8.12.7 The Thread Pool Plugin" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"6", + "name":"thread_pool_stall_limit", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"4", + "dynamic":"t", + "rank":"-1", + "summary":"Options for thread_pool_stall_limit", + "vartype":"integer", + "max_value":"600", + "scope":"{Global}", + "id":"242", + "unit":"NULL", + "description":"This variable affects executing statements. The value is theamount of time a statement has to finish after starting toexecute before it becomes defined as stalled at which pointthe thread pool permits the thread group to begin executinganother statement. The value is measured in 10 millisecondunits so a value of 6 (the default) means 60ms. The range ofvalues is 4 to 600 (40ms to 6s). Short wait values permitthreads to start more quickly. Short values are also betterfor avoiding deadlock situations. Long wait values are usefulfor workloads that include long-running statements to avoidstarting too many new statements while the current onesexecute.This variable was added in MySQL 5.5.16. It is available onlyif the thread pool plugin is enabled. SeeSection 8.12.7 The Thread Pool Plugin" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"262144", + "name":"thread_stack", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"131072", + "dynamic":"f", + "rank":"-1", + "summary":"Options for thread_stack", + "vartype":"integer", + "max_value":"18446744073709547520", + "scope":"{Global}", + "id":"243", + "unit":"1024", + "description":"The stack size for each thread. Many of the limits detected bythe crash-me test are dependent on thisvalue. See Section 8.13.2 The MySQL Benchmark Suite. The default of192KB (256KB for 64-bit systems) is large enough for normaloperation. If the thread stack size is too small it limitsthe complexity of the SQL statements that the server canhandle the recursion depth of stored procedures and othermemory-consuming actions." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"%H:%i:%s", + "name":"time_format", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"244", + "unit":"NULL", + "description":"This variable is unused." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"time_zone", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for time_zone", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"245", + "unit":"NULL", + "description":"The current time zone. This variable is used to initialize thetime zone for each client that connects. By default theinitial value of this is 'SYSTEM' (whichmeans use the value ofsystem_time_zone).The value can be specified explicitly at server startup withthe --default-time-zone option.See Section 10.6 MySQL Server Time Zone Support." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"timed_mutexes", + "deprecated":"t", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for timed_mutexes", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"246", + "unit":"NULL", + "description":"This variable is deprecated; it has no use. It will be removedin a future MySQL release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"28800", + "name":"wait_timeout", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for wait_timeout", + "vartype":"integer", + "max_value":"31536000", + "scope":"{GlobalSession}", + "id":"257", + "unit":"NULL", + "description":"The number of seconds the server waits for activity on anoninteractive connection before closing it.On thread startup the sessionwait_timeout value isinitialized from the globalwait_timeout value or fromthe globalinteractive_timeout valuedepending on the type of client (as defined by theCLIENT_INTERACTIVE connect option tomysql_real_connect()). Seealso interactive_timeout." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"200", + "name":"bgwriter_delay", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"10", + "dynamic":"t", + "rank":"-1", + "summary":"Background writer sleep time between rounds.", + "vartype":"integer", + "max_value":"10000", + "scope":"{Global}", + "id":"1474", + "unit":"ms", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"DEFAULT", + "name":"timestamp", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for timestamp", + "vartype":"numeric", + "max_value":"NULL", + "scope":"{Session}", + "id":"247", + "unit":"NULL", + "description":"Set the time for this client. This is used to get the originaltimestamp if you use the binary log to restore rows.timestamp_value should be a Unixepoch timestamp (a value like that returned byUNIX_TIMESTAMP() not a valuein 'YYYY-MM-DD hh:mm:ss' format) orDEFAULT.Setting timestamp to aconstant value causes it to retain that value until it ischanged again. Settingtimestamp toDEFAULT causes its value to be the currentdate and time as of the time it is accessed.SET timestamp affects the value returned byNOW() but not bySYSDATE(). This means thattimestamp settings in the binary log have no effect oninvocations of SYSDATE(). Theserver can be started with the--sysdate-is-now option tocause SYSDATE() to be an aliasfor NOW() in which caseSET timestamp affects both functions." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"16777216", + "name":"tmp_table_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1024", + "dynamic":"t", + "rank":"-1", + "summary":"Options for tmp_table_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{GlobalSession}", + "id":"248", + "unit":"NULL", + "description":"The maximum size of internal in-memory temporary tables. Thisvariable does not apply to user-createdMEMORY tables.The actual limit is determined as the minimum oftmp_table_size andmax_heap_table_size. If anin-memory temporary table exceeds the limit MySQLautomatically converts it to an on-diskMyISAM table. Increase the value oftmp_table_size (andmax_heap_table_size ifnecessary) if you do many advanced GROUP BYqueries and you have lots of memory.You can compare the number of internal on-disk temporarytables created to the total number of internal temporarytables created by comparing the values of theCreated_tmp_disk_tables andCreated_tmp_tablesvariables.See also Section 8.4.4 Internal Temporary Table Use in MySQL." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"8192", + "name":"transaction_alloc_block_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1024", + "dynamic":"t", + "rank":"-1", + "summary":"Options for transaction_alloc_block_size", + "vartype":"integer", + "max_value":"18446744073709547520", + "scope":"{GlobalSession}", + "id":"249", + "unit":"1024", + "description":"The amount in bytes by which to increase a per-transactionmemory pool which needs memory. See the description oftransaction_prealloc_size." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"4096", + "name":"transaction_prealloc_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1024", + "dynamic":"t", + "rank":"-1", + "summary":"Options for transaction_prealloc_size", + "vartype":"integer", + "max_value":"18446744073709547520", + "scope":"{GlobalSession}", + "id":"250", + "unit":"1024", + "description":"There is a per-transaction memory pool from which varioustransaction-related allocations take memory. The initial sizeof the pool in bytes istransaction_prealloc_size.For every allocation that cannot be satisfied from the poolbecause it has insufficient memory available the pool isincreased bytransaction_alloc_block_sizebytes. When the transaction ends the pool is truncated totransaction_prealloc_sizebytes.By makingtransaction_prealloc_sizesufficiently large to contain all statements within a singletransaction you can avoid many malloc()calls." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"REPEATABLE-READ", + "name":"tx_isolation", + "deprecated":"f", + "valid_vals":"READ-UNCOMMITTED,READ-COMMITTED,REPEATABLE-READ, SERIALIZABLE ", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for tx_isolation", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"251", + "unit":"NULL", + "description":"The default transaction isolation level. Defaults toREPEATABLE-READ.This variable can be set directly or indirectly using theSET TRANSACTION statement. SeeSection 13.3.6 SET TRANSACTION Syntax. If you settx_isolation directly to anisolation level name that contains a space the name should beenclosed within quotation marks with the space replaced by adash. For example:Any unique prefix of a valid value may be used to set thevalue of this variable.The default transaction isolation level can also be set atstartup using the--transaction-isolation serveroption." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"YES", + "default_val":"1", + "name":"unique_checks", + "deprecated":"f", + "valid_vals":"1,0", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for unique_checks", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"252", + "unit":"NULL", + "description":"If set to 1 (the default) uniqueness checks for secondaryindexes in InnoDB tables are performed. Ifset to 0 storage engines are permitted to assume thatduplicate keys are not present in input data. If you know forcertain that your data does not contain uniqueness violationsyou can set this to 0 to speed up large table imports toInnoDB.Setting this variable to 0 does notrequire storage engines to ignoreduplicate keys. An engine is still permitted to check for themand issue duplicate-key errors if it detects them." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"updatable_views_with_limit", + "deprecated":"f", + "valid_vals":"1,0", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for updatable_views_with_limit", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global,Session}", + "id":"253", + "unit":"NULL", + "description":"This variable controls whether updates to a view can be madewhen the view does not contain all columns of the primary keydefined in the underlying table if the update statementcontains a LIMIT clause. (Such updatesoften are generated by GUI tools.) An update is anUPDATE orDELETE statement. Primary keyhere means a PRIMARY KEY or aUNIQUE index in which no column can containNULL.The variable can have two values:" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"INTERNAL", + "name":"version_comment", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for version_comment", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"254", + "unit":"NULL", + "description":"The CMake configuration program has aCOMPILATION_COMMENT option thatpermits a comment to be specified when building MySQL. Thisvariable contains the value of that comment. SeeSection 2.9.4 MySQL Source-Configuration Options." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"INTERNAL", + "name":"version_compile_machine", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for version_compile_machine", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"255", + "unit":"NULL", + "description":"The type of machine or architecture on which MySQL was built." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"INTERNAL", + "name":"version_compile_os", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for version_compile_os", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"256", + "unit":"NULL", + "description":"The type of operating system on which MySQL was built." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1048576", + "name":"audit_log_buffer_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"4096", + "dynamic":"f", + "rank":"-1", + "summary":"Options for audit_log_buffer_size", + "vartype":"integer", + "max_value":"18446744073709547520", + "scope":"{Global}", + "id":"259", + "unit":"NULL", + "description":"When the audit log plugin writes events to the logasynchronously it uses a buffer to store event contentsprior to writing them. This variable controls the size ofthat buffer in bytes. The server adjusts the value to amultiple of 4096. The plugin uses a single buffer which itallocates when it initializes and removes when itterminates. The plugin allocates this buffer only if loggingis asynchronous.This variable was added in MySQL 5.5.28." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"audit.log", + "name":"audit_log_file", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for audit_log_file", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"260", + "unit":"NULL", + "description":"The name of the file to which the audit log plugin writesevents. The default value is audit.log.If the file name is a relative path the server interpretsit relative to the data directory. For security reasons theaudit log file should be written to a directory accessibleonly to the MySQL server and users with a legitimate reasonto view the log.This variable was added in MySQL 5.5.28." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"audit_log_flush", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for audit_log_flush", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"261", + "unit":"NULL", + "description":"When this variable is set to enabled (1 orON) the audit log plugin closes andreopens its log file to flush it. (The value remainsOFF so that you need not disable itexplicitly before enabling it again to perform anotherflush.) Enabling this variable has no effect unlessaudit_log_rotate_on_size is0This variable was added in MySQL 5.5.28." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OLD", + "name":"audit_log_format", + "deprecated":"f", + "valid_vals":"OLD,NEW", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for audit_log_format", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"262", + "unit":"NULL", + "description":"The audit log file format. Permitted values areOLD and NEW (defaultOLD). For details about each format seeSection 6.3.11.3 The Audit Log File.If you change the value ofaudit_log_format use thisprocedure to avoid writing log entries in one format to anexisting log file that contains entries in a differentformat:This variable was added in MySQL 5.5.34." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ALL", + "name":"audit_log_policy", + "deprecated":"f", + "valid_vals":"ALL,LOGINS,QUERIES,NONE", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for audit_log_policy", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"263", + "unit":"NULL", + "description":"The policy controlling the information written by the auditlog plugin to its log file. The following table shows thepermitted values.This variable was added in MySQL 5.5.28." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"audit_log_rotate_on_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for audit_log_rotate_on_size", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"264", + "unit":"NULL", + "description":"If theaudit_log_rotate_on_sizevalue is greater than 0 the audit log plugin closes andreopens its log file if a write to the file causes its sizeto exceed this value. The original file is renamed to have atimestamp extension.If theaudit_log_rotate_on_sizevalue is 0 the plugin does not close and reopen its logbased on size. Instead useaudit_log_flush to closeand reopen the log on demand. In this case rename the fileexternally to the server before flushing it.For more information about audit log file rotation andtimestamp interpretation seeSection 6.3.11.4 Audit Log Plugin Logging Control.If you set this variable to a value that is not a multipleof 4096 it is truncated to the nearest multiple. (Thussetting it to a value less than 4096 has the effect ofsetting it to 0 and no rotation occurs.)This variable was added in MySQL 5.5.28." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ASYNCHRONOUS", + "name":"audit_log_strategy", + "deprecated":"f", + "valid_vals":"ASYNCHRONOUS,PERFORMANCE,SEMISYNCHRONOUS,SYNCHRONOUS", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for audit_log_strategy", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"265", + "unit":"NULL", + "description":"The logging method used by the audit log plugin. Thefollowing table describes the permitted values.This variable was added in MySQL 5.5.28." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"performance_schema", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"266", + "unit":"NULL", + "description":"The value of this variable is ON orOFF to indicate whether the PerformanceSchema is enabled. By default the value isOFF. At server startup you can specifythis variable with no value or a value of 1 to enable it orwith a value of 0 to disable it." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"10000", + "name":"performance_schema_events_waits_history_long_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_events_waits_history_long_size", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"267", + "unit":"NULL", + "description":"The number of rows in theevents_waits_history_long table." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"10", + "name":"performance_schema_events_waits_history_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_events_waits_history_size", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"268", + "unit":"NULL", + "description":"The number of rows per thread in theevents_waits_history table." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"80", + "name":"performance_schema_max_cond_classes", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_cond_classes", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"269", + "unit":"NULL", + "description":"The maximum number of condition instruments." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1000", + "name":"performance_schema_max_cond_instances", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_cond_instances", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"270", + "unit":"NULL", + "description":"The maximum number of instrumented condition objects." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"50", + "name":"performance_schema_max_file_classes", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_file_classes", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"271", + "unit":"NULL", + "description":"The maximum number of file instruments." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"latin1_swedish_ci", + "name":"collation_server", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for collation-server", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"602", + "unit":"NULL", + "description":"The server's default collation." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"32768", + "name":"performance_schema_max_file_handles", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_file_handles", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"272", + "unit":"NULL", + "description":"The maximum number of opened file objects.The value ofperformance_schema_max_file_handlesshould be greater than the value ofopen_files_limit:open_files_limit affects themaximum number of open file handles the server can support andperformance_schema_max_file_handlesaffects how many of these file handles can be instrumented." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"10000", + "name":"performance_schema_max_file_instances", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_file_instances", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"273", + "unit":"NULL", + "description":"The maximum number of instrumented file objects." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"200", + "name":"performance_schema_max_mutex_classes", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_mutex_classes", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"274", + "unit":"NULL", + "description":"The maximum number of mutex instruments." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1000", + "name":"performance_schema_max_mutex_instances", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_mutex_instances", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"275", + "unit":"NULL", + "description":"The maximum number of instrumented mutex objects." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"20", + "name":"performance_schema_max_rwlock_classes", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_rwlock_classes", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"276", + "unit":"NULL", + "description":"The maximum number of rwlock instruments." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1000", + "name":"performance_schema_max_rwlock_instances", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_rwlock_instances", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"277", + "unit":"NULL", + "description":"The maximum number of instrumented rwlock objects." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"100000", + "name":"performance_schema_max_table_handles", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_table_handles", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"278", + "unit":"NULL", + "description":"The maximum number of opened table objects." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"50000", + "name":"performance_schema_max_table_instances", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_table_instances", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"279", + "unit":"NULL", + "description":"The maximum number of instrumented table objects." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"50", + "name":"performance_schema_max_thread_classes", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_thread_classes", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"280", + "unit":"NULL", + "description":"The maximum number of thread instruments." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1000", + "name":"performance_schema_max_thread_instances", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_thread_instances", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"281", + "unit":"NULL", + "description":"The maximum number of instrumented thread objects. The valuecontrols the size of the threadstable. If this maximum is exceeded such that a thread cannotbe instrumented the Performance Schema increments thePerformance_schema_thread_instances_loststatus variable.The max_connections andmax_delayed_threads systemvariables affect how many threads are run in the server.performance_schema_max_thread_instancesaffects how many of these running threads can be instrumented.If you increasemax_connections ormax_delayed_threads youshould consider increasingperformance_schema_max_thread_instancesso thatperformance_schema_max_thread_instancesis greater than the sum ofmax_connections andmax_delayed_threads." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"ignore_builtin_innodb", + "deprecated":"t", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for ignore-builtin-innodb", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"282", + "unit":"NULL", + "description":"See the description of--ignore-builtin-innodb underInnoDB Command Optionsearlier in this section." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"ON", + "name":"innodb_adaptive_flushing", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_adaptive_flushing", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"283", + "unit":"NULL", + "description":"Specifies whether to dynamically adjust the rate of flushingdirty pages in theInnoDBbuffer pool based onthe workload. Adjusting the flush rate dynamically is intendedto avoid bursts of I/O activity. This setting is enabled bydefault. SeeSection 14.7.2.2 Configuring the Rate of InnoDB Buffer Pool Flushing formore information. For general I/O tuning advice seeSection 8.5.7 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"ON", + "name":"innodb_adaptive_hash_index", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_adaptive_hash_index", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"284", + "unit":"NULL", + "description":"Whether the InnoDBadaptive hashindex is enabled or disabled. It may be desirabledepending on your workload to dynamically enable or disableadaptive hashindexing to improve query performance. Because theadaptive hash index may not be useful for all workloadsconduct benchmarks with it both enabled and disabled usingrealistic workloads. SeeSection 14.5.5.5 Adaptive Hash Indexes for details.This variable is enabled by default. As of MySQL 5.5 You canmodify this parameter using the SET GLOBALstatement without restarting the server. Changing the settingrequires the SUPER privilege. You can alsouse --skip-innodb_adaptive_hash_index atserver startup to disable it.Disabling the adaptive hash index empties the hash tableimmediately. Normal operations can continue while the hashtable is emptied and executing queries that were using thehash table access the index B-trees directly instead. When theadaptive hash index is re-enabled the hash table is populatedagain during normal operation." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"Antelope", + "name":"innodb_file_format_max", + "deprecated":"f", + "valid_vals":"Antelope,Barracuda", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_file_format_max", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"301", + "unit":"NULL", + "description":"At server startup InnoDB sets the value ofthis variable to the fileformat tag in thesystemtablespace (for example Antelope orBarracuda). If the server creates or opensa table with a higher file format it sets thevalue ofinnodb_file_format_max tothat format.This variable was added in MySQL 5.5.5." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"8388608", + "name":"innodb_additional_mem_pool_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"2097152", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_additional_mem_pool_size", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{Global}", + "id":"285", + "unit":"NULL", + "description":"The size in bytes of a memory pool InnoDBuses to store datadictionary information and other internal datastructures. The more tables you have in your application themore memory you need to allocate here. IfInnoDB runs out of memory in this pool itstarts to allocate memory from the operating system and writeswarning messages to the MySQL error log. The default value is8MB.This variable relates to the InnoDBinternal memory allocator which is unused ifinnodb_use_sys_malloc isenabled." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"8", + "name":"innodb_autoextend_increment", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_autoextend_increment", + "vartype":"integer", + "max_value":"1000", + "scope":"{Global}", + "id":"286", + "unit":"NULL", + "description":"The increment size (in MB) for extending the size of anauto-extending systemtablespace file when it becomes full. The default valueis 8. This variable does not affect the per-table tablespacefiles that are created if you useinnodb_file_per_table=1.Those files are auto-extending regardless of the value ofinnodb_autoextend_increment.The initial extensions are by small amounts after whichextensions occur in increments of 4MB." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1", + "name":"innodb_autoinc_lock_mode", + "deprecated":"f", + "valid_vals":"0,1,2", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_autoinc_lock_mode", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"287", + "unit":"NULL", + "description":"The lock mode to use forgeneratingauto-incrementvalues. The permissible values are 01 or 2 fortraditional consecutive orinterleaved lock mode respectively.Section 14.9.5 AUTO_INCREMENT Handling in InnoDB describesthe characteristics of these modes.This variable has a default of 1 (consecutivelock mode)." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1", + "name":"innodb_buffer_pool_instances", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_buffer_pool_instances", + "vartype":"integer", + "max_value":"64", + "scope":"{Global}", + "id":"288", + "unit":"NULL", + "description":"The number of regions that theInnoDB buffer pool is dividedinto. For systems with buffer pools in the multi-gigabyterange dividing the buffer pool into separate instances canimprove concurrency by reducing contention as differentthreads read and write to cached pages. Each page that isstored in or read from the buffer pool is assigned to one ofthe buffer pool instances randomly using a hashing function.Each buffer pool manages its own free lists flush listsLRUs and all other data structures connected to a bufferpool and is protected by its own buffer pool mutex.This option takes effect only when you set theinnodb_buffer_pool_size to asize of 1GB or more. The total size you specify is dividedamong all the buffer pools. For best efficiency specify acombination ofinnodb_buffer_pool_instancesand innodb_buffer_pool_sizeso that each buffer pool instance is at least 1GB." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"134217728", + "name":"innodb_buffer_pool_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"5242880", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_buffer_pool_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"289", + "unit":"NULL", + "description":"The size in bytes of thebuffer pool thememory area where InnoDB caches table andindex data. The default value is 128MB. The maximum valuedepends on the CPU architecture; the maximum is 4294967295(232-1) on 32-bit systems and18446744073709551615 (264-1) on64-bit systems. On 32-bit systems the CPU architecture andoperating system may impose a lower practical maximum sizethan the stated maximum. When the size of the buffer pool isgreater than 1GB settinginnodb_buffer_pool_instancesto a value greater than 1 can improve the scalability on abusy server.A larger buffer pool requires less disk I/O to access the sametable data more than once. On a dedicated database server youmight set the buffer pool size to 80% of the machine'sphysical memory size. Be aware of the following potentialissues when configuring buffer pool size and be prepared toscale back the size of the buffer pool if necessary." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"inserts", + "name":"innodb_change_buffering", + "deprecated":"f", + "valid_vals":"inserts,none,deletes,purges,changes,all", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_change_buffering", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"290", + "unit":"NULL", + "description":"Whether InnoDB performschange bufferingan optimization that delays write operations to secondaryindexes so that the I/O operations can be performedsequentially. The permitted values are described in thefollowing table. For more information seeSection 14.7.4 Configuring InnoDB Change Buffering. Forgeneral I/O tuning advice seeSection 8.5.7 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"innodb_change_buffering_debug", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_change_buffering_debug", + "vartype":"integer", + "max_value":"2", + "scope":"{Global}", + "id":"291", + "unit":"NULL", + "description":"Sets a debug flag for InnoDB changebuffering. A value of 1 forces all changes to the changebuffer. A value of 2 causes a crash at merge. A default valueof 0 indicates that the change buffering debug flag is notset. This option is only available when debugging support iscompiled in using the WITH_DEBUGCMake option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"ON", + "name":"innodb_checksums", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_checksums", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"292", + "unit":"NULL", + "description":"InnoDB can use checksum validation on allpages read from the disk to ensure extra fault toleranceagainst broken hardware or data files. This validation isenabled by default. However under some rare circumstances(such as when running benchmarks) this extra safety feature isunneeded and can be disabled with--skip-innodb-checksums." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"innodb_commit_concurrency", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_commit_concurrency", + "vartype":"integer", + "max_value":"1000", + "scope":"{Global}", + "id":"293", + "unit":"NULL", + "description":"The number of threads thatcan commit at the sametime. A value of 0 (the default) permits any number oftransactions to commitsimultaneously.The value ofinnodb_commit_concurrencycannot be changed at runtime from zero to nonzero or viceversa. The value can be changed from one nonzero value toanother." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1", + "name":"innodb_mirrored_log_groups", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"integer", + "max_value":"NULL", + "scope":"{NA}", + "id":"318", + "unit":"NULL", + "description":"Has no effect." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"500", + "name":"innodb_concurrency_tickets", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_concurrency_tickets", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{Global}", + "id":"294", + "unit":"NULL", + "description":"Determines the number ofthreads that can enterInnoDB concurrently. A thread is placed ina queue when it tries to enter InnoDB ifthe number of threads has already reached the concurrencylimit. When a thread is permitted to enterInnoDB it is given a number of freetickets equal to the value ofinnodb_concurrency_ticketsand the thread can enter and leave InnoDBfreely until it has used up its tickets. After that point thethread again becomes subject to the concurrency check (andpossible queuing) the next time it tries to enterInnoDB. The default value is 500.With a small innodb_concurrency_ticketsvalue small transactions that only need to process a few rowscompete fairly with larger transactions that process manyrows. The disadvantage of a smallinnodb_concurrency_tickets value is thatlarge transactions must loop through the queue many timesbefore they can complete which extends the length of timerequired to complete their task.With a large innodb_concurrency_ticketsvalue large transactions spend less time waiting for aposition at the end of the queue (controlled byinnodb_thread_concurrency)and more time retrieving rows. Large transactions also requirefewer trips through the queue to complete their task. Thedisadvantage of a largeinnodb_concurrency_tickets value is thattoo many large transactions running at the same time canstarve smaller transactions by making them wait a longer timebefore executing.With a non-zeroinnodb_thread_concurrencyvalue you may need to adjust theinnodb_concurrency_tickets value up or downto find the optimal balance between larger and smallertransactions. The SHOW ENGINE INNODB STATUSreport shows the number of tickets remaining for an executingtransaction in its current pass through the queue. This datamay also be obtained from theTRX_CONCURRENCY_TICKETS column of theINFORMATION_SCHEMA.INNODB_TRXtable.For more information seeSection 14.7.5 Configuring Thread Concurrency for InnoDB." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ibdata1:10M:autoextend", + "name":"innodb_data_file_path", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_data_file_path", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"295", + "unit":"NULL", + "description":"The paths to individual InnoDBdata files and theirsizes. The full directory path to each data file is formed byconcatenatinginnodb_data_home_dir to eachpath specified here. The file sizes are specified KB MB or GB(1024MB) by appending KM or G to the sizevalue. If specifying data file size in kilobytes (KB) do soin multiples of 1024. Otherwise KB values are rounded off tonearest megabyte (MB) boundary. The sum of the sizes of thefiles must be at least slightly larger than 10MB. If you donot specifyinnodb_data_file_path thedefault behavior is to create a single auto-extending datafile slightly larger than 10MB namedibdata1. The size limit of individualfiles is determined by your operating system. You can set thefile size to more than 4GB on those operating systems thatsupport big files. You can alsouse raw disk partitions asdata files. For detailed information on configuringInnoDBtablespace files seeSection 14.7 InnoDB Configuration." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"innodb_data_home_dir", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_data_home_dir", + "vartype":"directory name", + "max_value":"NULL", + "scope":"{Global}", + "id":"296", + "unit":"NULL", + "description":"The common part of the directory path for allInnoDB datafiles in thesystemtablespace. This setting does not affect the locationof file-per-tabletablespaces wheninnodb_file_per_table isenabled. The default value is the MySQLdata directory. If you specify the valueas an empty string you can use absolute file paths ininnodb_data_file_path." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"ON", + "name":"innodb_doublewrite", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_doublewrite", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"297", + "unit":"NULL", + "description":"If this variable is enabled (the default)InnoDB stores all data twice first to thedoublewritebuffer and then to the actualdata files. Thisvariable can be turned off with--skip-innodb_doublewritefor benchmarks or cases when top performance is needed ratherthan concern for data integrity or possible failures." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1", + "name":"innodb_fast_shutdown", + "deprecated":"f", + "valid_vals":"0,1,2", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_fast_shutdown", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"298", + "unit":"NULL", + "description":"The InnoDBshutdown mode. If thevalue is 0 InnoDB does aslow shutdown afull purge and a changebuffer merge before shutting down. If the value is 1 (thedefault) InnoDB skips these operations atshutdown a process known as afast shutdown. Ifthe value is 2 InnoDB flushes its logs andshuts down cold as if MySQL had crashed; no committedtransactions are lost but thecrash recoveryoperation makes the next startup take longer.The slow shutdown can take minutes or even hours in extremecases where substantial amounts of data are still buffered.Use the slow shutdown technique before upgrading ordowngrading between MySQL major releases so that all datafiles are fully prepared in case the upgrade process updatesthe file format.Use innodb_fast_shutdown=2 in emergency ortroubleshooting situations to get the absolute fastestshutdown if data is at risk of corruption." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"Barracuda", + "name":"innodb_file_format", + "deprecated":"f", + "valid_vals":"Antelope,Barracuda", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_file_format", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"299", + "unit":"NULL", + "description":"The file format to usefor new InnoDB tables. CurrentlyAntelope and Barracudaare supported. This applies only for tables that have theirown tablespace so forit to have an effectinnodb_file_per_table must beenabled. The Barracudafile format is required for certain InnoDBfeatures such as tablecompression.Be aware that ALTER TABLEoperations that recreate InnoDB tables(ALTER OFFLINE) will use the currentinnodb_file_format setting (the conditionsoutlined above still apply)." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"Antelope", + "name":"innodb_file_format_check", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_file_format_check", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"300", + "unit":"NULL", + "description":"As of MySQL 5.5.5 this variable can be set to 1 or 0 atserver startup to enable or disable whetherInnoDB checks thefile format tag in thesystemtablespace (for example Antelope orBarracuda). If the tag is checked and ishigher than that supported by the current version ofInnoDB an error occurs andInnoDB does not start. If the tag is nothigher InnoDB sets the value ofinnodb_file_format_max to thefile format tag.Before MySQL 5.5.5 this variable can be set to 1 or 0 atserver startup to enable or disable whetherInnoDB checks the file format tag in theshared tablespace. If the tag is checked and is higher thanthat supported by the current version ofInnoDB an error occurs andInnoDB does not start. If the tag is nothigher InnoDB sets the value ofinnodb_file_format_check tothe file format tag which is the value seen at runtime." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"ON", + "name":"innodb_file_per_table", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_file_per_table", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"302", + "unit":"NULL", + "description":"When innodb_file_per_table is disabledInnoDB stores the data for all tables andindexes in the ibdatafiles that make up thesystemtablespace. This setting reduces the performanceoverhead of filesystem operations for operations such asDROP TABLE orTRUNCATE TABLE. It is mostappropriate for a server environment where entire storagedevices are devoted to MySQL data. Because the systemtablespace never shrinks and is shared across all databasesin an instance avoidloading huge amounts of temporary data on a space-constrainedsystem when innodb_file_per_table=OFF. Setup a separate instance in such cases so that you can drop theentire instance to reclaim the space.When innodb_file_per_table is enabledInnoDB stores data and indexes for eachnewly created table in a separate.ibdfile rather than in the system tablespace. The storagefor these InnoDB tables is reclaimed whenthe tables are dropped or truncated. This setting enablesseveral other InnoDB features such astable compression. SeeSection 14.8.4 InnoDB File-Per-Table Tablespaces for detailsabout such features as well as advantages and disadvantages ofusing file-per-table tablespaces.Be aware that enablinginnodb_file_per_table alsomeans that an ALTER TABLEoperation will move InnoDB table from thesystem tablespace to an individual .ibdfile in cases where ALTER TABLErecreates the table (ALTER OFFLINE).In MySQL 5.5 and higher the configuration parameterinnodb_file_per_table isdynamic and can be set ON orOFF using SET GLOBAL.Previously the only way to set this parameter was in theMySQL configurationfile (my.cnf ormy.ini) and changing it requiredshutting down and restarting the server.Dynamically changing the value of this parameter requires theSUPER privilege and immediately affects theoperation of all connections." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1", + "name":"innodb_flush_log_at_trx_commit", + "deprecated":"f", + "valid_vals":"0,1,2", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_flush_log_at_trx_commit", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"303", + "unit":"NULL", + "description":"Controls the balance between strictACID compliance forcommit operations andhigher performance that is possible when commit-related I/Ooperations are rearranged and done in batches. You can achievebetter performance by changing the default value but then youcan lose up to a second of transactions in a crash.For the greatest possible durability and consistency in areplication setup using InnoDB withtransactions useinnodb_flush_log_at_trx_commit=1 andsync_binlog=1 in your master servermy.cnf file." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULLfsyncO_DSYNCO_DIRECT}", + "dangerous":"PARTIALLY", + "default_val":"NULL", + "name":"innodb_flush_method", + "deprecated":"f", + "valid_vals":"NULL,fsync,O_DSYNC,O_DIRECT,O_DIRECT_NO_FSYNC,littlesync,nosync", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_flush_method", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"304", + "unit":"NULL", + "description":"Defines the method used toflush data to theInnoDB datafiles and logfiles which can affect I/O throughput.If innodb_flush_method=NULL on a Unix-likesystem the fsync option is used bydefault. If innodb_flush_method=NULL onWindows the async_unbuffered option isused by default.The innodb_flush_method options forUnix-like systems include:The innodb_flush_method options for Windowssystems include:How each settings affects performance depends on hardwareconfiguration and workload. Benchmark your particularconfiguration to decide which setting to use or whether tokeep the default setting. Examine theInnodb_data_fsyncs statusvariable to see the overall number offsync() calls for each setting. The mix ofread and write operations in your workload can affect how asetting performs. For example on a system with a hardwareRAID controller and battery-backed write cacheO_DIRECT can help to avoid double bufferingbetween the InnoDB buffer pool and theoperating system's file system cache. On some systems whereInnoDB data and log files are located on aSAN the default value or O_DSYNC might befaster for a read-heavy workload with mostlySELECT statements. Always test thisparameter with hardware and workload that reflect yourproduction environment. For general I/O tuning advice seeSection 8.5.7 Optimizing InnoDB Disk I/O.Prior to MySQL 5.1.24 the defaultinnodb_flush_method option was namedfdatasync. Whenfdatasync was specified InnoDB used thefsync() system call to flush both the dataand log files. To avoid confusing thefdatasync option name with thefdatasync() system call the option namewas changed to fsync in MySQL 5.1.24." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_force_load_corrupted", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_force_load_corrupted", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"305", + "unit":"NULL", + "description":"Lets InnoDB load tables at startup that are marked ascorrupted. Use only during troubleshooting to recover datathat is otherwise inaccessible. When troubleshooting iscomplete turn this setting back off and restart the server." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"innodb_force_recovery", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_force_recovery", + "vartype":"integer", + "max_value":"6", + "scope":"{Global}", + "id":"306", + "unit":"NULL", + "description":"The crash recoverymode typically only changed in serious troubleshootingsituations. Possible values are from 0 to 6. For the meaningsof these values and important information aboutinnodb_force_recovery seeSection 14.21.2 Forcing InnoDB Recovery." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"200", + "name":"innodb_io_capacity", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"100", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_io_capacity", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"307", + "unit":"NULL", + "description":"The innodb_io_capacityparameter sets an upper limit on the I/O activity performed bythe InnoDB background tasks such asflushing pages from thebuffer pool andmerging data from thechange buffer. Thedefault value is 200. For busy systems capable of higher I/Orates you can set a higher value at server startup to helpthe server handle the background maintenance work associatedwith a high rate of row changes. For systems with individual5400 RPM or 7200 RPM drives you might lower the value to theformer default of 100.The innodb_io_capacity limitis a total limit for all buffer pool instances. When dirtypages are flushed theinnodb_io_capacity limit isdivided equally among buffer pool instances.This parameter should be set to approximately the number ofI/O operations that the system can perform per second.Ideally keep this setting as low as practical but not so lowthat these background activities fall behind. If the value istoo high data is removed from the buffer pool and insertbuffer too quickly to provide significant benefit from thecaching.The value represents an estimated proportion of the I/Ooperations per second (IOPS) available to older-generationdisk drives that could perform about 100 IOPS. The currentdefault of 200 reflects that modern storage devices arecapable of much higher I/O rates.In general you can increase the value as a function of thenumber of drives used for InnoDBI/O particularly fast drives capable of high numbers of IOPS.For example systems that use multiple disks or solid-statedisks for InnoDB are likely tobenefit from the ability to control this parameter.Although you can specify a very high number in practice suchlarge values have little if any benefit; for example a valueof one million would be considered very high.You can set the innodb_io_capacity value toany number 100 or greater and the default value is200. You can set the value of thisparameter in the MySQL option file (my.cnfor my.ini) or change it dynamically withthe SET GLOBAL command which requires theSUPER privilege.See Section 14.7.7 Configuring the InnoDB Master Thread I/O Rate formore guidelines about this option. For general informationabout InnoDB I/O performance seeSection 8.5.7 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_large_prefix", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_large_prefix", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"308", + "unit":"NULL", + "description":"Enable this option to allow index key prefixes longer than 767bytes (up to 3072 bytes) for InnoDB tablesthat use theDYNAMICandCOMPRESSEDrow formats. (Creating such tables also requires the optionvaluesinnodb_file_format=barracudaandinnodb_file_per_table=true.)See Section 14.9.7 Limits on InnoDB Tables for the relevantmaximums associated with index key prefixes under varioussettings.For tables using theREDUNDANTandCOMPACTrow formats this option does not affect the allowed keyprefix length. It does introduce a new error possibility. Whenthis setting is enabled attempting to create an index prefixwith a key length greater than 3072 for aREDUNDANT or COMPACTtable causes anER_INDEX_COLUMN_TOO_LONGerror." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"innodb_limit_optimistic_insert_debug", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_limit_optimistic_insert_debug", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{Global}", + "id":"309", + "unit":"NULL", + "description":"Limits the number of records perB-tree page. A defaultvalue of 0 means that no limit is imposed. This option is onlyavailable if debugging support is compiled in using theWITH_DEBUGCMake option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"50", + "name":"innodb_lock_wait_timeout", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_lock_wait_timeout", + "vartype":"integer", + "max_value":"1073741824", + "scope":"{GlobalSession}", + "id":"310", + "unit":"NULL", + "description":"The length of time in seconds an InnoDBtransaction waits fora row lock before givingup. The default value is 50 seconds. A transaction that triesto access a row that is locked by anotherInnoDB transaction waits at most this manyseconds for write access to the row before issuing thefollowing error:When a lock wait timeout occurs the current statement isrolled back (not theentire transaction). To have the entire transaction roll backstart the server with the--innodb_rollback_on_timeoutoption. See also Section 14.21.4 InnoDB Error Handling.You might decrease this value for highly interactiveapplications or OLTP systemsto display user feedback quickly or put the update into aqueue for processing later. You might increase this value forlong-running back-end operations such as a transform step ina data warehouse that waits for other large insert or updateoperations to finish.innodb_lock_wait_timeout applies toInnoDB row locks only. A MySQLtable lock does nothappen inside InnoDB and this timeout doesnot apply to waits for table locks.The lock wait timeout value does not apply todeadlocks becauseInnoDB detects them immediately and rollsback one of the deadlocked transactions.As of MySQL 5.5innodb_lock_wait_timeout canbe set at runtime with the SET GLOBAL orSET SESSION statement. Changing theGLOBAL setting requires theSUPER privilege and affects the operationof all clients that subsequently connect. Any client canchange the SESSION setting forinnodb_lock_wait_timeoutwhich affects only that client." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_locks_unsafe_for_binlog", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_locks_unsafe_for_binlog", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"311", + "unit":"NULL", + "description":"This variable affects how InnoDB uses gaplocking for searches and index scans. NormallyInnoDB uses an algorithm callednext-key locking thatcombines index-row locking with gap locking.InnoDB performs row-level locking in such away that when it searches or scans a table index it setsshared or exclusive locks on the index records it encounters.Thus the row-level locks are actually index-record locks. Inaddition a next-key lock on an index record also affects thegap before that index record. That is anext-key lock is an index-record lock plus a gap lock on thegap preceding the index record. If one session has a shared orexclusive lock on record R in an indexanother session cannot insert a new index record in the gapimmediately before R in the index order.See Section 14.6.2 InnoDB Record Gap and Next-Key Locks.By default the value ofinnodb_locks_unsafe_for_binlog is 0(disabled) which means that gap locking is enabled:InnoDB uses next-key locks for searches andindex scans. To enable the variable set it to 1. This causesgap locking to be disabled: InnoDB usesonly index-record locks for searches and index scans.Enabling innodb_locks_unsafe_for_binlogdoes not disable the use of gap locking for foreign-keyconstraint checking or duplicate-key checking.The effect of enablinginnodb_locks_unsafe_for_binlog is similarto but not identical to setting the transaction isolationlevel to READ COMMITTED:READ COMMITTED thereforeoffers finer and more flexible control thaninnodb_locks_unsafe_for_binlog.For additional details about the effect of isolation level ongap locking see Section 13.3.6 SET TRANSACTION Syntax.Enabling innodb_locks_unsafe_for_binlog maycause phantom problems because other sessions can insert newrows into the gaps when gap locking is disabled. Suppose thatthere is an index on the id column of thechild table and that you want to read andlock all rows from the table having an identifier value largerthan 100 with the intention of updating some column in theselected rows later:The query scans the index starting from the first record whereid is greater than 100. If the locks set onthe index records in that range do not lock out inserts madein the gaps another session can insert a new row into thetable. Consequently if you were to execute the sameSELECT again within the sametransaction you would see a new row in the result setreturned by the query. This also means that if new items areadded to the database InnoDB does notguarantee serializability. Therefore ifinnodb_locks_unsafe_for_binlog is enabledInnoDB guarantees at most an isolationlevel of READ COMMITTED.(Conflict serializability is still guaranteed.) For additionalinformation about phantoms seeSection 14.6.3 Avoiding the Phantom Problem Using Next-Key Locking.Enabling innodb_locks_unsafe_for_binlog hasadditional effects:Consider the following example beginning with this table:In this case table has no indexes so searches and indexscans use the hidden clustered index for record locking (seeSection 14.5.5.2 Clustered and Secondary Indexes).Suppose that one client performs anUPDATE using these statements:Suppose also that a second client performs anUPDATE by executing thesestatements following those of the first client:As InnoDB executes eachUPDATE it first acquires anexclusive lock for each row and then determines whether tomodify it. If InnoDB does notmodify the row andinnodb_locks_unsafe_for_binlog is enabledit releases the lock. OtherwiseInnoDB retains the lock until theend of the transaction. This affects transaction processing asfollows.If innodb_locks_unsafe_for_binlog isdisabled the first UPDATEacquires x-locks and does not release any of them:The second UPDATE blocks assoon as it tries to acquire any locks (because first updatehas retained locks on all rows) and does not proceed untilthe first UPDATE commits orrolls back:If innodb_locks_unsafe_for_binlog isenabled the first UPDATEacquires x-locks and releases those for rows that it does notmodify:For the second UPDATEInnoDB does asemi-consistent read returning the latestcommitted version of each row to MySQL so that MySQL candetermine whether the row matches the WHEREcondition of the UPDATE:" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"8388608", + "name":"innodb_log_buffer_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"262144", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_log_buffer_size", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{Global}", + "id":"312", + "unit":"NULL", + "description":"The size in bytes of the buffer that InnoDBuses to write to the logfiles on disk. The default value is 8MB. A largelog buffer enableslarge transactions torun without a need to write the log to disk before thetransactions commit. Thusif you have transactions that update insert or delete manyrows making the log buffer larger saves disk I/O. For generalI/O tuning advice seeSection 8.5.7 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"5242880", + "name":"innodb_log_file_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1048576", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_log_file_size", + "vartype":"integer", + "max_value":"4GB / innodb_log_files_in_group", + "scope":"{Global}", + "id":"313", + "unit":"NULL", + "description":"The size in bytes of each logfile in a loggroup. The combined size of log files(innodb_log_file_size *innodb_log_files_in_group)cannot exceed a maximum value that is slightly less than 4GB.A pair of 2047 MB log files for example would allow you toapproach the range limit but not exceed it. The default valueis 5MB. Sensible values range from 1MB to1/N-th of the size of the bufferpool where N is the number of logfiles in the group. The larger the value the less checkpointflush activity is needed in the buffer pool saving disk I/O.Larger log files also makecrash recoveryslower although improvements to recovery performance in MySQL5.5 and higher make the log file size less of a consideration.For general I/O tuning advice seeSection 8.5.7 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"2", + "name":"innodb_log_files_in_group", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"2", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_log_files_in_group", + "vartype":"integer", + "max_value":"100", + "scope":"{Global}", + "id":"314", + "unit":"NULL", + "description":"The number of log filesin the log group.InnoDB writes to the files in a circularfashion. The default (and recommended) value is 2. Thelocation of these files is specified byinnodb_log_group_home_dir." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"innodb_log_group_home_dir", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_log_group_home_dir", + "vartype":"directory name", + "max_value":"NULL", + "scope":"{Global}", + "id":"315", + "unit":"NULL", + "description":"The directory path to the InnoDBredo log files whosenumber is specified byinnodb_log_files_in_group. Ifyou do not specify any InnoDB logvariables the default is to create two files namedib_logfile0 andib_logfile1 in the MySQL data directory.Their size is given by the size of theinnodb_log_file_size systemvariable." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"75", + "name":"innodb_max_dirty_pages_pct", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_max_dirty_pages_pct", + "vartype":"numeric", + "max_value":"99", + "scope":"{Global}", + "id":"316", + "unit":"NULL", + "description":"InnoDB tries toflush data from thebuffer pool so thatthe percentage of dirtypages does not exceed this value. Specify an integer inthe range from 0 to 99. The default value is 75.For additional information about this variable seeSection 14.7.2.2 Configuring the Rate of InnoDB Buffer Pool Flushing. Forgeneral I/O tuning advice seeSection 8.5.7 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"innodb_max_purge_lag", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_max_purge_lag", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{Global}", + "id":"317", + "unit":"NULL", + "description":"This variable controls how to delayINSERTUPDATE andDELETE operations whenpurge operations are lagging(see Section 14.5.2 InnoDB Multi-Versioning). The defaultvalue is 0 (no delays).The InnoDB transaction system maintains alist of transactions that have index records delete-marked byUPDATE orDELETE operations. The lengthof this list represents thepurge_lag value. Whenpurge_lag exceedsinnodb_max_purge_lag eachINSERTUPDATE andDELETE operation is delayed by((purge_lag/innodb_max_purge_lag)10)5milliseconds. The delay is computed in the beginning of apurge batch every ten seconds. The operations are not delayedif purge cannot run because of an oldconsistent readview that could see the rows to be purged.A typical setting for a problematic workload might be 1million assuming that transactions are small only 100 bytesin size and it is permissible to have 100MB of unpurgedInnoDB table rows.The lag value is displayed as the history list length in theTRANSACTIONS section of InnoDB Monitoroutput. For example if the output includes the followinglines the lag value is 20:For general I/O tuning advice seeSection 8.5.7 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"37", + "name":"innodb_old_blocks_pct", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"5", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_old_blocks_pct", + "vartype":"integer", + "max_value":"95", + "scope":"{Global}", + "id":"319", + "unit":"NULL", + "description":"Specifies the approximate percentage of theInnoDBbuffer pool used forthe old block sublist. Therange of values is 5 to 95. The default value is 37 (that is3/8 of the pool). SeeSection 14.7.2.3 Making the Buffer Pool Scan Resistant formore information. See Section 8.10.1 The InnoDB Buffer Pool forinformation about buffer pool management such as theLRU algorithm andeviction policies." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"innodb_old_blocks_time", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_old_blocks_time", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{Global}", + "id":"320", + "unit":"NULL", + "description":"Non-zero values protect against thebuffer pool beingfilled up by data that is referenced only for a brief periodsuch as during a fulltable scan. Increasing this value offers moreprotection against full table scans interfering with datacached in the buffer pool.Specifies how long in milliseconds (ms) a block inserted intothe old sublist must staythere after its first access before it can be moved to the newsublist. If the value is 0 a block inserted into the oldsublist moves immediately to the new sublist the first time itis accessed no matter how soon after insertion the accessoccurs. If the value is greater than 0 blocks remain in theold sublist until an access occurs at least that many ms afterthe first access. For example a value of 1000 causes blocksto stay in the old sublist for 1 second after the first accessbefore they become eligible to move to the new sublist.This variable is often used in combination withinnodb_old_blocks_pct. SeeSection 14.7.2.3 Making the Buffer Pool Scan Resistant formore information. See Section 8.10.1 The InnoDB Buffer Pool forinformation about buffer pool management such as theLRU algorithm andeviction policies." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"300", + "name":"innodb_open_files", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"10", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_open_files", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{Global}", + "id":"321", + "unit":"NULL", + "description":"This variable is relevant only if you use multipleInnoDBtablespaces. Itspecifies the maximum number of.ibdfiles that MySQL can keep open at one time. The minimumvalue is 10. The default value is 300.The file descriptors used for .ibd filesare for InnoDB tables only. They areindependent of those specified by the--open-files-limit serveroption and do not affect the operation of the table cache." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_print_all_deadlocks", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_print_all_deadlocks", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"322", + "unit":"NULL", + "description":"When this option is enabled information about alldeadlocks inInnoDB user transactions is recorded in themysqld errorlog. Otherwise you see information about only the lastdeadlock using the SHOW ENGINE INNODBSTATUS command. An occasionalInnoDB deadlock is not necessarily anissue because InnoDB detects the conditionimmediately and rolls back one of the transactionsautomatically. You might use this option to troubleshoot whydeadlocks are happening if an application does not haveappropriate error-handling logic to detect the rollback andretry its operation. A large number of deadlocks mightindicate the need to restructure transactions that issueDML or SELECT ... FORUPDATE statements for multiple tables so that eachtransaction accesses the tables in the same order thusavoiding the deadlock condition." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"20", + "name":"innodb_purge_batch_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_purge_batch_size", + "vartype":"integer", + "max_value":"5000", + "scope":"{Global}", + "id":"323", + "unit":"NULL", + "description":"The granularity of changes expressed in units ofredo log records thattrigger a purge operationflushing the changed bufferpool blocks to disk. This option is intended for tuningperformance in combination with the settinginnodb_purge_threads=nand typical users do not need to modify it." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"innodb_purge_threads", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_purge_threads", + "vartype":"integer", + "max_value":"1", + "scope":"{Global}", + "id":"324", + "unit":"NULL", + "description":"The number of background threads devoted to the InnoDBpurge operation. Currentlycan only be 0 (the default) or 1. The default value of 0signifies that the purge operation is performed as part of themaster thread.Running the purge operation in its own thread can reduceinternal contention within InnoDB improving scalability.Currently the performance gain might be minimal because thebackground thread might encounter different kinds ofcontention than before. This feature primarily lays thegroundwork for future performance work." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_random_read_ahead", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_random_read_ahead", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"325", + "unit":"NULL", + "description":"Enables the randomread-ahead techniquefor optimizing InnoDB I/O. Randomread-ahead functionality was removed from the InnoDBPlugin (version 1.0.4) and was therefore notincluded in MySQL 5.5.0 when InnoDB Pluginbecame the built-in version ofInnoDB. Random read-ahead was reintroducedin MySQL 5.1.59 and 5.5.16 and higher along with theinnodb_random_read_ahead configurationoption which is disabled by default.See Section 14.7.2.1 Configuring InnoDB Buffer Pool Prefetching (Read-Ahead) fordetails about the performance considerations for the differenttypes of read-ahead requests. For general I/O tuning advicesee Section 8.5.7 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1073741824", + "name":"max_binlog_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"4096", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_binlog_size", + "vartype":"integer", + "max_value":"1073741824", + "scope":"{Global}", + "id":"356", + "unit":"NULL", + "description":"If a write to the binary log causes the current log filesize to exceed the value of this variable the serverrotates the binary logs (closes the current file and opensthe next one). The minimum value is 4096 bytes. The maximumand default value is 1GB.A transaction is written in one chunk to the binary log soit is never split between several binary logs. Therefore ifyou have big transactions you might see binary log fileslarger thanmax_binlog_size.If max_relay_log_size is 0the value ofmax_binlog_size applies torelay logs as well." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"56", + "name":"innodb_read_ahead_threshold", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_read_ahead_threshold", + "vartype":"integer", + "max_value":"64", + "scope":"{Global}", + "id":"326", + "unit":"NULL", + "description":"Controls the sensitivity of linearread-ahead thatInnoDB uses to prefetch pages into thebuffer pool. IfInnoDB reads at leastinnodb_read_ahead_threshold pagessequentially from an extent(64 pages) it initiates an asynchronous read for the entirefollowing extent. The permissible range of values is 0 to 64.The default is 56: InnoDB must read atleast 56 pages sequentially from an extent to initiate anasynchronous read for the following extent.Knowing how many pages are read through this read-aheadmechanism and how many of them are evicted from the bufferpool without ever being accessed can be useful to helpfine-tune theinnodb_read_ahead_thresholdparameter. As of MySQL 5.5SHOW ENGINEINNODB STATUS output displays counter informationfrom theInnodb_buffer_pool_read_aheadandInnodb_buffer_pool_read_ahead_evictedglobal status variables. These variables indicate the numberof pages brought into thebuffer pool byread-ahead requests and the number of such pagesevicted from the bufferpool without ever being accessed respectively. These countersprovide global values since the last server restart.SHOW ENGINE INNODB STATUS also shows therate at which the read-ahead pages are read in and the rate atwhich such pages are evicted without being accessed. Theper-second averages are based on the statistics collectedsince the last invocation of SHOW ENGINE INNODBSTATUS and are displayed in the BUFFER POOLAND MEMORY section of the output.See Section 14.7.2.1 Configuring InnoDB Buffer Pool Prefetching (Read-Ahead) for moreinformation. For general I/O tuning advice seeSection 8.5.7 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"4", + "name":"innodb_read_io_threads", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_read_io_threads", + "vartype":"integer", + "max_value":"64", + "scope":"{Global}", + "id":"327", + "unit":"NULL", + "description":"The number of I/O threads for read operations inInnoDB. The default value is 4. Itscounterpart for write threads isinnodb_write_io_threads. SeeSection 14.7.6 Configuring the Number of Background InnoDB I/O Threads formore information. For general I/O tuning advice seeSection 8.5.7 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"innodb_replication_delay", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_replication_delay", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{Global}", + "id":"328", + "unit":"NULL", + "description":"The replication thread delay (in ms) on a slave server ifinnodb_thread_concurrency isreached." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_rollback_on_timeout", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_rollback_on_timeout", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"329", + "unit":"NULL", + "description":"In MySQL 5.5 InnoDBrolls back only the laststatement on a transaction timeout by default. If--innodb_rollback_on_timeout isspecified a transaction timeout causesInnoDB to abort and roll back the entiretransaction (the same behavior as in MySQL 4.1)." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"128", + "name":"innodb_rollback_segments", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_rollback_segments", + "vartype":"integer", + "max_value":"128", + "scope":"{Global}", + "id":"330", + "unit":"NULL", + "description":"Defines how many of therollback segmentsin the systemtablespace are used for InnoDBtransactions. Youmight reduce this value from its default of 128 if a smallernumber of rollback segments performs better for your workload." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"6", + "name":"innodb_spin_wait_delay", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_spin_wait_delay", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{Global}", + "id":"331", + "unit":"NULL", + "description":"The maximum delay between polls for aspin lock. The low-levelimplementation of this mechanism varies depending on thecombination of hardware and operating system so the delaydoes not correspond to a fixed time interval. The defaultvalue is 6. SeeSection 14.7.8 Configuring Spin Lock Polling formore information." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"nulls_equal", + "name":"innodb_stats_method", + "deprecated":"f", + "valid_vals":"nulls_equal,nulls_unequal,nulls_ignored", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_stats_method", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"332", + "unit":"NULL", + "description":"How the server treats NULL values whencollecting statisticsabout the distribution of index values forInnoDB tables. This variable has threepossible values nulls_equalnulls_unequal andnulls_ignored. Fornulls_equal all NULLindex values are considered equal and form a single valuegroup that has a size equal to the number ofNULL values. Fornulls_unequal NULLvalues are considered unequal and eachNULL forms a distinct value group of size1. For nulls_ignoredNULL values are ignored.The method that is used for generating table statisticsinfluences how the optimizer chooses indexes for queryexecution as described in Section 8.3.7 InnoDB and MyISAM Index Statistics Collection." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"ON", + "name":"innodb_stats_on_metadata", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_stats_on_metadata", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"333", + "unit":"NULL", + "description":"When this variable is enabled (which is the default as beforethe variable was created) InnoDB updatesstatistics whenmetadata statements such as SHOW TABLESTATUS or SHOW INDEXare run or when accessing theINFORMATION_SCHEMA.TABLES orINFORMATION_SCHEMA.STATISTICStables. (These updates are similar to what happens forANALYZE TABLE.) When disabledInnoDB does not update statistics duringthese operations. Disabling this variable can improve accessspeed for schemas that have a large number of tables orindexes. It can also improve the stability ofexecutionplans for queries that involveInnoDB tables.To change the setting issue the statement SET GLOBALinnodb_stats_on_metadata=modewhere mode iseither ON or OFF (or1 or 0). Changing thissetting requires the SUPER privilege andimmediately affects the operation of all connections." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"8", + "name":"innodb_stats_sample_pages", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_stats_sample_pages", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"334", + "unit":"NULL", + "description":"The number of index pages to sample for index distributionstatistics such as arecalculated by ANALYZE TABLE.The default value is 8. For additional information seeSection 14.7.10 Configuring Optimizer Statistics for InnoDB.Setting a high value forinnodb_stats_sample_pages could result inlengthy ANALYZE TABLE executiontime. To estimate the number of database pages accessed byANALYZE TABLE seeSection 14.7.10.1 Estimating ANALYZE TABLE Complexity for InnoDB Tables." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"false", + "name":"disable_gtid_unsafe_statements", + "deprecated":"t", + "valid_vals":"TRUE,FALSE", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for disable_gtid_unsafe_statements", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"364", + "unit":"NULL", + "description":"Obsolete: Replaced byenforce_gtid_consistency inMySQL 5.6.9. (Bug #14775984)" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_strict_mode", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_strict_mode", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"335", + "unit":"NULL", + "description":"When innodb_strict_mode isON InnoDB returnserrors rather than warnings for certain conditions. Thedefault value is OFF.Strict mode helpsguard against ignored typos and syntax errors in SQL or otherunintended consequences of various combinations of operationalmodes and SQL statements. Wheninnodb_strict_mode isON InnoDB raises errorconditions in certain cases rather than issuing a warning andprocessing the specified statement (perhaps with unintendedbehavior). This is analogous tosql_mode inMySQL which controls what SQL syntax MySQL accepts anddetermines whether it silently ignores errors or validatesinput syntax and data values.The innodb_strict_mode setting affects thehandling of syntax errors for CREATETABLE ALTER TABLEand CREATE INDEX statements.innodb_strict_mode also enables a recordsize check so that an INSERT orUPDATE never fails due to the record beingtoo large for the selected page size.Oracle recommends enablinginnodb_strict_mode when usingROW_FORMAT andKEY_BLOCK_SIZE clauses onCREATE TABLEALTER TABLE andCREATE INDEX statements. Wheninnodb_strict_mode isOFF InnoDB ignoresconflicting clauses and creates the table or index with onlya warning in the message log. The resulting table might havedifferent behavior than you intended such as having nocompression when you tried to create a compressed table. Wheninnodb_strict_mode isON such problems generate an immediateerror and the table or index is not created avoiding atroubleshooting session later.You can turn innodb_strict_modeON or OFF on the commandline when you start mysqld or in theconfigurationfile my.cnf ormy.ini. You can also enable or disableinnodb_strict_mode at runtime with thestatement SET [GLOBAL|SESSION]innodb_strict_mode=modewhere mode iseither ON or OFF.Changing the GLOBAL setting requires theSUPER privilege and affects the operationof all clients that subsequently connect. Any client canchange the SESSION setting forinnodb_strict_mode and the setting affectsonly that client." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"TRUE", + "name":"innodb_support_xa", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_support_xa", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"336", + "unit":"NULL", + "description":"Enables InnoDB support for two-phase commitin XA transactions causing anextra disk flush for transaction preparation. This setting isthe default. The XA mechanism is used internally and isessential for any server that has its binary log turned on andis accepting changes to its data from more than one thread. Ifyou turn it off transactions can be written to the binary login a different order from the one in which the live databaseis committing them. This can produce different data when thebinary log is replayed in disaster recovery or on areplication slave. Do not turn it off on a replication masterserver unless you have an unusual setup where only one threadis able to change data.For a server that is accepting data changes from only onethread it is safe and recommended to turn off this option toimprove performance for InnoDBtables. For example you can turn it off on replication slaveswhere only the replication SQL thread is changing data.You can also turn off this option if you do not need it forsafe binary logging or replication and you also do not use anexternal XA transaction manager." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"30", + "name":"innodb_sync_spin_loops", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_sync_spin_loops", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{Global}", + "id":"337", + "unit":"NULL", + "description":"The number of times a thread waits for anInnoDB mutex to be freed before the threadis suspended. The default value is 30." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"TRUE", + "name":"innodb_table_locks", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_table_locks", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"338", + "unit":"NULL", + "description":"If autocommit = 0InnoDB honors LOCKTABLES; MySQL does not return from LOCKTABLES ... WRITE until all other threads havereleased all their locks to the table. The default value ofinnodb_table_locks is 1which means that LOCK TABLEScauses InnoDB to lock a table internally ifautocommit = 0.As of MySQL 5.5.3 innodb_table_locks =0 has no effect for tables locked explicitly withLOCK TABLES ...WRITE. It still has an effect for tables locked forread or write byLOCK TABLES ...WRITE implicitly (for example through triggers) orby LOCK TABLES... READ." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"innodb_thread_concurrency", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_thread_concurrency", + "vartype":"integer", + "max_value":"1000", + "scope":"{Global}", + "id":"339", + "unit":"NULL", + "description":"InnoDB tries to keep the number ofoperating system threads concurrently insideInnoDB less than or equal to the limitgiven by this variable (InnoDB usesoperating system threads to process user transactions). Oncethe number of threads reaches this limit additional threadsare placed into a wait state within a First In FirstOut (FIFO) queue for execution. Threads waiting forlocks are not counted in the number of concurrently executingthreads.The range of this variable is 0 to 1000. A value of 0 (thedefault) is interpreted as infinite concurrency (noconcurrency checking). Disabling thread concurrency checkingenables InnoDB to create as many threads asit needs. A value of 0 also disables the queriesinside InnoDB and queries in queuecounters in the ROW OPERATIONSsection of SHOW ENGINE INNODB STATUSoutput.Consider setting this variable if your MySQL instance sharesCPU resources with other applications or if your workload ornumber of concurrent users is growing. The correct settingdepends on workload computing environment and the version ofMySQL that you are running. You will need to test a range ofvalues to determine the setting that provides the bestperformance. innodb_thread_concurrency is adynamic variable which allows you to experiment withdifferent settings on a live test system. If a particularsetting performs poorly you can quickly setinnodb_thread_concurrency back to 0.Use the following guidelines to help find and maintain anappropriate setting:For related information seeSection 14.7.5 Configuring Thread Concurrency for InnoDB." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"10000", + "name":"innodb_thread_sleep_delay", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_thread_sleep_delay", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"340", + "unit":"NULL", + "description":"How long InnoDB threads sleep beforejoining the InnoDB queue in microseconds.The default value is 10000. A value of 0 disables sleep.For more information seeSection 14.7.5 Configuring Thread Concurrency for InnoDB." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"binlog_direct_non_transactional_updates", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for binlog_direct_non_transactional_updates", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"349", + "unit":"NULL", + "description":"Due to concurrency issues a slave can become inconsistentwhen a transaction contains updates to both transactionaland nontransactional tables. MySQL tries to preservecausality among these statements by writing nontransactionalstatements to the transaction cache which is flushed uponcommit. However problems arise when modifications done tonontransactional tables on behalf of a transaction becomeimmediately visible to other connections because thesechanges may not be written immediately into the binary log.Beginning with MySQL 5.5.2 thebinlog_direct_non_transactional_updatesvariable offers one possible workaround to this issue. Bydefault this variable is disabled. Enablingbinlog_direct_non_transactional_updatescauses updates to nontransactional tables to be writtendirectly to the binary log rather than to the transactioncache.binlog_direct_non_transactional_updatesworks only for statements that are replicated using thestatement-based binary logging format; that isit works only when the value ofbinlog_format isSTATEMENT or whenbinlog_format isMIXED and a given statement is beingreplicated using the statement-based format. This variablehas no effect when the binary log format isROW or whenbinlog_format is set toMIXED and a given statement is replicatedusing the row-based format.Beginning with MySQL 5.5.5 this variable has no effect whenthe binary log format is ROW orMIXED. (Bug #51291)" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"gtid_done", + "deprecated":"t", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for gtid_done", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"365", + "unit":"NULL", + "description":"Obsolete: replaced in MySQL 5.6.9 bygtid_executed. (Bug#14775984)" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"ON", + "name":"innodb_use_native_aio", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_use_native_aio", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"341", + "unit":"NULL", + "description":"Specifies whether to use the Linux asynchronous I/O subsystem.This variable applies to Linux systems only and cannot bechanged while the server is running. Normally you do not needto touch this option because it is enabled by default.As of MySQL 5.5 theasynchronous I/Ocapability that InnoDB has on Windowssystems is available on Linux systems. (Other Unix-likesystems continue to use synchronous I/O calls.) This featureimproves the scalability of heavily I/O-bound systems whichtypically show many pending reads/writes in the output of thecommand SHOW ENGINE INNODB STATUSG.Running with a large number of InnoDB I/Othreads and especially running multiple such instances on thesame server machine can exceed capacity limits on Linuxsystems. In this case you may receive the following error:You can typically address this error by writing a higher limitto /proc/sys/fs/aio-max-nr.However if a problem with the asynchronous I/O subsystem inthe OS prevents InnoDB from starting youcan start the server withinnodb_use_native_aio=0disabled (useinnodb_use_native_aio=0 inthe option file). This option may also be turned offautomatically during startup if InnoDBdetects a potential problem such as a combination oftmpdir location tmpfsfilesystem and Linux kernel that does not support AIO ontmpfs.This variable was added in MySQL 5.5.4." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"innodb_trx_purge_view_update_only_debug", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_trx_purge_view_update_only_debug", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"342", + "unit":"NULL", + "description":"Pauses purging of delete-marked records while allowing thepurge view to be updated. This option artificially creates asituation in which the purge view is updated but purges havenot yet been performed. This option is only available ifdebugging support is compiled in using theWITH_DEBUGCMake option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"innodb_trx_rseg_n_slots_debug", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_trx_rseg_n_slots_debug", + "vartype":"integer", + "max_value":"1024", + "scope":"{Global}", + "id":"343", + "unit":"NULL", + "description":"Sets a debug flag that limitsTRX_RSEG_N_SLOTS to a given value for thetrx_rsegf_undo_find_free function whichlooks for a free slot for an undo log segment. This option isonly available if debugging support is compiled in using theWITH_DEBUGCMake option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"ON", + "name":"innodb_use_sys_malloc", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_use_sys_malloc", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"344", + "unit":"NULL", + "description":"Whether InnoDB uses the operating systemmemory allocator (ON) or its own(OFF). The default value isON. SeeSection 14.7.3 Configuring the Memory Allocator for InnoDB for moreinformation." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"innodb_version", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"345", + "unit":"NULL", + "description":"The InnoDB version number. Starting in5.5.30 the separate numbering for InnoDBis discontinued and this value is the same as for theversion variable." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"4", + "name":"innodb_write_io_threads", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_write_io_threads", + "vartype":"integer", + "max_value":"64", + "scope":"{Global}", + "id":"346", + "unit":"NULL", + "description":"The number of I/O threads for write operations inInnoDB. The default value is 4. Itscounterpart for read threads isinnodb_read_io_threads. SeeSection 14.7.6 Configuring the Number of Background InnoDB I/O Threads formore information. For general I/O tuning advice seeSection 8.5.7 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"log-bin", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for log-bin", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"347", + "unit":"NULL", + "description":"Enable binary logging. The server logs all statements thatchange data to the binary log which is used for backup andreplication. See Section 5.4.4 The Binary Log.The option value if given is the base name for the logsequence. The server creates binary log files in sequence byadding a numeric suffix to the base name. It is recommendedthat you specify a base name (see Section B.5.7 Known Issues in MySQLfor the reason). Otherwise MySQL useshost_name-binas the base name.In MySQL 5.5.20 and later when the server reads an entryfrom the index file it checks whether the entry contains arelative path and if it does the relative part of the pathis replaced with the absolute path set using the--log-bin option. An absolute path remainsunchanged; in such a case the index must be edited manuallyto enable the new path or paths to be used. Previous toMySQL 5.5.20 manual intervention was required wheneverrelocating the binary log or relay log files. (Bug#11745230 Bug #12133)Setting this option causes thelog_bin system variable tobe set to ON (or 1)and not to the base name. This is a known issue; see Bug#19614 for more information." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"32768", + "name":"binlog_cache_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"4096", + "dynamic":"t", + "rank":"-1", + "summary":"Options for binlog_cache_size", + "vartype":"integer", + "max_value":"18446744073709547520", + "scope":"{Global}", + "id":"348", + "unit":"NULL", + "description":"The size of the cache to hold changes to the binary logduring a transaction. A binary log cache is allocated foreach client if the server supports any transactional storageengines and if the server has the binary log enabled(--log-bin option). If youoften use large transactions you can increase this cachesize to get better performance. TheBinlog_cache_use andBinlog_cache_disk_usestatus variables can be useful for tuning the size of thisvariable. See Section 5.4.4 The Binary Log.In MySQL 5.5.3 a separate binary log cache (the binary logstatement cache) was introduced for nontransactionalstatements and in MySQL 5.5.3 through 5.5.8 this variablesets.the size for both caches. This means that in theseMySQL versions the total memory used for these caches isdouble the value set forbinlog_cache_size.Beginning with MySQL 5.5.9binlog_cache_size sets the size for thetransaction cache only and the size of the statement cacheis governed by thebinlog_stmt_cache_sizesystem variable." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"STATEMENT", + "name":"binlog_format", + "deprecated":"f", + "valid_vals":"ROW,STATEMENT,MIXED", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for binlog-format", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"350", + "unit":"NULL", + "description":"This variable sets the binary logging format and can be anyone of STATEMENT ROWor MIXED. SeeSection 17.1.2 Replication Formats.binlog_format is set by the--binlog-format option atstartup or by thebinlog_format systemvariable at runtime.In MySQL 5.5 the default format isSTATEMENT.Exception. In MySQL Cluster NDB 7.2.1 through MySQL Cluster NDB7.2.12 the default for this variable isSTATEMENT. In MySQL Cluster NDB 7.2.13and later when the NDBstorage engine is enabled the default isMIXED. (Bug #16417224) See alsoSection 18.6.6 Starting MySQL Cluster Replication (Single Replication Channel) andSection 18.6.7 Using Two Replication Channels for MySQL Cluster Replication.You must have the SUPERprivilege to set either the global or sessionbinlog_format value.The rules governing when changes to this variable takeeffect and how long the effect lasts are the same as forother MySQL server system variables. SeeSection 13.7.4 SET Syntax for more information.When MIXED is specified statement-basedreplication is used except for cases where only row-basedreplication is guaranteed to lead to proper results. Forexample this happens when statements contain user-definedfunctions (UDF) or the UUID()function. An exception to this rule is thatMIXED always uses statement-basedreplication for stored functions and triggers.There are exceptions when you cannot switch the replicationformat at runtime:Trying to switch the format in those cases results in anerror.The binary log format affects the behavior of the followingserver options:These effects are discussed in detail in the descriptions ofthe individual options." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"32768", + "name":"binlog_stmt_cache_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"4096", + "dynamic":"t", + "rank":"-1", + "summary":"Options for binlog_stmt_cache_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"351", + "unit":"NULL", + "description":"Beginning with MySQL 5.5.9 this variable determines thesize of the cache for the binary log to holdnontransactional statements issued during a transaction. InMySQL 5.5.3 and later separate binary log transaction andstatement caches are allocated for each client if the serversupports any transactional storage engines and if the serverhas the binary log enabled(--log-bin option). If youoften use large nontransactional statements duringtransactions you can increase this cache size to get moreperformance. TheBinlog_stmt_cache_use andBinlog_stmt_cache_disk_usestatus variables can be useful for tuning the size of thisvariable. See Section 5.4.4 The Binary Log.In MySQL 5.5.3 through 5.5.8 the size for both caches isset usingbinlog_cache_size. Thismeans that in these MySQL versions the total memory usedfor these caches is double the value set forbinlog_cache_size.Beginning with MySQL 5.5.9binlog_cache_size sets thesize for the transaction cache only." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"log_bin", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for log_bin", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"352", + "unit":"NULL", + "description":"Whether the binary log is enabled. If the--log-bin option is usedthen the value of this variable is ON;otherwise it is OFF. This variablereports only on the status of binary logging (enabled ordisabled); it does not actually report the value to which--log-bin is set.See Section 5.4.4 The Binary Log." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"log_bin_use_v1_row_events", + "deprecated":"f", + "valid_vals":"1,0", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for log_bin_use_v1_row_events", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"353", + "unit":"NULL", + "description":"Shows whether Version 2 binary logging available beginningwith MySQL Cluster NDB 7.2.1 is in use. A value of 1 showsthat the server is writing the binary log using Version 1logging events (the only version of binary log events usedin previous releases) and thus producing a binary log thatcan be read by older slaves. 0 indicates that Version 2binary log events are in use.This variable is read-only. To switch between Version 1 andVersion 2 binary event binary logging it is necessary torestart mysqld with the--log-bin-use-v1-row-eventsoption.Other than when performing upgrades of MySQL ClusterReplication --log-bin-use-v1-events ischiefly of interest when setting up replication conflictdetection and resolution usingNDB,EPOCH_TRANS() which requires Version2 binary row event logging. Thus this option and--ndb-log-transaction-id arenot compatible.This variable is not supported in mainline MySQL Server5.5.For more information seeSection 18.6.11 MySQL Cluster Replication Conflict Resolution." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"FALSE", + "name":"log_slave_updates", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"2", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for log_slave_updates", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"354", + "unit":"NULL", + "description":"Whether updates received by a slave server from a masterserver should be logged to the slave's own binary log.Binary logging must be enabled on the slave for thisvariable to have any effect. SeeSection 17.1.3 Replication and Binary Logging Options and Variables." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"18446744073709547520", + "name":"max_binlog_cache_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"4096", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_binlog_cache_size", + "vartype":"integer", + "max_value":"18446744073709547520", + "scope":"{Global}", + "id":"355", + "unit":"NULL", + "description":"If a transaction requires more than this many bytes ofmemory the server generates a Multi-statementtransaction required more than 'max_binlog_cache_size' bytesof storage error. The minimum value is 4096. Themaximum possible value is 16EB (exabytes). The maximumrecommended value is 4GB; this is due to the fact that MySQLcurrently cannot work with binary log positions greater than4GB.In MySQL 5.5.3 a separate binary log cache (the binary logstatement cache) was introduced for nontransactionalstatements and in MySQL 5.5.3 through 5.5.8 this variablesets.the upper limit for both caches. This means that inthese MySQL versions the effective maximum for these cachesis double the value set formax_binlog_cache_size.Beginning with MySQL 5.5.9max_binlog_cache_size sets the size forthe transaction cache only and the upper limit for thestatement cache is governed by themax_binlog_stmt_cache_sizesystem variable.Also beginning with MySQL 5.5.9 the session visibility ofthe max_binlog_cache_sizesystem variable matches that of thebinlog_cache_size systemvariable: In MySQL 5.5.8 and earlier releases a change inmax_binlog_cache_size tookimmediate effect; in MySQL 5.5.9 and later a change inmax_binlog_cache_size takeseffect only for new sessions that started after the value ischanged." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"50", + "name":"performance_schema_max_thread_classes", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_thread_classes", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"865", + "unit":"NULL", + "description":"The maximum number of thread instruments." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"18446744073709547520", + "name":"max_binlog_stmt_cache_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"4096", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_binlog_stmt_cache_size", + "vartype":"integer", + "max_value":"18446744073709547520", + "scope":"{Global}", + "id":"357", + "unit":"NULL", + "description":"If nontransactional statements within a transaction requiremore than this many bytes of memory the server generates anerror. The minimum value is 4096. The maximum and defaultvalues are 4GB on 32-bit platforms and 16EB (exabytes) on64-bit platforms.In MySQL 5.5.3 a separate binary log cache (the binary logstatement cache) was introduced for nontransactionalstatements and in MySQL 5.5.3 through 5.5.8 this variablesets.the upper limit for both caches. This means that inthese MySQL versions the effective maximum for these cachesis double the value set formax_binlog_cache_size.Beginning with MySQL 5.5.9max_binlog_stmt_cache_size sets the sizefor the statement cache only and the upper limit for thetransaction cache is governed exclusively by themax_binlog_cache_sizesystem variable." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"sync_binlog", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sync_binlog", + "vartype":"integer", + "max_value":"18446744073709547520", + "scope":"{Global}", + "id":"358", + "unit":"NULL", + "description":"If the value of this variable is greater than 0 the MySQLserver synchronizes its binary log to disk (usingfdatasync()) after everysync_binlog writes to thebinary log. There is one write to the binary log perstatement if autocommit is enabled and one write pertransaction otherwise. The default value ofsync_binlog is 0 whichdoes no synchronizing to diskin this case the serverrelies on the operating system to flush the binarylog's contents from time to time as for any other file.A value of 1 is the safest choice because in the event of acrash you lose at most one statement or transaction from thebinary log. However it is also the slowest choice (unlessthe disk has a battery-backed cache which makessynchronization very fast)." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"auto_increment_increment", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for auto_increment_increment", + "vartype":"integer", + "max_value":"65535", + "scope":"{GlobalSession}", + "id":"359", + "unit":"NULL", + "description":"auto_increment_incrementand auto_increment_offsetare intended for use with master-to-master replication andcan be used to control the operation ofAUTO_INCREMENT columns. Both variableshave global and session values and each can assume aninteger value between 1 and 65535 inclusive. Setting thevalue of either of these two variables to 0 causes its valueto be set to 1 instead. Attempting to set the value ofeither of these two variables to an integer greater than65535 or less than 0 causes its value to be set to 65535instead. Attempting to set the value ofauto_increment_increment orauto_increment_offset to anoninteger value gives rise to an error and the actualvalue of the variable remains unchanged.These two variables affect AUTO_INCREMENTcolumn behavior as follows:Should one or both of these variables be changed and thennew rows inserted into a table containing anAUTO_INCREMENT column the results mayseem counterintuitive because the series ofAUTO_INCREMENT values is calculatedwithout regard to any values already present in the columnand the next value inserted is the least value in the seriesthat is greater than the maximum existing value in theAUTO_INCREMENT column. In other wordsthe series is calculated like so:auto_increment_offset +N auto_increment_incrementwhere N is a positive integervalue in the series [123 ...]. For example:The values shown forauto_increment_incrementand auto_increment_offsetgenerate the series 5 + N 10 that is [515253545 ...]. The greatest valuepresent in the col column prior to theINSERT is 31 and the nextavailable value in the AUTO_INCREMENTseries is 35 so the inserted values forcol begin at that point and the resultsare as shown for the SELECTquery.It is not possible to confine the effects of these twovariables to a single table and thus they do not take theplace of the sequences offered by some other databasemanagement systems; these variables control the behavior ofall AUTO_INCREMENT columns inall tables on the MySQL server. If theglobal value of either variable is set its effects persistuntil the global value is changed or overridden by settingthe session value or until mysqld isrestarted. If the local value is set the new value affectsAUTO_INCREMENT columns for all tablesinto which new rows are inserted by the current user for theduration of the session unless the values are changedduring that session.The default value ofauto_increment_increment is1. SeeSection 17.4.1.1 Replication and AUTO_INCREMENT." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"auto_increment_offset", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"2", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for auto_increment_offset", + "vartype":"integer", + "max_value":"65535", + "scope":"{Global,Session}", + "id":"360", + "unit":"NULL", + "description":"This variable has a default value of 1. For particulars seethe description forauto_increment_increment." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"false", + "name":"disable-gtid-unsafe-statements", + "deprecated":"t", + "valid_vals":"TRUE,FALSE", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for disable-gtid-unsafe-statements", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"361", + "unit":"NULL", + "description":"Obsolete: Replaced by--enforce-gtid-consistency inMySQL 5.6.9. (Bug #14775984)" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"false", + "name":"enforce-gtid-consistency", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for enforce-gtid-consistency", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"362", + "unit":"NULL", + "description":"When enabled this option enforces GTID consistency byallowing execution of only those statements that can belogged in a transactionally safe manner. Youmust enable--enforce-gtid-consistency before setting--gtid-mode toON; otherwise enabling GTID mode failswith an error. You can (andshould) use this optionprior to using--gtid-mode in order to test whether thesystem is ready to use GTIDs.Since only transactionally safe statements can be loggedwhen --enforce-gtid-consistency is enabledit follows that the operations listed here cannot be usedwith this option:Prior to MySQL 5.6.9 this option was named--disable-gtid-unsafe-statements.(Bug #14775984)Prior to MySQL 5.6.7 using this option causednontransactional DML on temporary tables to fail althoughchanges to temporary tables are not logged when usingrow-based binary logging. In MySQL 5.6.7 and laternontransactional DML statements are allowed on temporarytables with--disable-gtid-unsafe-statements(--enforce-gtid-consistency beginning withMySQL 5.6.9) as long as all affected tables are temporarytables (Bug #14272672).Prior to MySQL 5.6.7 mysql_upgrade couldnot be used with a MySQL Server running with this optionenabled unless mysql_upgrade was runningwith --write-binlogexplicitly disabled. (Bug #13833710 Bug #14221043) In MySQL5.6.7 and later it is possible but not recommended to runmysql_upgrade on a server where--gtid-mode=ON since theMySQL system tables use theMyISAM storage engine which isnontransactional.In MySQL 5.6.8 and earlier you could not use any statementsaffecting nontransactional tables when--enforce-gtid-consistency was used (theoption was then called--disable-gtid-unsafe-statements).In MySQL 5.6.9 and later this option allows singlestatements updating nontransactional tables. This isintended chiefly for use with programs such asmysql_install_db andmysql_upgrade. (Bug #14722659)" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"FALSE", + "name":"binlog_gtid_simple_recovery", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for binlog_gtid_simple_recovery", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"363", + "unit":"NULL", + "description":"This variable controls how binary log files are iteratedduring the search for GTIDs when MySQL starts or restarts.In MySQL version 5.6.21 this variable was added assimplified_binlog_gtid_recovery and inMySQL version 5.6.23 it was renamed tobinlog_gtid_simple_recovery.Whenbinlog_gtid_simple_recovery=FALSEthe iteration starts from the newest file to initializegtid_executed and startsfrom the oldest file to initializegtid_purged. This processcould take a long time if you had a large number of binarylog files without GTID events for example created whengtid_mode=OFF.Whenbinlog_gtid_simple_recovery=TRUEthe server does not open more than two binary logs wheniterating to populategtid_purged andgtid_executed eitherduring server restart or when binary logs are being purged." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"COLLATION", + "name":"collation_connection", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for collation_connection", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"950", + "unit":"NULL", + "description":"The collation of the connection character set." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"false", + "name":"enforce_gtid_consistency", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for enforce_gtid_consistency", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"366", + "unit":"NULL", + "description":"When this variable is true the server enforces GTIDconsistency by allowing execution of only those statementsthat can be logged in a transactionally safe manner. Youmust enable GTID consistency (by using--enforce-gtid-consistency)before you can start the server with--gtid-mode=ON; otherwiseenabling GTID mode fails with an error. Youcan (and should)enable GTID consistency prior to using--gtid-mode in order to test whether thesystem is ready to use GTIDs.Since only transactionally safe statements can be loggedwhen enforce_gtid_consistency is true itfollows that the operations listed here cannot be used whenthis is the case:This variable is read-only. To set it use the--enforce-gtid-consistencyoption on the command line or in an option file whenstarting the MySQL Server.Prior to MySQL 5.6.9 this variable was nameddisable_gtid_unsafe_statements.(Bug #14775984)" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"gtid_executed", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for gtid_executed", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"367", + "unit":"NULL", + "description":"When used with global scope this variable contains arepresentation of the set of all transactions that arelogged in the binary log. This is the same as the value ofthe Executed_Gtid_Set column in theoutput of SHOW MASTER STATUSand SHOW SLAVE STATUS.When used with session scope this variable contains arepresentation of the set of transactions that are writtento the cache in the current session.The set of transactions that can be found in the binary logsat any given time is equal toGTID_SUBTRACT(@@global.gtid_executed@@global.gtid_purged); that is to alltransactions in the binary log that have not yet beenpurged.When the server starts@@global.gtid_executed is initialized tothe union of the following two sets:Thereafter GTIDs are added to the set as transactions areexecuted.Issuing RESET MASTER causesthe global value (but not the session value) of thisvariable to be reset to an empty string. GTIDs are nototherwise removed from this set other than when the set iscleared due to RESET MASTER. The set isalso cleared if the server is shut down and all binary logsare removed.Prior to MySQL 5.6.9 this variable was known asgtid_done." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"gtid_lost", + "deprecated":"t", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for gtid_lost", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"368", + "unit":"NULL", + "description":"Obsolete: Replaced bygtid_purged in MySQL 5.6.9.(Bug #14775984)" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"gtid_mode", + "deprecated":"f", + "valid_vals":"OFF,UPGRADE_STEP_1,UPGRADE_STEP_2,ON", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for gtid_mode", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"369", + "unit":"NULL", + "description":"Shows whether GTIDs are enabled. Read-only; set using--gtid-mode." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"AUTOMATIC", + "name":"gtid_next", + "deprecated":"f", + "valid_vals":"AUTOMATIC,ANONYMOUS,UUID:NUMBER", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for gtid_next", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Session}", + "id":"370", + "unit":"NULL", + "description":"This variable is used to specify whether and how the nextGTID is obtained. gtid_next can take anyof the following values:You must have the SUPERprivilege to set this variable. Setting this variable has noeffect if gtid_mode isOFF.Prior to MySQL 5.6.20 when GTIDs were enabled butgtid_next was notAUTOMATIC DROPTABLE did not work correctly when used on acombination of nontemporary tables with temporary tables orof temporary tables using transactional storage engines withtemporary tables using nontransactional storage engines. InMySQL 5.6.20 and later DROP TABLE orDROP TEMPORARY TABLE fails with anexplicit error when used with either of these combinationsof tables. (Bug #17620053)In MySQL 5.6.11 only you cannot execute any of thestatements CHANGE MASTER TOSTART SLAVESTOP SLAVEREPAIR TABLEOPTIMIZE TABLEANALYZE TABLECHECK TABLECREATE SERVERALTER SERVERDROP SERVERCACHE INDEXLOAD INDEX INTOCACHE FLUSH orRESET whengtid_next is set to anyvalue other than AUTOMATIC; in suchcases the statement fails with an error. Such statementsare not disallowed in MySQL 5.6.12 andlater. (Bug #16062608 Bug #16715809 Bug #69045)" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"gtid_owned", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for gtid_owned", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"371", + "unit":"NULL", + "description":"This read-only variable holds a list whose contents dependon its scope. When used with session scope the list holdsall GTIDs that are owned by this client; when used withglobal scope it holds a list of all GTIDs along with theirowners." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ALL", + "name":"audit_log_policy", + "deprecated":"f", + "valid_vals":"ALL,LOGINS,QUERIES,NONE", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for audit_log_policy", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"382", + "unit":"NULL", + "description":"The policy controlling how the audit log plugin writesevents to its log file. The following table shows thepermitted values.As of MySQL 5.6.20audit_log_policy can be setonly at server startup. At runtime it is a read-onlyvariable. This is due to the introduction of two othersystem variablesaudit_log_connection_policyandaudit_log_statement_policythat provide finer control over logging policy and that canbe set either at startup or at runtime. If you continue touse audit_log_policy atstartup instead of the other two variables the server usesits value to set those variables. For more information aboutthe policy variables and their interaction seeSection 6.4.3.4 Audit Log Plugin Logging Control.Before MySQL 5.6.20 theaudit_log_connection_policyandaudit_log_statement_policysystem variables do not exist.audit_log_policy is theonly policy control variable and it can be set at serverstartup or runtime." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"gtid_purged", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for gtid_purged", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"372", + "unit":"NULL", + "description":"The set of all transactions that have been purged from thebinary log. This is a subset of the set of transactions ingtid_executed.When the server starts the global value ofgtid_purged is initializedto the set of GTIDs contained by thePrevious_gtid_log_event of the oldestbinary log. When a binary log is purgedgtid_purged is re-read fromthe binary log that has now become the oldest one.Prior to MySQL 5.6.9 this variable was known asgtid_lost and wasread-only. In MySQL 5.6.9 and later it is possible toupdate the value of this variable. (Bug #14797808)To update the value of this variablegtid_mode must beONgtid_executed must be theempty string and thereforegtid_purged will also bethe empty string. This can occur either when replication hasnot been started previously or when replication was notpreviously using GTIDs.After executing SET gtid_purged youshould note down the current binary log filename which canbe checked using SHOW MASTERSTATUS. If the server is restarted before thisfile has been purged then you should usebinlog_gtid_simple_recovery=0(the default in 5.6) to avoidgtid_purged orgtid_executed beingcomputed incorrectly.Issuing RESET MASTER causesthe value of this variable to be reset to an empty string." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"FALSE", + "name":"simplified_binlog_gtid_recovery", + "deprecated":"t", + "valid_vals":"TRUE,FALSE", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for simplified_binlog_gtid_recovery", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"373", + "unit":"NULL", + "description":"This option is deprecated and will be removed in a futureMySQL release. Use the renamedbinlog_gtid_simple_recoveryto control how MySQL iterates through binary log files aftera crash." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1048576", + "name":"audit_log_buffer_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"4096", + "dynamic":"f", + "rank":"-1", + "summary":"Options for audit_log_buffer_size", + "vartype":"integer", + "max_value":"18446744073709547520", + "scope":"{Global}", + "id":"374", + "unit":"NULL", + "description":"When the audit log plugin writes events to the logasynchronously it uses a buffer to store event contentsprior to writing them. This variable controls the size ofthat buffer in bytes. The server adjusts the value to amultiple of 4096. The plugin uses a single buffer which itallocates when it initializes and removes when itterminates. The plugin allocates this buffer only if loggingis asynchronous." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ALL", + "name":"audit_log_connection_policy", + "deprecated":"f", + "valid_vals":"ALL,ERRORS,NONE", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for audit_log_connection_policy", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"375", + "unit":"NULL", + "description":"The policy controlling how the audit log plugin writesconnection events to its log file. The following table showsthe permitted values." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"audit_log_current_session", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for audit_log_current_session", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"376", + "unit":"NULL", + "description":"Whether audit logging is enabled for the current session.The session value of this variable is read only. It is setwhen the session begins based on the values of theaudit_log_include_accountsandaudit_log_exclude_accountssystem variables. The audit log plugin uses the sessionvalue to determine whether to audit events for the session.(There is a global value but the plugin does not use it.)" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"NULL", + "name":"audit_log_exclude_accounts", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for audit_log_exclude_accounts", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"377", + "unit":"NULL", + "description":"The accounts for which events should not be logged. Thevalue should be NULL or a stringcontaining a list of one or more comma-separated accountnames. For more information seeSection 6.4.3.4 Audit Log Plugin Logging Control.Modifications toaudit_log_exclude_accountsaffect only connections created subsequent to themodification not existing connections." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"audit.log", + "name":"audit_log_file", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for audit_log_file", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"378", + "unit":"NULL", + "description":"The name of the file to which the audit log plugin writesevents. The default value is audit.log.If the file name is a relative path the server interpretsit relative to the data directory. For security reasons theaudit log file should be written to a directory accessibleonly to the MySQL server and users with a legitimate reasonto view the log." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"audit_log_flush", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for audit_log_flush", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"379", + "unit":"NULL", + "description":"When this variable is set to enabled (1 orON) the audit log plugin closes andreopens its log file to flush it. (The value remainsOFF so that you need not disable itexplicitly before enabling it again to perform anotherflush.) Enabling this variable has no effect unlessaudit_log_rotate_on_size is0" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OLD", + "name":"audit_log_format", + "deprecated":"f", + "valid_vals":"OLD,NEW", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for audit_log_format", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"380", + "unit":"NULL", + "description":"The audit log file format. Permitted values areOLD and NEW (defaultOLD). For details about each format seeSection 6.4.3.3 The Audit Log File.If you change the value ofaudit_log_format use thisprocedure to avoid writing log entries in one format to anexisting log file that contains entries in a differentformat:" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"NULL", + "name":"audit_log_include_accounts", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for audit_log_include_accounts", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"381", + "unit":"NULL", + "description":"The accounts for which events should be logged. The valueshould be NULL or a string containing alist of one or more comma-separated account names. For moreinformation seeSection 6.4.3.4 Audit Log Plugin Logging Control.Modifications toaudit_log_include_accountsaffect only connections created subsequent to themodification not existing connections." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"audit_log_rotate_on_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for audit_log_rotate_on_size", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"383", + "unit":"NULL", + "description":"If theaudit_log_rotate_on_sizevalue is greater than 0 the audit log plugin closes andreopens its log file if a write to the file causes its sizeto exceed this value. The original file is renamed to have atimestamp extension.If theaudit_log_rotate_on_sizevalue is 0 the plugin does not close and reopen its logbased on size. Instead useaudit_log_flush to closeand reopen the log on demand. In this case rename the fileexternally to the server before flushing it.For more information about audit log file rotation andtimestamp interpretation seeSection 6.4.3.4 Audit Log Plugin Logging Control.If you set this variable to a value that is not a multipleof 4096 it is truncated to the nearest multiple. (Thussetting it to a value less than 4096 has the effect ofsetting it to 0 and no rotation occurs.)" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ALL", + "name":"audit_log_statement_policy", + "deprecated":"f", + "valid_vals":"ALL,ERRORS,NONE", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for audit_log_statement_policy", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"384", + "unit":"NULL", + "description":"The policy controlling how the audit log plugin writesstatement events to its log file. The following table showsthe permitted values." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ASYNCHRONOUS", + "name":"audit_log_strategy", + "deprecated":"f", + "valid_vals":"ASYNCHRONOUS,PERFORMANCE,SEMISYNCHRONOUS,SYNCHRONOUS", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for audit_log_strategy", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"385", + "unit":"NULL", + "description":"The logging method used by the audit log plugin. Thefollowing table describes the permitted values." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"basedir", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for basedir", + "vartype":"directory name", + "max_value":"NULL", + "scope":"{Global}", + "id":"386", + "unit":"NULL", + "description":"The path to the MySQL installation directory. All paths areusually resolved relative to this directory." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"datadir", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for datadir", + "vartype":"directory name", + "max_value":"NULL", + "scope":"{Global}", + "id":"387", + "unit":"NULL", + "description":"The path to the data directory." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"d:t:i:o/tmp/mysqld.trace", + "name":"debug", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for debug", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"388", + "unit":"NULL", + "description":"If MySQL is configured with the-DWITH_DEBUG=1CMake option you can use this option toget a trace file of what mysqld is doing. Atypical debug_options string isd:t:ofile_name.The default is d:t:i:o/tmp/mysqld.trace onUnix and d:t:i:Omysqld.trace on Windows.Using -DWITH_DEBUG=1 toconfigure MySQL with debugging support enables you to use the--debug=dparser_debug optionwhen you start the server. This causes the Bison parser thatis used to process SQL statements to dump a parser trace tothe server's standard error output. Typically this output iswritten to the error log.This option may be given multiple times. Values that beginwith + or - are added toor subtracted from the previous value. For example--debug=T--debug=+P sets the value toP:T.For more information see Section 24.5.3 The DBUG Package." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"flush", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for flush", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"389", + "unit":"NULL", + "description":"Flush (synchronize) all changes to disk after each SQLstatement. Normally MySQL does a write of all changes to diskonly after each SQL statement and lets the operating systemhandle the synchronizing to disk. SeeSection B.5.3.3 What to Do If MySQL Keeps Crashing." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"/usr/local/mysql/share/mysql/english/", + "name":"language", + "deprecated":"t", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for language", + "vartype":"directory name", + "max_value":"NULL", + "scope":"{Global}", + "id":"390", + "unit":"NULL", + "description":"The language to use for error messages.lang_name can be given as thelanguage name or as the full path name to the directory wherethe language files are installed. SeeSection 10.2 Setting the Error Message Language.--lc-messages-dir and--lc-messages should be usedrather than --language whichis deprecated as of MySQL 5.6.1 and handled as an alias for--lc-messages-dir. The--language option will beremoved in a future MySQL release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"log", + "deprecated":"t", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for log", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"391", + "unit":"NULL", + "description":"The --log option was removed inMySQL 5.6.1 (along with thelog system variable).Instead use the --general_logoption to enable the general query log and the--general_log_file=file_nameoption to set the general query log file name." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"min-examined-row-limit", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for min-examined-row-limit", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{GlobalSession}", + "id":"392", + "unit":"NULL", + "description":"When this option is set queries which examine fewer thannumber rows are not written to theslow query log. The default is 0." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"3306", + "name":"port", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"Options for port", + "vartype":"integer", + "max_value":"65535", + "scope":"{Global}", + "id":"393", + "unit":"NULL", + "description":"The port number to use when listening for TCP/IP connections.On Unix and Unix-like systems the port number must be 1024 orhigher unless the server is started by theroot system user." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"/tmp/mysql.sock", + "name":"socket", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for socket", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"394", + "unit":"NULL", + "description":"On Unix this option specifies the Unix socket file to usewhen listening for local connections. The default value is/tmp/mysql.sock. If this option is giventhe server creates the file in the data directory unless anabsolute path name is given to specify a different directory.On Windows the option specifies the pipe name to use whenlistening for local connections that use a named pipe. Thedefault value is MySQL (not casesensitive)." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1024", + "name":"group_concat_max_len", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"4", + "dynamic":"t", + "rank":"-1", + "summary":"Options for group_concat_max_len", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{GlobalSession}", + "id":"636", + "unit":"NULL", + "description":"The maximum permitted result length in bytes for theGROUP_CONCAT() function. Thedefault is 1024." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"tmpdir", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for tmpdir", + "vartype":"directory name", + "max_value":"NULL", + "scope":"{Global}", + "id":"395", + "unit":"NULL", + "description":"The path of the directory to use for creating temporary files.It might be useful if your default /tmpdirectory resides on a partition that is too small to holdtemporary tables. This option accepts several paths that areused in round-robin fashion. Paths should be separated bycolon characters (:) on Unixand semicolon characters (;)on Windows. If the MySQL server is acting as a replicationslave you should not set--tmpdir to point to adirectory on a memory-based file system or to a directory thatis cleared when the server host restarts. For more informationabout the storage location of temporary files seeSection B.5.3.5 Where MySQL Stores Temporary Files. A replication slave needssome of its temporary files to survive a machine restart sothat it can replicate temporary tables orLOAD DATAINFILE operations. If files in the temporary filedirectory are lost when the server restarts replicationfails." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"version", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"396", + "unit":"NULL", + "description":"Display version information and exit." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"4096", + "name":"mysql_firewall_max_query_size", + "deprecated":"t", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"Options for mysql_firewall_max_query_size", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{Global}", + "id":"397", + "unit":"NULL", + "description":"The maximum size of a normalized statement that can beinserted in the MySQL Enterprise Firewall cache. Normalized statements longerthan this size are truncated. Truncated statements arediscarded if the firewall mode for the current user isRECORDING and rejected if the mode isPROTECTING.mysql_firewall_max_query_sizewas removed in MySQL 5.6.26.max_digest_length shouldbe set large enough to avoid statement truncation." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"mysql_firewall_mode", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for mysql_firewall_mode", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"398", + "unit":"NULL", + "description":"Whether MySQL Enterprise Firewall is enabled (the default) or disabled." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"mysql_firewall_trace", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for mysql_firewall_trace", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"399", + "unit":"NULL", + "description":"Whether the MySQL Enterprise Firewall trace is enabled or disabled (thedefault). When enabledmysql_firewall_trace hasthis effect:" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"log-bin", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for log-bin", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"400", + "unit":"NULL", + "description":"Enable binary logging. The server logs all statements thatchange data to the binary log which is used for backup andreplication. See Section 5.4.4 The Binary Log.The option value if given is the base name for the logsequence. The server creates binary log files in sequence byadding a numeric suffix to the base name. It is recommendedthat you specify a base name (see Section B.5.7 Known Issues in MySQLfor the reason). Otherwise MySQL useshost_name-binas the base name.In MySQL 5.6.5 and later when the server reads an entryfrom the index file it checks whether the entry contains arelative path and if it does the relative part of the pathis replaced with the absolute path set using the--log-bin option. An absolute path remainsunchanged; in such a case the index must be edited manuallyto enable the new path or paths to be used. Previous toMySQL 5.6.5 manual intervention was required wheneverrelocating the binary log or relay log files. (Bug#11745230 Bug #12133)Setting this option causes thelog_bin system variable tobe set to ON (or 1)and not to the base name. Beginning with MySQL 5.6.2 thebinary log filename (with path) is available as thelog_bin_basename systemvariable." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"32768", + "name":"binlog_cache_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"4096", + "dynamic":"t", + "rank":"-1", + "summary":"Options for binlog_cache_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"401", + "unit":"NULL", + "description":"The size of the cache to hold changes to the binary logduring a transaction. A binary log cache is allocated foreach client if the server supports any transactional storageengines and if the server has the binary log enabled(--log-bin option). If youoften use large transactions you can increase this cachesize to get better performance. TheBinlog_cache_use andBinlog_cache_disk_usestatus variables can be useful for tuning the size of thisvariable. See Section 5.4.4 The Binary Log.binlog_cache_size sets the size for thetransaction cache only; the size of the statement cache isgoverned by thebinlog_stmt_cache_sizesystem variable." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"NONE", + "name":"binlog_checksum", + "deprecated":"f", + "valid_vals":"NONE,CRC32", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for binlog_checksum", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"402", + "unit":"NULL", + "description":"When enabled this variable causes the master to write achecksum for each event in the binary log.binlog_checksum supports the valuesNONE (disabled) andCRC32. The default isCRC32 as of MySQL 5.6.6NONE before that.When binlog_checksum is disabled (valueNONE) the server verifies that it iswriting only complete events to the binary log by writingand checking the event length (rather than a checksum) foreach event.Changing the value of this variable causes the binary log tobe rotated; checksums are always written to an entire binarylog file and never to only part of one.This variable was added in MySQL 5.6.2.In MySQL 5.6.6 and later setting this variable on themaster to a value unrecognized by the slave causes the slaveto set its own binlog_checksum value toNONE and to stop replication with anerror. (Bug #13553750 Bug #61096) If backward compatibilitywith older slaves is a concern you may want to set thevalue explicitly to NONE." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"have_compress", + "deprecated":"f", + "valid_vals":"YES,NO,DISABLED", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"637", + "unit":"NULL", + "description":"YES if the zlibcompression library is available to the serverNO if not. If not theCOMPRESS() andUNCOMPRESS() functions cannotbe used." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"binlog_direct_non_transactional_updates", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for binlog_direct_non_transactional_updates", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"403", + "unit":"NULL", + "description":"Due to concurrency issues a slave can become inconsistentwhen a transaction contains updates to both transactionaland nontransactional tables. MySQL tries to preservecausality among these statements by writing nontransactionalstatements to the transaction cache which is flushed uponcommit. However problems arise when modifications done tonontransactional tables on behalf of a transaction becomeimmediately visible to other connections because thesechanges may not be written immediately into the binary log.Thebinlog_direct_non_transactional_updatesvariable offers one possible workaround to this issue. Bydefault this variable is disabled. Enablingbinlog_direct_non_transactional_updatescauses updates to nontransactional tables to be writtendirectly to the binary log rather than to the transactioncache.binlog_direct_non_transactional_updatesworks only for statements that are replicated using thestatement-based binary logging format; that isit works only when the value ofbinlog_format isSTATEMENT or whenbinlog_format isMIXED and a given statement is beingreplicated using the statement-based format. This variablehas no effect when the binary log format isROW or whenbinlog_format is set toMIXED and a given statement is replicatedusing the row-based format.In MySQL 5.6 this variable has no effect whenthe binary log format is ROW orMIXED. (Bug #51291)" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"IGNORE_ERROR", + "name":"binlog_error_action", + "deprecated":"f", + "valid_vals":"IGNORE_ERROR,ABORT_SERVER", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for binlog_error_action", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"404", + "unit":"NULL", + "description":"Controls what happens when the server cannot write to thebinary log which can cause the master's log to becomeinconsistent and replication slaves to lose synchronization.Previous releases used the namebinlogging_impossible_mode.In MySQL 5.6 the default forbinlog_error_action isIGNORE_ERROR meaning the server logs theerror halts logging and continues performing updates; thisis to provide backward compatibility with older versions ofthe MySQL Server. Setting this variable toABORT_SERVER makes the server haltlogging and shut down whenever it cannot write to the binarylog; this is the recommended setting particularly incomplex replication environments." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"MIXED", + "name":"binlog_format", + "deprecated":"f", + "valid_vals":"ROW,STATEMENT,MIXED", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for binlog-format", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"405", + "unit":"NULL", + "description":"This variable sets the binary logging format and can be anyone of STATEMENT ROWor MIXED. SeeSection 17.1.2 Replication Formats.binlog_format is set by the--binlog-format option atstartup or by thebinlog_format variable atruntime.In MySQL 5.6 the default format isSTATEMENT.Exception: In MySQL Cluster NDB 7.3 andlater the default is MIXED;statement-based replication is not supported for MySQLCluster.You must have the SUPERprivilege to set either the global or sessionbinlog_format value.The rules governing when changes to this variable takeeffect and how long the effect lasts are the same as forother MySQL server system variables. SeeSection 13.7.4 SET Syntax for more information.When MIXED is specified statement-basedreplication is used except for cases where only row-basedreplication is guaranteed to lead to proper results. Forexample this happens when statements contain user-definedfunctions (UDF) or the UUID()function. An exception to this rule is thatMIXED always uses statement-basedreplication for stored functions and triggers.There are exceptions when you cannot switch the replicationformat at runtime:Trying to switch the format in those cases results in anerror.The binary log format affects the behavior of the followingserver options:These effects are discussed in detail in the descriptions ofthe individual options." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"IGNORE_ERROR", + "name":"binlogging_impossible_mode", + "deprecated":"t", + "valid_vals":"IGNORE_ERROR,ABORT_SERVER", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for binlogging_impossible_mode", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"406", + "unit":"NULL", + "description":"This option is deprecated and will be removed in a futureMySQL release. Use the renamedbinlog_error_action tocontrol what happens when the server cannot write to thebinary log." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"binlog_max_flush_queue_time", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for binlog_max_flush_queue_time", + "vartype":"integer", + "max_value":"100000", + "scope":"{Global}", + "id":"407", + "unit":"NULL", + "description":"How long in microseconds to keep reading transactions fromthe flush queue before proceeding with the group commit (andsyncing the log to disk ifsync_binlog is greater than0). If the value is 0 (the default) there is no timeout andthe server keeps reading new transactions until the queue isempty.Normallybinlog_max_flush_queue_timecan remain set to 0. If the server processes a large numberof connections (for example 100 or more) and many shorttransactions with low-latency requirements it may be usefulto set the value larger than 0 to force more frequentflushes to disk.This variable was added in MySQL 5.6.6." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"binlog_order_commits", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for binlog_order_commits", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"408", + "unit":"NULL", + "description":"If this variable is enabled (the default) transactions arecommitted in the same order they are written to the binarylog. If disabled transactions may be committed in parallel.In some cases disabling this variable might produce aperformance increment.This variable was added in MySQL 5.6.6." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"full", + "name":"binlog_row_image", + "deprecated":"f", + "valid_vals":"full, (Log all columns),minimal, (Log only changed columns, and columns needed to identify rows),noblob, (Log all columns, except for unneeded BLOB and TEXT columns)", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for binlog_row_image", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"409", + "unit":"NULL", + "description":"In MySQL row-based replication each row change eventcontains two images a before image whosecolumns are matched against when searching for the row to beupdated and an after image containing thechanges. Normally MySQL logs full rows (that is allcolumns) for both the before and after images. However itis not strictly necessary to include every column in bothimages and we can often save disk memory and networkusage by logging only those columns which are actuallyrequired.For the before image it is necessary only that the minimumset of columns required to uniquely identify rows is logged.If the table containing the row has a primary key then onlythe primary key column or columns are written to the binarylog. Otherwise if the table has a unique key all of whosecolumns are NOT NULL then only thecolumns in the unique key need be logged. (If the table hasneither a primary key nor a unique key without anyNULL columns then all columns must beused in the before image and logged.) In the after imageit is necessary to log only the columns which have actuallychanged.In MySQL 5.6 you can cause the server to log full orminimal rows using the binlog_row_imagesystem variable. This variable actually takes one of threepossible values as shown in the following list:The default value is full. In MySQL 5.5and earlier full row images are always used for both beforeimages and after images. If you need to replicate from aMySQL 5.6 (or later) master to a slave running a previousversion of MySQL the master should always use this value.When using minimal ornoblob deletes and updates areguaranteed to work correctly for a given table if and onlyif the following conditions are true for both the source anddestination tables:(In other words the tables must be identical with thepossible exception of indexes that are not part of thetables' primary keys.)If these conditions are not met it is possible that theprimary key column values in the destination table may proveinsufficient to provide a unique match for a delete orupdate. In this event no warning or error is issued; themaster and slave silently diverge thus breakingconsistency.Setting this variable has no effect when the binary loggingformat is STATEMENT. Whenbinlog_format isMIXED the setting forbinlog_row_image is applied to changesthat are logged using row-based format but this setting noeffect on changes logged as statements.Setting binlog_row_image on either theglobal or session level does not cause an implicit commit;this means that this variable can be changed while atransaction is in progress without affecting thetransaction." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"FALSE", + "name":"binlog_rows_query_log_events", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for binlog_rows_query_log_events", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"410", + "unit":"NULL", + "description":"Thebinlog_rows_query_log_eventssystem variable affects row-based logging only. Whenenabled it causes a MySQL 5.6.2 or later server to writeinformational log events such as row query log events intoits binary log. This information can be used for debuggingand related purposes; such as obtaining the original queryissued on the master when it cannot be reconstructed fromthe row updates.These events are normally ignored by MySQL 5.6.2 and laterprograms reading the binary log and so cause no issues whenreplicating or restoring from backup. This is not true for amysqld or mysqlbinlogfrom MySQL 5.6.1 or earlier: When the older version of theprogram reading the log encounters an informational logevent it fails and stops reading at that point. To makethe binary log readable by slave replication MySQL serversand other readers (for examplemysqlbinlog) from a MySQL 5.6.1 orearlier distributionbinlog_rows_query_log_eventsmust be disabled during logging." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"84", + "name":"ft_max_word_len", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"10", + "dynamic":"f", + "rank":"-1", + "summary":"Options for ft_max_word_len", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"985", + "unit":"NULL", + "description":"The maximum length of the word to be included in aMyISAM FULLTEXT index." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"32768", + "name":"binlog_stmt_cache_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"4096", + "dynamic":"t", + "rank":"-1", + "summary":"Options for binlog_stmt_cache_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"411", + "unit":"NULL", + "description":"This variable determines the size of the cache for thebinary log to hold nontransactional statements issued duringa transaction. Separate binary log transaction and statementcaches are allocated for each client if the server supportsany transactional storage engines and if the server has thebinary log enabled (--log-binoption). If you often use large nontransactional statementsduring transactions you can increase this cache size to getbetter performance. TheBinlog_stmt_cache_use andBinlog_stmt_cache_disk_usestatus variables can be useful for tuning the size of thisvariable. See Section 5.4.4 The Binary Log.The binlog_cache_sizesystem variable sets the size for the transaction cache." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"log_bin", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for log_bin", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"412", + "unit":"NULL", + "description":"Whether the binary log is enabled. If the--log-bin option is usedthen the value of this variable is ON;otherwise it is OFF. This variablereports only on the status of binary logging (enabled ordisabled); it does not actually report the value to which--log-bin is set.See Section 5.4.4 The Binary Log." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"datadir + '/' + hostname + '-bin'", + "name":"log_bin_basename", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for log_bin_basename", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"413", + "unit":"NULL", + "description":"Holds the name and complete path to the binary log file.Unlike the log_bin systemvariable log_bin_basenamereflects the name set with the--log-bin server option.The log_bin_basename systemvariable was added in MySQL 5.6.2." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"log_bin_index", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for log_bin_index", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"414", + "unit":"NULL", + "description":"The index file for binary log file names.The log_bin_index systemvariable was added in MySQL 5.6.4." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"log_bin_use_v1_row_events", + "deprecated":"f", + "valid_vals":"1,0", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for log_bin_use_v1_row_events", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"415", + "unit":"NULL", + "description":"Shows whether Version 2 binary logging available beginningwith MySQL 5.6.6 is in use. A value of 1 shows that theserver is writing the binary log using Version 1 loggingevents (the only version of binary log events used in MySQL5.6.5 and previous MySQL Server releases) and thusproducing a binary log that can be read by older slaves. 0indicates that Version 2 binary log events are in use.This variable is read-only. To switch between Version 1 andVersion 2 binary event binary logging it is necessary torestart mysqld with the--log-bin-use-v1-row-eventsoption.Other than when performing upgrades of MySQL ClusterReplication --log-bin-use-v1-events ischiefly of interest when setting up replication conflictdetection and resolution usingNDB,EPOCH_TRANS() which requires Version2 binary row event logging. Thus this option and--ndb-log-transaction-id arenot compatible.For more information seeSection 18.6.11 MySQL Cluster Replication Conflict Resolution." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"FALSE", + "name":"log_slave_updates", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for log_slave_updates", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"416", + "unit":"NULL", + "description":"Whether updates received by a slave server from a masterserver should be logged to the slave's own binary log.Binary logging must be enabled on the slave for thisvariable to have any effect. SeeSection 17.1.4 Replication and Binary Logging Options and Variables." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"master_verify_checksum", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for master_verify_checksum", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"417", + "unit":"NULL", + "description":"Enabling this variable causes the master to examinechecksums when reading from the binary log.master_verify_checksum is disabled bydefault; in this case the master uses the event length fromthe binary log to verify events so that only completeevents are read from the binary log.This variable was added in MySQL 5.6.2." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"18446744073709551615", + "name":"max_binlog_cache_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"4096", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_binlog_cache_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"418", + "unit":"NULL", + "description":"If a transaction requires more than this many bytes ofmemory the server generates a Multi-statementtransaction required more than 'max_binlog_cache_size' bytesof storage error. The minimum value is 4096. Themaximum possible value is 16EB (exabytes). The maximumrecommended value is 4GB; this is due to the fact that MySQLcurrently cannot work with binary log positions greater than4GB.max_binlog_cache_size sets the size forthe transaction cache only; the upper limit for thestatement cache is governed by themax_binlog_stmt_cache_sizesystem variable.In MySQL 5.6 the visibility to sessions ofmax_binlog_cache_size matches that of thebinlog_cache_size systemvariable; in other words changing its value effects onlynew sessions that are started after the value is changed." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1073741824", + "name":"max_binlog_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"4096", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_binlog_size", + "vartype":"integer", + "max_value":"1073741824", + "scope":"{Global}", + "id":"419", + "unit":"NULL", + "description":"If a write to the binary log causes the current log filesize to exceed the value of this variable the serverrotates the binary logs (closes the current file and opensthe next one). The minimum value is 4096 bytes. The maximumand default value is 1GB.A transaction is written in one chunk to the binary log soit is never split between several binary logs. Therefore ifyou have big transactions you might see binary log fileslarger thanmax_binlog_size.If max_relay_log_size is 0the value ofmax_binlog_size applies torelay logs as well." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"100", + "name":"bgwriter_lru_maxpages", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Background writer maximum number of LRU pages to flush per round.", + "vartype":"integer", + "max_value":"1000", + "scope":"{Global}", + "id":"1475", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"18446744073709547520", + "name":"max_binlog_stmt_cache_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"4096", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_binlog_stmt_cache_size", + "vartype":"integer", + "max_value":"18446744073709547520", + "scope":"{Global}", + "id":"420", + "unit":"NULL", + "description":"If nontransactional statements within a transaction requiremore than this many bytes of memory the server generates anerror. The minimum value is 4096. The maximum and defaultvalues are 4GB on 32-bit platforms and 16EB (exabytes) on64-bit platforms.max_binlog_stmt_cache_size sets the sizefor the statement cache only; the upper limit for thetransaction cache is governed exclusively by themax_binlog_cache_sizesystem variable." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"sync_binlog", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sync_binlog", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{Global}", + "id":"421", + "unit":"NULL", + "description":"If the value of this variable is greater than 0 the MySQLserver synchronizes its binary log to disk (usingfdatasync()) aftersync_binlog commit groupsare written to the binary log. The default value ofsync_binlog is 0 whichdoes no synchronizing to diskin this case the serverrelies on the operating system to flush the binarylog's contents from time to time as for any other file.A value of 1 is the safest choice because in the event of acrash you lose at most one commit group from the binary log.However it is also the slowest choice (unless the disk hasa battery-backed cache which makes synchronization veryfast)." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"slave_compressed_protocol", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for slave_compressed_protocol", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"422", + "unit":"NULL", + "description":"If this option is set to 1 use compression for theslave/master protocol if both the slave and the mastersupport it. The default is 0 (no compression)." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"init_slave", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for init_slave", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"423", + "unit":"NULL", + "description":"This variable is similar toinit_connect but is astring to be executed by a slave server each time the SQLthread starts. The format of the string is the same as forthe init_connect variable." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"log_slow_slave_statements", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for log_slow_slave_statements", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"424", + "unit":"NULL", + "description":"When the slow query log is enabled this variable enableslogging for queries that have taken more thanlong_query_time seconds toexecute on the slave. This variable was added in MySQL5.6.11." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"FILE", + "name":"master_info_repository", + "deprecated":"f", + "valid_vals":"FILE,TABLE", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for master_info_repository", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"425", + "unit":"NULL", + "description":"The setting of this variable determines whether the slavelogs master status and connection information to aFILE (master.info)or to a TABLE(mysql.slave_master_info).The setting of this variable also has a direct bearing onthe effect had by the setting of thesync_master_info systemvariable; see that variable's description for furtherinformation.This variable was added in MySQL 5.6.2." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"relay_log", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for relay-log", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"426", + "unit":"NULL", + "description":"The name of the relay log file." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"datadir + '/' + hostname + '-relay-bin'", + "name":"relay_log_basename", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for relay_log_basename", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"427", + "unit":"NULL", + "description":"Holds the name and complete path to the relay log file.The relay_log_basenamesystem variable was added in MySQL 5.6.2." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"*host_name*-relay-bin.index", + "name":"relay_log_index", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for relay_log_index", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"428", + "unit":"NULL", + "description":"The name of the relay log index file. The default name ishost_name-relay-bin.indexin the data directory wherehost_name is the name of theslave server." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"relay-log.info", + "name":"relay_log_info_file", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for relay_log_info_file", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"429", + "unit":"NULL", + "description":"The name of the file in which the slave records informationabout the relay logs. The default name isrelay-log.info in the data directory." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"FILE", + "name":"relay_log_info_repository", + "deprecated":"f", + "valid_vals":"FILE,TABLE", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for relay_log_info_repository", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"430", + "unit":"NULL", + "description":"This variable determines whether the slave's positionin the relay logs is written to a FILE(relay-log.info) or to aTABLE(mysql.slave_relay_log_info).The setting of this variable also has a direct bearing onthe effect had by the setting of thesync_relay_log_info systemvariable; see that variable's descrption for furtherinformation.This variable was added in MySQL 5.6.2." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1073741824", + "name":"slave_max_allowed_packet", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1024", + "dynamic":"t", + "rank":"-1", + "summary":"Options for slave_max_allowed_packet", + "vartype":"integer", + "max_value":"1073741824", + "scope":"{Global}", + "id":"437", + "unit":"NULL", + "description":"In MySQL 5.6.6 and later this variable sets the maximumpacket size for the slave SQL and I/O threads so that largeupdates using row-based replication do not cause replicationto fail because an update exceededmax_allowed_packet.This global variable always has a value that is a positiveinteger multiple of 1024; if you set it to some value thatis not the value is rounded down to the next highestmultiple of 1024 for it is stored or used; settingslave_max_allowed_packet to 0 causes 1024to be used. (A truncation warning is issued in all suchcases.) The default and maximum value is 1073741824 (1 GB);the minimum is 1024.slave_max_allowed_packet can also be setat startup using the--slave-max-allowed-packetoption." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"3600", + "name":"slave_net_timeout", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for slave-net-timeout", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"438", + "unit":"NULL", + "description":"The number of seconds to wait for more data from amaster/slave connection before aborting the read." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"FALSE", + "name":"relay_log_recovery", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for relay_log_recovery", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"431", + "unit":"NULL", + "description":"Enables automatic relay log recovery immediately followingserver startup. The recovery process creates a new relay logfile initializes the SQL thread position to this new relaylog and initializes the I/O thread to the SQL threadposition. Reading of the relay log from the master thencontinues. In MySQL 5.6.5 and earlier it was possible tochange this global variable dynamically; beginning withMySQL 5.6.6 it is read-only. (Bug #13840948) Regardless ofthe MySQL Server version its value can be changed bystarting the slave with the--relay-log-recovery optionwhich should be used following a crash on the replicationslave to ensure that no possibly corrupted relay logs areprocessed and must be used in order to guarantee acrash-safe slave. The default value is 0 (disabled).When relay_log_recovery is enabled andthe slave has stopped due to errors encountered whilerunning in multi-threaded mode you cannot executeCHANGE MASTER TO if there areany gaps in the log. Beginning with MySQL 5.6.6 you shoulduse START SLAVEUNTIL SQL_AFTER_MTS_GAPS to ensure that all gapsare processed before switching back to single-threaded modeor executing a CHANGE MASTER TOstatement." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"31536000", + "name":"rpl_stop_slave_timeout", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"2", + "dynamic":"t", + "rank":"-1", + "summary":"Options for rpl_stop_slave_timeout", + "vartype":"integer", + "max_value":"31536000", + "scope":"{Global}", + "id":"432", + "unit":"NULL", + "description":"In MySQL 5.6.13 and later you can control the length oftime (in seconds) that STOPSLAVE waits before timing out by setting thisvariable. This can be used to avoid deadlocks betweenSTOP SLAVE and other slave SQL statementsusing different client connections to the slave. The maximumand default value ofrpl_stop_slave_timeout is 31536000seconds (1 year). The minimum is 2 seconds." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"512", + "name":"slave_checkpoint_group", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"32", + "dynamic":"t", + "rank":"-1", + "summary":"Options for slave_checkpoint_group", + "vartype":"integer", + "max_value":"524280", + "scope":"{Global}", + "id":"433", + "unit":"8", + "description":"Sets the maximum number of transactions that can beprocessed by a multi-threaded slave before a checkpointoperation is called to update its status as shown bySHOW SLAVE STATUS. Settingthis variable has no effect on slaves for whichmulti-threading is not enabled.This variable works in combination with theslave_checkpoint_periodsystem variable in such a way that when either limit isexceeded the checkpoint is executed and the counterstracking both the number of transactions and the timeelapsed since the last checkpoint are reset.The minimum allowed value for this variable is 32 unlessthe server was built using-DWITH_DEBUG in which casethe minimum value is 1. The effective value is always amultiple of 8; you can set it to a value that is not such amultiple but the server rounds it down to the next lowermultiple of 8 before storing the value.(Exception: No such rounding isperformed by the debug server.) Regardless of how the serverwas built the default value is 512 and the maximum allowedvalue is 524280.slave_checkpoint_group was added in MySQL5.6.3." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"300", + "name":"slave_checkpoint_period", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for slave_checkpoint_period", + "vartype":"integer", + "max_value":"4294967296", + "scope":"{Global}", + "id":"434", + "unit":"NULL", + "description":"Sets the maximum time (in milliseconds) that is allowed topass before a checkpoint operation is called to update thestatus of a multi-threaded slave as shown bySHOW SLAVE STATUS. Settingthis variable has no effect on slaves for whichmulti-threading is not enabled.This variable works in combination with theslave_checkpoint_groupsystem variable in such a way that when either limit isexceeded the checkpoint is executed and the counterstracking both the number of transactions and the timeelapsed since the last checkpoint are reset.The minimum allowed value for this variable is 1 unless theserver was built using-DWITH_DEBUG in which casethe minimum value is 0. Regardless of how the server wasbuilt the default value is 300 and the maximum possiblevalue is 4294967296 (4GB).slave_checkpoint_period was added inMySQL 5.6.3." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":" (NDB)", + "name":"slave_exec_mode", + "deprecated":"f", + "valid_vals":"IDEMPOTENT,STRICT", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for slave_exec_mode", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"435", + "unit":"NULL", + "description":"Controls how a slave thread resolves conflicts and errorsduring replication. IDEMPOTENT modecauses suppression of duplicate-key and no-key-found errors.This mode should be employed in multi-master replicationcircular replication and some other special replicationscenarios. STRICT mode is the defaultand is suitable for most other cases.This mode is needed for multi-master replication circularreplication and some other special replication scenariosfor MySQL Cluster Replication. (SeeSection 18.6.10 MySQL Cluster Replication: Multi-Master and Circular ReplicationandSection 18.6.11 MySQL Cluster Replication Conflict Resolutionfor more information.) The mysqldsupplied with MySQL Cluster ignores any value explicitly setfor slave_exec_mode andalways treats it as IDEMPOTENT.In MySQL Server 5.6 STRICTmode is the default value. This should not be changed;currently IDEMPOTENT mode is supportedonly by NDB and is used whenreplicating NDB toInnoDB." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"/tmp", + "name":"slave_load_tmpdir", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for slave-load-tmpdir", + "vartype":"directory name", + "max_value":"NULL", + "scope":"{Global}", + "id":"436", + "unit":"NULL", + "description":"The name of the directory where the slave creates temporaryfiles for replicatingLOAD DATAINFILE statements." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_api_enable_mdl", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_api_enable_mdl", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"465", + "unit":"NULL", + "description":"Locks the table used by the InnoDBmemcached plugin so that it cannot bedropped or altered by DDLthrough the SQL interface. SeeSection 14.18 InnoDB memcached Plugin for usage details for thisoption." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"slave_parallel_workers", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for slave_parallel_workers", + "vartype":"integer", + "max_value":"1024", + "scope":"{Global}", + "id":"439", + "unit":"NULL", + "description":"Sets the number of slave worker threads for executingreplication events (transactions) in parallel. Setting thisvariable to 0 (the default) disables parallel execution. Themaximum is 1024.When parallel execution is enabled the slave SQL threadacts as the coordinator for the slave worker threads amongwhich transactions are distributed on a per-database basis.This means that a worker thread on the slave slave canprocess successive transactions on a given database withoutwaiting for updates to other databases to complete. Thecurrent implementation of multi-threading on the slaveassumes that the data is partitioned per database and thatupdates within a given database occur in the same relativeorder as they do on the master in order to work correctly.However transactions do not need to be coordinated betweenany two databases.Due to the fact that transactions on different databases canoccur in a different order on the slave than on the masterchecking for the most recently executed transaction does notguarantee that all previous transactions from the masterhave been executed on the slave. This has implications forlogging and recovery when using a multi-threaded slave. Forinformation about how to interpret binary logginginformation when using multi-threading on the slave seeSection 13.7.5.35 SHOW SLAVE STATUS Syntax. In addition this meansthat STARTSLAVE UNTIL is not supported with a multi-threadedslave.When multi-threading is enabledslave_transaction_retriesis treated as equal to 0 and cannot be changed. (Currentlyretrying of transactions is not supported withmulti-threaded slaves.)This variable was added in MySQL 5.6.3." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"16777216", + "name":"slave_pending_jobs_size_max", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1024", + "dynamic":"t", + "rank":"-1", + "summary":"Options for slave_pending_jobs_size_max", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"440", + "unit":"1024", + "description":"For multi-threaded slaves this variable sets the maximumamount of memory (in bytes) available to slave worker queuesholding events not yet applied. Setting this variable has noeffect on slaves for which multi-threading is not enabled.The minimum possible value for this variable is 1024; thedefault is 16MB. The maximum possible value is18446744073709551615 (16 exabytes). Values that are notexact multiples of 1024 are rounded down to the next-highestmultiple of 1024 prior to being stored.slave_pending_jobs_size_max was added inMySQL 5.6.3." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"TABLE_SCANINDEX_SCAN", + "name":"slave_rows_search_algorithms", + "deprecated":"f", + "valid_vals":"TABLE_SCAN,INDEX_SCAN,INDEX_SCAN,HASH_SCAN,TABLE_SCAN,HASH_SCAN,TABLE_SCAN,INDEX_SCAN,HASH_SCAN, (equivalent to INDEX_SCAN,HASH_SCAN)", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for slave_rows_search_algorithms", + "vartype":"set", + "max_value":"NULL", + "scope":"{Global}", + "id":"441", + "unit":"NULL", + "description":"When preparing batches of rows for row-based logging andreplication using theslave_rows_search_algorithmsvariable controls how the rows are searched formatchesthat is whether or not hashing is used forsearches using a primary or unique key using some otherkey or using no key at all. This option takes acomma-separated list of at least 2 values from the listINDEX_SCANTABLE_SCAN HASH_SCAN.The value is expected as a string so the value must bequoted. In addition the value must not contain any spaces.Possible combinations (lists) and their effects are shown inthe following table:The order in which the algorithms are specified in the listdoes not make any difference in the order in which they aredisplayed by a SELECT orSHOW VARIABLES statement asshown here:The default value isTABLE_SCANINDEX_SCAN which means thatall searches that can use indexes do use them and searcheswithout any indexes use table scans.SpecifyingINDEX_SCANTABLE_SCANHASH_SCAN has thesame effect as specifyingINDEX_SCANHASH_SCAN. To use hashing forany searches that does not use a primary or unique key setthis variable to INDEX_SCANHASH_SCAN. Toforce hashing for all searches set itto TABLE_SCANHASH_SCAN.This variable was added in MySQL 5.6.6." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"slave_skip_errors", + "deprecated":"f", + "valid_vals":"OFF,[list of error codes],all", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for slave-skip-errors", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"442", + "unit":"NULL", + "description":"Normally replication stops when an error occurs on theslave. This gives you the opportunity to resolve theinconsistency in the data manually. This variable tells theslave SQL thread to continue replication when a statementreturns any of the errors listed in the variable value." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"slave_sql_verify_checksum", + "deprecated":"f", + "valid_vals":"0,1", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for slave_sql_verify_checksum", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"443", + "unit":"NULL", + "description":"Cause the slave SQL thread to verify data using thechecksums read from the relay log. In the event of amismatch the slave stops with an error.slave_sql_verify_checksum was added inMySQL 5.6.2." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"10", + "name":"slave_transaction_retries", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for slave_transaction_retries", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"444", + "unit":"NULL", + "description":"If a replication slave SQL thread fails to execute atransaction because of anInnoDB deadlock or because thetransaction's execution time exceededInnoDB'sinnodb_lock_wait_timeout orNDB'sTransactionDeadlockDetectionTimeoutorTransactionInactiveTimeoutit automatically retriesslave_transaction_retriestimes before stopping with an error. The default value is10Transactions cannot be retried when using a multi-threadedslave. In other words wheneverslave_parallel_workers isgreater than 0 slave_transaction_retriesis treated as equal to 0 and cannot be changed." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"slave_type_conversions", + "deprecated":"f", + "valid_vals":"ALL_LOSSY,ALL_NON_LOSSY", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for slave_type_conversions", + "vartype":"set", + "max_value":"NULL", + "scope":"{Global}", + "id":"445", + "unit":"NULL", + "description":"Controls the type conversion mode in effect on the slavewhen using row-based replication. In MySQL 5.6.13 and laterits value is a comma-delimited set of zero or more elementsfrom the list: ALL_LOSSYALL_NON_LOSSYALL_SIGNEDALL_UNSIGNED. Set this variable to anempty string to disallow type conversions between the masterand the slave. Changes require a restart of the slave totake effect.ALL_SIGNED andALL_UNSIGNED were added in MySQL 5.6.13(Bug#15831300). For additional information on typeconversion modes applicable to attribute promotion anddemotion in row-based replication seeRow-based replication: attribute promotion and demotion." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"sql_slave_skip_counter", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sql_slave_skip_counter", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"446", + "unit":"NULL", + "description":"The number of events from the master that a slave servershould skip.This option is incompatible with GTID-based replication andmust not be set to a nonzero value when--gtid-mode=ON. In MySQL5.6.10 and later trying to do so is specificallydisallowed. (Bug #15833516) If you need to skip transactionswhen employing GTIDs usegtid_executed from themaster instead. SeeInjecting empty transactions forinformation about how to do this." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"4", + "name":"ft_min_word_len", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"f", + "rank":"-1", + "summary":"Options for ft_min_word_len", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"986", + "unit":"NULL", + "description":"The minimum length of the word to be included in aMyISAM FULLTEXT index." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"sync_master_info", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sync_master_info", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"447", + "unit":"NULL", + "description":"The effects of this variable on a replication slave dependon whether the slave'smaster_info_repository isset to FILE or TABLEas explained in the following paragraphs.master_info_repository = FILE. If the value of sync_master_info isgreater than 0 the slave synchronizes itsmaster.info file to disk (usingfdatasync()) after everysync_master_info events. If it is 0the MySQL server performs no synchronization of themaster.info file to disk; insteadthe server relies on the operating system to flush itscontents periodically as with any other file.master_info_repository = TABLE. If the value of sync_master_info isgreater than 0 the slave updates its master inforepository table after everysync_master_info events. If it is 0the table is never updated.The default value for sync_master_info is10000 as of MySQL 5.6.6 0 before that." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"sync_relay_log", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sync_relay_log", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"448", + "unit":"NULL", + "description":"If the value of this variable is greater than 0 the MySQLserver synchronizes its relay log to disk (usingfdatasync()) after everysync_relay_log events are written to therelay log.Setting sync_relay_log to 0 causes nosynchronization to be done to disk; in this case the serverrelies on the operating system to flush the relay log'scontents from time to time as for any other file.Prior to MySQL 5.6.6 0 was the default for this variable.In MySQL 5.6. and later the default is 10000.A value of 1 is the safest choice because in the event of acrash you lose at most one event from the relay log.However it is also the slowest choice (unless the disk hasa battery-backed cache which makes synchronization veryfast)." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"sync_relay_log_info", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sync_relay_log_info", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"449", + "unit":"NULL", + "description":"The effects of this variable on the slave depend on theserver'srelay_log_info_repositorysetting (FILE orTABLE) and if this isTABLE additionally on whether thestorage engine used by the relay log info table istransactional (such as InnoDB)or not (MyISAM). The effects ofthese factors on the behavior of the server forsync_relay_log_info values of zero andgreater than zero are shown in the following table:The default value for sync_relay_log_infois 10000 as of MySQL 5.6.6 0 before that." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"false", + "name":"daemon_memcached_enable_binlog", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for daemon_memcached_enable_binlog", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"450", + "unit":"NULL", + "description":"See Section 14.18 InnoDB memcached Plugin for usage details forthis option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"innodb_engine.so", + "name":"daemon_memcached_engine_lib_name", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for daemon_memcached_engine_lib_name", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"451", + "unit":"NULL", + "description":"Specifies the shared library that implements theInnoDB memcached plugin.See Section 14.18 InnoDB memcached Plugin for usage details forthis option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"NULL", + "name":"daemon_memcached_engine_lib_path", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for daemon_memcached_engine_lib_path", + "vartype":"directory name", + "max_value":"NULL", + "scope":"{Global}", + "id":"452", + "unit":"NULL", + "description":"The path of the directory containing the shared library thatimplements the InnoDBmemcached plugin. The default value isNULL representing the MySQL plugin directory. You should notneed to modify this parameter unless specifying a differentstorage engine memcached plugin that islocated outside of the MySQL plugin directory.See Section 14.18 InnoDB memcached Plugin for usage details forthis option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"daemon_memcached_option", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for daemon_memcached_option", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"453", + "unit":"NULL", + "description":"Used to pass space-separated memcached options to theunderlying memcached memory object cachingdaemon on startup. For example you might change the port thatmemcached listens on reduce the maximumnumber of simultaneous connections change the maximum memorysize for a key/value pair or enable debugging messages forthe error log.See Section 14.18 InnoDB memcached Plugin for usage details forthis option. For information about memcached options refer tothe memcached man page." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"daemon_memcached_r_batch_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for daemon_memcached_r_batch_size", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"454", + "unit":"NULL", + "description":"Specifies how many memcached readoperations (get) to perform before doing aCOMMIT to start a newtransaction. Counterpart ofdaemon_memcached_w_batch_size.This value is set to 1 by default so that any changes made tothe table through SQL statements are immediately visible tothe memcached operations. You mightincrease it to reduce the overhead from frequent commits on asystem where the underlying table is only being accessedthrough the memcached interface. If you setthe value too large the amount of undo or redo data couldimpose some storage overhead as with any long-runningtransaction.See Section 14.18 InnoDB memcached Plugin for usage details forthis option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"innodb_api_trx_level", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_api_trx_level", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"466", + "unit":"NULL", + "description":"Lets you control the transactionisolation level onqueries processed by the memcachedinterface. See Section 14.18 InnoDB memcached Plugin for usagedetails for this option. The constants corresponding to thefamiliar names are:" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"have_crypt", + "deprecated":"f", + "valid_vals":"YES,NO,DISABLED", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"638", + "unit":"NULL", + "description":"YES if the crypt()system call is available to the server NOif not. If not the ENCRYPT()function cannot be used." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"daemon_memcached_w_batch_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for daemon_memcached_w_batch_size", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"455", + "unit":"NULL", + "description":"Specifies how many memcached writeoperations such as addset or incr to performbefore doing a COMMIT to starta new transaction. Counterpart ofdaemon_memcached_r_batch_size.This value is set to 1 by default on the assumption that anydata being stored is important to preserve in case of anoutage and should immediately be committed. When storingnon-critical data you might increase this value to reduce theoverhead from frequent commits; but then the lastN-1 uncommitted write operationscould be lost in case of a crash.See Section 14.18 InnoDB memcached Plugin for usage details forthis option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"ignore_builtin_innodb", + "deprecated":"t", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for ignore-builtin-innodb", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"456", + "unit":"NULL", + "description":"See the description of--ignore-builtin-innodb underInnoDB Command Optionsearlier in this section." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"ON", + "name":"innodb_adaptive_flushing", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_adaptive_flushing", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"457", + "unit":"NULL", + "description":"Specifies whether to dynamically adjust the rate of flushingdirty pages in theInnoDBbuffer pool based onthe workload. Adjusting the flush rate dynamically is intendedto avoid bursts of I/O activity. This setting is enabled bydefault. SeeSection 14.4.3.2 Configuring the Rate of InnoDB Buffer Pool Flushing formore information. For general I/O tuning advice seeSection 8.5.8 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"10", + "name":"innodb_adaptive_flushing_lwm", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_adaptive_flushing_lwm", + "vartype":"integer", + "max_value":"70", + "scope":"{Global}", + "id":"458", + "unit":"NULL", + "description":"Low water mark representing percentage ofredo log capacity atwhich adaptiveflushing is enabled." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"ON", + "name":"innodb_adaptive_hash_index", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_adaptive_hash_index", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"459", + "unit":"NULL", + "description":"Whether the InnoDBadaptive hashindex is enabled or disabled. It may be desirabledepending on your workload to dynamically enable or disableadaptive hashindexing to improve query performance. Because theadaptive hash index may not be useful for all workloadsconduct benchmarks with it both enabled and disabled usingrealistic workloads. SeeSection 14.2.5.6 Adaptive Hash Indexes for details.This variable is enabled by default. You can modify thisparameter using the SET GLOBAL statementwithout restarting the server. Changing the setting requiresthe SUPER privilege. You can also use--skip-innodb_adaptive_hash_index at serverstartup to disable it.Disabling the adaptive hash index empties the hash tableimmediately. Normal operations can continue while the hashtable is emptied and executing queries that were using thehash table access the index B-trees directly instead. When theadaptive hash index is re-enabled the hash table is populatedagain during normal operation." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"150000", + "name":"innodb_adaptive_max_sleep_delay", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_adaptive_max_sleep_delay", + "vartype":"integer", + "max_value":"1000000", + "scope":"{Global}", + "id":"460", + "unit":"NULL", + "description":"Allows InnoDB to automatically adjust thevalue ofinnodb_thread_sleep_delay upor down according to the current workload. Any non-zero valueenables automated dynamic adjustment of theinnodb_thread_sleep_delay value up to themaximum value specified in theinnodb_adaptive_max_sleep_delay option. Thevalue represents the number of microseconds. This option canbe useful in busy systems with greater than 16InnoDB threads. (In practice it is mostvaluable for MySQL systems with hundreds or thousands ofsimultaneous connections.)For more information seeSection 14.4.6 Configuring Thread Concurrency for InnoDB." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"8388608", + "name":"innodb_additional_mem_pool_size", + "deprecated":"t", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"2097152", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_additional_mem_pool_size", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{Global}", + "id":"461", + "unit":"NULL", + "description":"The size in bytes of a memory pool InnoDBuses to store datadictionary information and other internal datastructures. The more tables you have in your application themore memory you allocate here. If InnoDBruns out of memory in this pool it starts to allocate memoryfrom the operating system and writes warning messages to theMySQL error log. The default value is 8MB.This variable relates to the InnoDBinternal memory allocator which is unused ifinnodb_use_sys_malloc isenabled. As of MySQL 5.6.3innodb_additional_mem_pool_size isdeprecated and will be removed in a future MySQL release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"5", + "name":"innodb_api_bk_commit_interval", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_api_bk_commit_interval", + "vartype":"integer", + "max_value":"1073741824", + "scope":"{Global}", + "id":"462", + "unit":"NULL", + "description":"How often to auto-commit idle connections that use theInnoDB memcachedinterface in seconds. See Section 14.18 InnoDB memcached Pluginfor usage details for this option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_api_disable_rowlock", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_api_disable_rowlock", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"463", + "unit":"NULL", + "description":"Use this variable to disable row locks whenInnoDB memcachedperforms DML operations. By defaultinnodb_api_disable_rowlock is set toOFF which means thatmemcached requests row locks for get andset operations. Wheninnodb_api_disable_rowlock is set toON memcached requests atable lock instead of row locks.The innodb_api_disable_rowlock option isnot dynamic. It must be specified on themysqld command line or entered in the MySQLconfiguration file. Configuration takes effect when the pluginis installed which you do each time the MySQL server isstarted." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_api_enable_binlog", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_api_enable_binlog", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"464", + "unit":"NULL", + "description":"Lets you use the InnoDBmemcached plugin with the MySQLbinary log. SeeSection 14.18 InnoDB memcached Plugin for usage details for thisoption." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"8", + "name":"innodb_autoextend_increment", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_autoextend_increment", + "vartype":"integer", + "max_value":"1000", + "scope":"{Global}", + "id":"467", + "unit":"NULL", + "description":"The increment size (in MB) for extending the size of anauto-extend InnoDBsystemtablespace file when it becomes full. The default valueis 64 as of MySQL 5.6.6 8 before that. This variable does notaffect the per-table tablespace files that are created if youuse innodb_file_per_table=1.Those files are auto-extending regardless of the value ofinnodb_autoextend_increment.The initial extensions are by small amounts after whichextensions occur in increments of 4MB." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1", + "name":"innodb_autoinc_lock_mode", + "deprecated":"f", + "valid_vals":"0,1,2", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_autoinc_lock_mode", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"468", + "unit":"NULL", + "description":"The lock mode to use forgeneratingauto-incrementvalues. The permissible values are 01 or 2 fortraditional consecutive orinterleaved lock mode respectively.Section 14.6.5 AUTO_INCREMENT Handling in InnoDB describesthe characteristics of these modes.This variable has a default of 1 (consecutivelock mode)." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_buffer_pool_dump_at_shutdown", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_buffer_pool_dump_at_shutdown", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"469", + "unit":"NULL", + "description":"Specifies whether to record the pages cached in the InnoDBbuffer pool when theMySQL server is shut down to shorten thewarmup process at the nextrestart. Typically used in combination withinnodb_buffer_pool_load_at_startup.For related information seeSection 14.4.3.5 Preloading the InnoDB Buffer Pool for Faster Restart." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_buffer_pool_dump_now", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_buffer_pool_dump_now", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"470", + "unit":"NULL", + "description":"Immediately records the pages cached in the InnoDBbuffer pool. Typicallyused in combination withinnodb_buffer_pool_load_now.For related information seeSection 14.4.3.5 Preloading the InnoDB Buffer Pool for Faster Restart." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ib_buffer_pool", + "name":"innodb_buffer_pool_filename", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_buffer_pool_filename", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"471", + "unit":"NULL", + "description":"Specifies the name of the file that holds the list oftablespace IDs and page IDs produced byinnodb_buffer_pool_dump_at_shutdownorinnodb_buffer_pool_dump_now.Tablespace IDs and page IDs are saved in the following format:space page_id. By default the file islocated in the InnoDB data directory.For related information seeSection 14.4.3.5 Preloading the InnoDB Buffer Pool for Faster Restart." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1", + "name":"innodb_buffer_pool_instances", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_buffer_pool_instances", + "vartype":"integer", + "max_value":"64", + "scope":"{Global}", + "id":"472", + "unit":"NULL", + "description":"The number of regions that the InnoDBbuffer pool is dividedinto. For systems with buffer pools in the multi-gigabyterange dividing the buffer pool into separate instances canimprove concurrency by reducing contention as differentthreads read and write to cached pages. Each page that isstored in or read from the buffer pool is assigned to one ofthe buffer pool instances randomly using a hashing function.Each buffer pool manages its own free listsflush listsLRUs and all other datastructures connected to a buffer pool and is protected by itsown buffer pool mutex.This option takes effect only when you set theinnodb_buffer_pool_size to asize of 1GB or more. The total size you specify is dividedamong all the buffer pools. For best efficiency specify acombination ofinnodb_buffer_pool_instancesand innodb_buffer_pool_sizeso that each buffer pool instance is at least 1GB.Before MySQL 5.6.6 the default is 1. The default value inMySQL 5.6.6 and higher on 32-bit Windows systems depends onthe value ofinnodb_buffer_pool_size asdescribed below:On all other platforms the default value in MySQL 5.6.6 andhigher is 8 wheninnodb_buffer_pool_size isgreater than or equal to 1GB. Otherwise the default is 1." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_buffer_pool_load_abort", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_buffer_pool_load_abort", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"473", + "unit":"NULL", + "description":"Interrupts the process of restoring InnoDBbuffer pool contentstriggered byinnodb_buffer_pool_load_at_startuporinnodb_buffer_pool_load_now.For related information seeSection 14.4.3.5 Preloading the InnoDB Buffer Pool for Faster Restart." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_buffer_pool_load_at_startup", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_buffer_pool_load_at_startup", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"474", + "unit":"NULL", + "description":"Specifies that on MySQL server startup the InnoDBbuffer pool isautomatically warmed up byloading the same pages it held at an earlier time. Typicallyused in combination withinnodb_buffer_pool_dump_at_shutdown.For related information seeSection 14.4.3.5 Preloading the InnoDB Buffer Pool for Faster Restart." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_buffer_pool_load_now", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_buffer_pool_load_now", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"475", + "unit":"NULL", + "description":"Immediately warms up theInnoDB buffer pool byloading a set of data pages without waiting for a serverrestart. Can be useful to bring cache memory back to a knownstate during benchmarking or to ready the MySQL server toresume its normal workload after running queries for reportsor maintenance.For related information seeSection 14.4.3.5 Preloading the InnoDB Buffer Pool for Faster Restart." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"5", + "name":"innodb_compression_failure_threshold_pct", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_compression_failure_threshold_pct", + "vartype":"integer", + "max_value":"100", + "scope":"{Global}", + "id":"484", + "unit":"NULL", + "description":"Sets the cutoff point at which MySQL begins adding paddingwithin compressedpages to avoid expensivecompressionfailures. A value of zero disables the mechanism thatmonitors compression efficiency and dynamically adjusts thepadding amount.For more information seeSection 14.7.6 Compression for OLTP Workloads." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"134217728", + "name":"innodb_buffer_pool_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"5242880", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_buffer_pool_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"476", + "unit":"NULL", + "description":"The size in bytes of thebuffer pool thememory area where InnoDB caches table andindex data. The default value is 128MB. The maximum valuedepends on the CPU architecture; the maximum is 4294967295(232-1) on 32-bit systems and18446744073709551615 (264-1) on64-bit systems. On 32-bit systems the CPU architecture andoperating system may impose a lower practical maximum sizethan the stated maximum. When the size of the buffer pool isgreater than 1GB settinginnodb_buffer_pool_instancesto a value greater than 1 can improve the scalability on abusy server.A larger buffer pool requires less disk I/O to access the sametable data more than once. On a dedicated database server youmight set the buffer pool size to 80% of the machine'sphysical memory size. Be aware of the following potentialissues when configuring buffer pool size and be prepared toscale back the size of the buffer pool if necessary." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"25", + "name":"innodb_change_buffer_max_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_change_buffer_max_size", + "vartype":"integer", + "max_value":"50", + "scope":"{Global}", + "id":"477", + "unit":"NULL", + "description":"Maximum size for the InnoDBchange buffer as apercentage of the total size of thebuffer pool. You mightincrease this value for a MySQL server with heavy insertupdate and delete activity or decrease it for a MySQL serverwith unchanging data used for reporting. For general I/Otuning advice see Section 8.5.8 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"all", + "name":"innodb_change_buffering", + "deprecated":"f", + "valid_vals":"none,inserts,deletes,changes,purges,all", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_change_buffering", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"478", + "unit":"NULL", + "description":"Whether InnoDB performschange bufferingan optimization that delays write operations to secondaryindexes so that the I/O operations can be performedsequentially. The permitted values are described in thefollowing table. For more information seeSection 14.4.5 Configuring InnoDB Change Buffering. Forgeneral I/O tuning advice seeSection 8.5.8 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"innodb_change_buffering_debug", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_change_buffering_debug", + "vartype":"integer", + "max_value":"2", + "scope":"{Global}", + "id":"479", + "unit":"NULL", + "description":"Sets a debug flag for InnoDB changebuffering. A value of 1 forces all changes to the changebuffer. A value of 2 causes a crash at merge. A default valueof 0 indicates that the change buffering debug flag is notset. This option is only available when debugging support iscompiled in using the WITH_DEBUGCMake option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"innodb", + "name":"innodb_checksum_algorithm", + "deprecated":"f", + "valid_vals":"innodb,crc32,none,strict_innodb,strict_crc32,strict_none", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_checksum_algorithm", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"480", + "unit":"NULL", + "description":"Specifies how to generate and verify thechecksum stored in eachdisk block of each InnoDBtablespace.innodb_checksum_algorithm replaces theinnodb_checksums option as ofMySQL 5.6.3. The following values are provided forcompatibility:To avoid conflicts remove references toinnodb_checksums from yourconfiguration file and MySQL startup scripts.The value innodb is backward-compatiblewith all versions of MySQL. The value crc32uses an algorithm that is faster to compute the checksum forevery modified block and to check the checksums for each diskread. It scans blocks 32 bits at a time which is faster theinnodb checksum algorithm which scansblocks 8 bits at a time. The value nonewrites a constant value in the checksum field rather thancomputing a value based on the block data. The blocks in atablespace can use a mix of old new and no checksum valuesbeing updated gradually as the data is modified; once anyblocks in a tablespace are modified to use thecrc32 algorithm the associated tablescannot be read by earlier versions of MySQL.The strict_* forms work the same asinnodb crc32 andnone except that InnoDBreports an error if it encounters a valid but non-matchingchecksum value in the tablespace. It is recommended that youonly use the strict_* options in a newinstance to set up all tablespaces for the first time. Thestrict_* settings are somewhat fasterbecause they do not need to compute all checksum values duringdisk reads.The following table illustrates the difference between thenone innodb andcrc32 option values and theirstrict_ counterparts.none innodb andcrc32 write the specified type of checksumvalue into each data block but for compatibility accept anyof the other checksum values when verifying a block during aread operation. The strict_ form of eachparameter also accepts any valid checksum value but prints anerror message when a valid non-matching checksum value isencountered. Using the strict_ form canmake verification faster if all InnoDB datafiles in an instance are created under an identicalinnodb_checksum_algorithm value.The default value forinnodb_checksum_algorithm was changed frominnodb to crc32 in MySQL5.6.6 but switched back to innodb in 5.6.7for improved compatibility of InnoDB datafiles during a downgrade to an earlier MySQL version and foruse with MySQLEnterprise Backup. The limitations encounteredincluded:" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"ON", + "name":"innodb_checksums", + "deprecated":"t", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_checksums", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"481", + "unit":"NULL", + "description":"InnoDB can usechecksum validation onall tablespace pages read from the disk to ensure extra faulttolerance against hardware faults or corrupted data files.This validation is enabled by default. Under specializedcircumstances (such as when running benchmarks) this extrasafety feature can be disabled with--skip-innodb-checksums. You can specify themethod of calculating the checksum withinnodb_checksum_algorithm.In MySQL 5.6.3 and higher this option is deprecated replacedby innodb_checksum_algorithm.innodb_checksum_algorithm=innodb is thesame as innodb_checksums=ON (the default).innodb_checksum_algorithm=none is the sameas innodb_checksums=OFF. Remove anyinnodb_checksums options from yourconfiguration files and startup scripts to avoid conflictswith innodb_checksum_algorithm:innodb_checksums=OFF would automaticallyset innodb_checksum_algorithm=none;innodb_checksums=ON would be ignored andoverridden by any other setting forinnodb_checksum_algorithm." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_cmp_per_index_enabled", + "deprecated":"f", + "valid_vals":"OFF,ON", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_cmp_per_index_enabled", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"482", + "unit":"NULL", + "description":"Enables per-index compression-related statistics in theINFORMATION_SCHEMA.INNODB_CMP_PER_INDEXtable. Because these statistics can be expensive to gatheronly enable this option on development test or slaveinstances during performance tuning related toInnoDBcompressed tables." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"innodb_commit_concurrency", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_commit_concurrency", + "vartype":"integer", + "max_value":"1000", + "scope":"{Global}", + "id":"483", + "unit":"NULL", + "description":"The number of threads thatcan commit at the sametime. A value of 0 (the default) permits any number oftransactions to commitsimultaneously.The value of innodb_commit_concurrencycannot be changed at runtime from zero to nonzero or viceversa. The value can be changed from one nonzero value toanother." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"50", + "name":"innodb_compression_pad_pct_max", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_compression_pad_pct_max", + "vartype":"integer", + "max_value":"75", + "scope":"{Global}", + "id":"486", + "unit":"NULL", + "description":"Specifies the maximum percentage that can be reserved as freespace within each compressedpage allowing room toreorganize the data and modification log within the page whena compressed table orindex is updated and the data might be recompressed. Onlyapplies wheninnodb_compression_failure_threshold_pctis set to a non-zero value and the rate ofcompressionfailures passes the cutoff point.For more information seeSection 14.7.6 Compression for OLTP Workloads." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"500", + "name":"innodb_concurrency_tickets", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_concurrency_tickets", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{Global}", + "id":"487", + "unit":"NULL", + "description":"Determines the number ofthreads that can enterInnoDB concurrently. A thread is placed ina queue when it tries to enter InnoDB ifthe number of threads has already reached the concurrencylimit. When a thread is permitted to enterInnoDB it is given a number of freetickets equal to the value ofinnodb_concurrency_ticketsand the thread can enter and leave InnoDBfreely until it has used up its tickets. After that point thethread again becomes subject to the concurrency check (andpossible queuing) the next time it tries to enterInnoDB. The default value is 5000 as ofMySQL 5.6.6 500 before that.With a small innodb_concurrency_ticketsvalue small transactions that only need to process a few rowscompete fairly with larger transactions that process manyrows. The disadvantage of a smallinnodb_concurrency_tickets value is thatlarge transactions must loop through the queue many timesbefore they can complete which extends the length of timerequired to complete their task.With a large innodb_concurrency_ticketsvalue large transactions spend less time waiting for aposition at the end of the queue (controlled byinnodb_thread_concurrency)and more time retrieving rows. Large transactions also requirefewer trips through the queue to complete their task. Thedisadvantage of a largeinnodb_concurrency_tickets value is thattoo many large transactions running at the same time canstarve smaller transactions by making them wait a longer timebefore executing.With a non-zeroinnodb_thread_concurrencyvalue you may need to adjust theinnodb_concurrency_tickets value up or downto find the optimal balance between larger and smallertransactions. The SHOW ENGINE INNODB STATUSreport shows the number of tickets remaining for an executingtransaction in its current pass through the queue. This datamay also be obtained from theTRX_CONCURRENCY_TICKETS column of theINFORMATION_SCHEMA.INNODB_TRXtable.For more information seeSection 14.4.6 Configuring Thread Concurrency for InnoDB." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ibdata1:10M:autoextend", + "name":"innodb_data_file_path", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_data_file_path", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"488", + "unit":"NULL", + "description":"The paths to individual InnoDBdata files and theirsizes. The full directory path to each data file is formed byconcatenatinginnodb_data_home_dir to eachpath specified here. The file sizes are specified KB MB or GB(1024MB) by appending KM or G to the sizevalue. If specifying data file size in kilobytes (KB) do soin multiples of 1024. Otherwise KB values are rounded off tonearest megabyte (MB) boundary. The sum of the sizes of thefiles must be at least slightly larger than 10MB. If you donot specify innodb_data_file_path thedefault behavior is to create a single auto-extending datafile slightly larger than 12MB namedibdata1. The size limit of individualfiles is determined by your operating system. You can set thefile size to more than 4GB on those operating systems thatsupport big files. You can alsouse raw disk partitions asdata files. For detailed information on configuringInnoDBtablespace files seeSection 14.4 InnoDB Configuration." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"innodb_data_home_dir", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_data_home_dir", + "vartype":"directory name", + "max_value":"NULL", + "scope":"{Global}", + "id":"489", + "unit":"NULL", + "description":"The common part of the directory path for allInnoDB datafiles in thesystemtablespace. This setting does not affect the locationof file-per-tabletablespaces wheninnodb_file_per_table isenabled. The default value is the MySQLdata directory. If you specify the valueas an empty string you can use absolute file paths ininnodb_data_file_path." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_disable_sort_file_cache", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_disable_sort_file_cache", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"490", + "unit":"NULL", + "description":"If enabled this variable disables the operating system filesystem cache for merge-sort temporary files. The effect is toopen such files with the equivalent ofO_DIRECT. This variable was added in MySQL5.6.4." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"ON", + "name":"innodb_doublewrite", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_doublewrite", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"491", + "unit":"NULL", + "description":"If this variable is enabled (the default)InnoDB stores all data twice first to thedoublewritebuffer then to the actualdata files. Thisvariable can be turned off with--skip-innodb_doublewrite for benchmarks orcases when top performance is needed rather than concern fordata integrity or possible failures." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1", + "name":"innodb_fast_shutdown", + "deprecated":"f", + "valid_vals":"0,1,2", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_fast_shutdown", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"492", + "unit":"NULL", + "description":"The InnoDBshutdown mode. If thevalue is 0 InnoDB does aslow shutdown afull purge and a changebuffer merge before shutting down. If the value is 1 (thedefault) InnoDB skips these operations atshutdown a process known as afast shutdown. Ifthe value is 2 InnoDB flushes its logs andshuts down cold as if MySQL had crashed; no committedtransactions are lost but thecrash recoveryoperation makes the next startup take longer.The slow shutdown can take minutes or even hours in extremecases where substantial amounts of data are still buffered.Use the slow shutdown technique before upgrading ordowngrading between MySQL major releases so that all datafiles are fully prepared in case the upgrade process updatesthe file format.Use innodb_fast_shutdown=2 in emergency ortroubleshooting situations to get the absolute fastestshutdown if data is at risk of corruption." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"innodb_fil_make_page_dirty_debug", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_fil_make_page_dirty_debug", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{Global}", + "id":"493", + "unit":"NULL", + "description":"By default settinginnodb_fil_make_page_dirty_debug to the IDof a tablespace immediately dirties the first page of thetablespace. Ifinnodb_saved_page_number_debugis set to a non-default value settinginnodb_fil_make_page_dirty_debug dirtiesthe specified page. Theinnodb_fil_make_page_dirty_debug option isonly available if debugging support is compiled in using theWITH_DEBUGCMake option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"2", + "name":"bgwriter_lru_multiplier", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Multiple of the average buffer usage to free per round.", + "vartype":"real", + "max_value":"10", + "scope":"{Global}", + "id":"1476", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"Antelope", + "name":"innodb_file_format", + "deprecated":"f", + "valid_vals":"Antelope,Barracuda", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_file_format", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"494", + "unit":"NULL", + "description":"The file format to usefor new InnoDB tables. CurrentlyAntelope and Barracudaare supported. This applies only for tables that have theirown tablespace so forit to have an effectinnodb_file_per_table must beenabled. The Barracudafile format is required for certain InnoDB features such astable compression.Be aware that ALTER TABLEoperations that recreate InnoDB tables(ALGORITHM=COPY) will use the currentinnodb_file_format setting (the conditionsoutlined above still apply)." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"innodb_file_format_check", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_file_format_check", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"495", + "unit":"NULL", + "description":"This variable can be set to 1 or 0 at server startup to enableor disable whether InnoDB checks thefile format tag in thesystemtablespace (for example Antelope orBarracuda). If the tag is checked and ishigher than that supported by the current version ofInnoDB an error occurs andInnoDB does not start. If the tag is nothigher InnoDB sets the value ofinnodb_file_format_max to thefile format tag." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"Antelope", + "name":"innodb_file_format_max", + "deprecated":"f", + "valid_vals":"Antelope,Barracuda", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_file_format_max", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"496", + "unit":"NULL", + "description":"At server startup InnoDB sets the value ofthis variable to the fileformat tag in thesystemtablespace (for example Antelope orBarracuda). If the server creates or opensa table with a higher file format it sets thevalue ofinnodb_file_format_max tothat format." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_file_per_table", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_file_per_table", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"497", + "unit":"NULL", + "description":"When innodb_file_per_table is enabled (thedefault in 5.6.6 and higher) InnoDB storesthe data and indexes for each newly created table in aseparate.ibdfile rather than in the system tablespace. The storagefor these InnoDB tables is reclaimed whenthe tables are dropped or truncated. This setting enablesseveral other InnoDB features such astable compression. SeeSection 14.5.4 InnoDB File-Per-Table Tablespaces for detailsabout such features as well as advantages and disadvantages ofusing file-per-table tablespaces.Be aware that enablinginnodb_file_per_table alsomeans that an ALTER TABLEoperation will move InnoDB table from thesystem tablespace to an individual .ibdfile in cases where ALTER TABLErecreates the table (ALGORITHM=COPY).When innodb_file_per_table is disabledInnoDB stores the data for all tables andindexes in the ibdatafiles that make up thesystemtablespace. This setting reduces the performanceoverhead of filesystem operations for operations such asDROP TABLE orTRUNCATE TABLE. It is mostappropriate for a server environment where entire storagedevices are devoted to MySQL data. Because the systemtablespace never shrinks and is shared across all databasesin an instance avoidloading huge amounts of temporary data on a space-constrainedsystem when innodb_file_per_table=OFF. Setup a separate instance in such cases so that you can drop theentire instance to reclaim the space.By default innodb_file_per_table isenabled as of MySQL 5.6.6 disabled before that. Considerdisabling it if backward compatibility with MySQL 5.5 or 5.1is a concern. This will prevent ALTERTABLE from movingInnoDB tables from the systemtablespace to individual .ibd files.innodb_file_per_table isdynamic and can be set ON orOFF using SET GLOBAL.You can also set this parameter in the MySQLconfigurationfile (my.cnf ormy.ini) but this requires shutting downand restarting the server.Dynamically changing the value of this parameter requires theSUPER privilege and immediately affects theoperation of all connections." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1", + "name":"innodb_flush_log_at_timeout", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_flush_log_at_timeout", + "vartype":"integer", + "max_value":"2700", + "scope":"{Global}", + "id":"498", + "unit":"NULL", + "description":"Write and flush the logs every Nseconds.innodb_flush_log_at_timeoutwas introduced in MySQL 5.6.6. It allows the timeout periodbetween flushes to be increased in order to reduce flushingand avoid impacting performance of binary log group commit.Prior to MySQL 5.6.6 flushing frequency was once per second.The default setting forinnodb_flush_log_at_timeoutis also once per second." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1", + "name":"innodb_flush_log_at_trx_commit", + "deprecated":"f", + "valid_vals":"0,1,2", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_flush_log_at_trx_commit", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"499", + "unit":"NULL", + "description":"Controls the balance between strictACID compliance forcommit operations andhigher performance that is possible when commit-related I/Ooperations are rearranged and done in batches. You can achievebetter performance by changing the default value but then youcan lose up to a second of transactions in a crash.For durability and consistency in a replication setup thatuses InnoDB with transactions:" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULLfsyncO_DSYNCO_DIRECT}", + "dangerous":"PARTIALLY", + "default_val":"NULL", + "name":"innodb_flush_method", + "deprecated":"f", + "valid_vals":"NULL,fsync,O_DSYNC,O_DIRECT,O_DIRECT_NO_FSYNC,littlesync,nosync", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_flush_method", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"500", + "unit":"NULL", + "description":"Defines the method used toflush data to theInnoDB datafiles and logfiles which can affect I/O throughput. This variableis only configurable on Unix and Linux systems.If innodb_flush_method=NULL on a Unix-likesystem the fsync option is used bydefault. If innodb_flush_method=NULL onWindows the async_unbuffered option isused by default.If innodb_flush_method=NULL on a Unix-likesystem the fdatasync option is used bydefault. If innodb_flush_method=NULL onWindows the async_unbuffered option isused by default.The innodb_flush_method options forUnix-like systems include:The innodb_flush_method options for Windowssystems include:How each settings affects performance depends on hardwareconfiguration and workload. Benchmark your particularconfiguration to decide which setting to use or whether tokeep the default setting. Examine theInnodb_data_fsyncs statusvariable to see the overall number offsync() calls for each setting. The mix ofread and write operations in your workload can affect how asetting performs. For example on a system with a hardwareRAID controller and battery-backed write cacheO_DIRECT can help to avoid double bufferingbetween the InnoDB buffer pool and theoperating system's file system cache. On some systems whereInnoDB data and log files are located on aSAN the default value or O_DSYNC might befaster for a read-heavy workload with mostlySELECT statements. Always test thisparameter with hardware and workload that reflect yourproduction environment. For general I/O tuning advice seeSection 8.5.8 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1", + "name":"innodb_flush_neighbors", + "deprecated":"f", + "valid_vals":"0,1,2", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_flush_neighbors", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"501", + "unit":"NULL", + "description":"Specifies whether flushing apage from the InnoDB bufferpool also flushes otherdirty pages in the sameextent.When the table data is stored on a traditionalHDD storage device flushingsuch neighbor pagesin one operation reduces I/O overhead (primarily for disk seekoperations) compared to flushing individual pages at differenttimes. For table data stored onSSD seek time is not asignificant factor and you can turn this setting off to spreadout the write operations. For general I/O tuning advice seeSection 8.5.8 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"8192", + "name":"block_size", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"8192", + "dynamic":"f", + "rank":"-1", + "summary":"Shows the size of a disk block.", + "vartype":"integer", + "max_value":"8192", + "scope":"{NA}", + "id":"1477", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"30", + "name":"innodb_flushing_avg_loops", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_flushing_avg_loops", + "vartype":"integer", + "max_value":"1000", + "scope":"{Global}", + "id":"502", + "unit":"NULL", + "description":"Number of iterations for which InnoDB keeps the previouslycalculated snapshot of the flushing state controlling howquickly adaptiveflushing responds to changingworkloads. Increasing thevalue makes the rate offlush operations changesmoothly and gradually as the workload changes. Decreasing thevalue makes adaptive flushing adjust quickly to workloadchanges which can cause spikes in flushing activity if theworkload increases and decreases suddenly." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_force_load_corrupted", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_force_load_corrupted", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"503", + "unit":"NULL", + "description":"Lets InnoDB load tables at startup that are marked ascorrupted. Use only during troubleshooting to recover datathat is otherwise inaccessible. When troubleshooting iscomplete turn this setting back off and restart the server." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"innodb_force_recovery", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_force_recovery", + "vartype":"integer", + "max_value":"6", + "scope":"{Global}", + "id":"504", + "unit":"NULL", + "description":"The crash recoverymode typically only changed in serious troubleshootingsituations. Possible values are from 0 to 6. For the meaningsof these values and important information aboutinnodb_force_recovery seeSection 14.19.2 Forcing InnoDB Recovery." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"innodb_ft_aux_table", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_ft_aux_table", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"505", + "unit":"NULL", + "description":"Specifies the qualified name of an InnoDBtable containing a FULLTEXT index. Thisvariable is intended for diagnostic purposes and can only beset at runtime. For example:Attempting to set this variable at startup will result in amysqld: option '--innodb-ft-aux-table'cannot take an argument error and startupwill abort. After you set this variable to a name in theformatdb_name/table_namethe INFORMATION_SCHEMA tablesINNODB_FT_INDEX_TABLEINNODB_FT_INDEX_CACHEINNODB_FT_CONFIGINNODB_FT_DELETED andINNODB_FT_BEING_DELETED will showinformation about the search index for the specified table." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"8000000", + "name":"innodb_ft_cache_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1600000", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_ft_cache_size", + "vartype":"integer", + "max_value":"80000000", + "scope":"{Global}", + "id":"506", + "unit":"NULL", + "description":"The memory allocated in bytes for theInnoDB FULLTEXT search index cache whichholds a parsed document in memory while creating anInnoDB FULLTEXT index.Index inserts and updates are only committed to disk when theinnodb_ft_cache_size size limit is reached.innodb_ft_cache_size defines the cache sizeon a per table basis. To set a global limit for all tablesseeinnodb_ft_total_cache_size." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"ON", + "name":"innodb_ft_enable_diag_print", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_ft_enable_diag_print", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"507", + "unit":"NULL", + "description":"Whether to enable additional full-text search (FTS) diagnosticoutput. This option is primarily intended for advanced FTSdebugging and will not be of interest to most users. Output isprinted to the error log and includes information such as:" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"ON", + "name":"innodb_ft_enable_stopword", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_ft_enable_stopword", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"508", + "unit":"NULL", + "description":"Specifies that a set ofstopwords is associatedwith an InnoDB FULLTEXTindex at the time the index is created. If theinnodb_ft_user_stopword_tableoption is set the stopwords are taken from that table. Elseif theinnodb_ft_server_stopword_tableoption is set the stopwords are taken from that table.Otherwise a built-in set of default stopwords is used." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"84", + "name":"innodb_ft_max_token_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"10", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_ft_max_token_size", + "vartype":"integer", + "max_value":"84", + "scope":"{Global}", + "id":"509", + "unit":"NULL", + "description":"Maximum character length of words that are stored in an InnoDBFULLTEXT index. Setting a limit on thisvalue reduces the size of the index thus speeding up queriesby omitting long keywords or arbitrary collections of lettersthat are not real words and are not likely to be search terms." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"3", + "name":"innodb_ft_min_token_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_ft_min_token_size", + "vartype":"integer", + "max_value":"16", + "scope":"{Global}", + "id":"510", + "unit":"NULL", + "description":"Minimum length of words that are stored in an InnoDBFULLTEXT index. Increasing this valuereduces the size of the index thus speeding up queries byomitting common word that are unlikely to be significant in asearch context such as the English words a andto. For content using a CJK (Chinese JapaneseKorean) character set specify a value of 1." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"2000", + "name":"innodb_ft_num_word_optimize", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_ft_num_word_optimize", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"511", + "unit":"NULL", + "description":"Number of words to process during eachOPTIMIZE TABLE operation on anInnoDB FULLTEXT index.Because a bulk insert or update operation to a tablecontaining a full-text search index could require substantialindex maintenance to incorporate all changes you might do aseries of OPTIMIZE TABLEstatements each picking up where the last left off." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"2000000000", + "name":"innodb_ft_result_cache_limit", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1000000", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_ft_result_cache_limit", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"512", + "unit":"NULL", + "description":"The InnoDB FULLTEXT search (FTS) queryresult cache limit (defined in bytes) per FTS query or perthread. Intermediate and final InnoDB FTSquery results are handled in memory. Useinnodb_ft_result_cache_limit to place asize limit on the InnoDB FTS query resultcache to avoid excessive memory consumption in case of verylarge InnoDB FTS query results (millions orhundreds of millions of rows for example). Memory isallocated as required when an FTS query is processed. If theresult cache size limit is reached an error is returnedindicating that the query exceeds the maximum allowed memory.As of MySQL 5.6.17 the maximum value ofinnodb_ft_result_cache_limit for allplatform types and platform bit sizes is 2**32-1. Bug #71554." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"NULL", + "name":"innodb_ft_server_stopword_table", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_ft_server_stopword_table", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"513", + "unit":"NULL", + "description":"This option is used to specify your ownInnoDB FULLTEXT indexstopword list for all InnoDB tables. Toconfigure your own stopword list for a specificInnoDB table useinnodb_ft_user_stopword_table.Set innodb_ft_server_stopword_table to thename of the table containing a list of stopwords in theformatdb_name/table_name.The stopword table must exist before you configureinnodb_ft_server_stopword_table.innodb_ft_enable_stopword must be enabledand innodb_ft_server_stopword_table optionmust be configured before you create theFULLTEXT index.The stopword table must be an InnoDB tablecontaining a single VARCHAR column namedvalue.For more information seeSection 12.9.4 Full-Text Stopwords." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"2", + "name":"innodb_ft_sort_pll_degree", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_ft_sort_pll_degree", + "vartype":"integer", + "max_value":"32", + "scope":"{Global}", + "id":"514", + "unit":"NULL", + "description":"Number of threads used in parallel to index and tokenize textin an InnoDB FULLTEXTindex when building asearch index. Seeinnodb_sort_buffer_size foradditional usage information." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"640000000", + "name":"innodb_ft_total_cache_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"32000000", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_ft_total_cache_size", + "vartype":"integer", + "max_value":"1600000000", + "scope":"{Global}", + "id":"515", + "unit":"NULL", + "description":"The total memory allocated in bytes for theInnoDB FULLTEXT searchindex cache for all tables. Creating numerous tables eachwith a full-text search index could consume a significantportion of available memory.innodb_ft_total_cache_sizedefines a global memory limit for all full-text search indexesto help avoid excessive memory consumption. If the globallimit is reached by an index operation a force sync istriggered." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"NULL", + "name":"innodb_ft_user_stopword_table", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_ft_user_stopword_table", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"516", + "unit":"NULL", + "description":"This option is used to specify your ownInnoDB FULLTEXT indexstopword list on a specific table. To configure your ownstopword list for all InnoDB tables useinnodb_ft_server_stopword_table.Set innodb_ft_user_stopword_table to thename of the table containing a list of stopwords in theformatdb_name/table_name.The stopword table must exist before you configureinnodb_ft_user_stopword_table.innodb_ft_enable_stopword must be enabledand innodb_ft_user_stopword_table must beconfigured before you create the FULLTEXTindex.The stopword table must be an InnoDB tablecontaining a single VARCHAR column namedvalue.For more information seeSection 12.9.4 Full-Text Stopwords." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"200", + "name":"innodb_io_capacity", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"100", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_io_capacity", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"517", + "unit":"NULL", + "description":"The innodb_io_capacityparameter sets an upper limit on the I/O activity performed bythe InnoDB background tasks such asflushing pages from thebuffer pool andmerging data from thechange buffer. Thedefault value is 200. For busy systems capable of higher I/Orates you can set a higher value at server startup to helpthe server handle the background maintenance work associatedwith a high rate of row changes.The innodb_io_capacity limitis a total limit for all buffer pool instances. When dirtypages are flushed theinnodb_io_capacity limit isdivided equally among buffer pool instances.For systems with individual 5400 RPM or 7200 RPM drives youmight lower the value to the former default of100This parameter should be set to approximately the number ofI/O operations that the system can perform per second.Ideally keep this setting as low as practical but not so lowthat these background activities fall behind. If the value istoo high data is removed from the buffer pool and insertbuffer too quickly to provide significant benefit from thecaching.The value represents an estimated proportion of the I/Ooperations per second (IOPS) available to older-generationdisk drives that could perform about 100 IOPS. The currentdefault of 200 reflects that modern storage devices arecapable of much higher I/O rates.In general you can increase the value as a function of thenumber of drives used for InnoDBI/O particularly fast drives capable of high numbers of IOPS.For example systems that use multiple disks or solid-statedisks for InnoDB are likely tobenefit from the ability to control this parameter.Although you can specify a very high number in practice suchlarge values have little if any benefit; for example a valueof one million would be considered very high.You can set the innodb_io_capacity value toany number 100 or greater to a maximum defined byinnodb_io_capacity_max. Thedefault value is 200. You can set the valueof this parameter in the MySQL option file(my.cnf or my.ini) orchange it dynamically with the SET GLOBALcommand which requires the SUPERprivilege.See Section 14.4.8 Configuring the InnoDB Master Thread I/O Rate formore guidelines about this option. For general informationabout InnoDB I/O performance seeSection 8.5.8 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"2000", + "name":"innodb_io_capacity_max", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"2000", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_io_capacity_max", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"518", + "unit":"NULL", + "description":"The limit up to which InnoDB is allowed toextend the innodb_io_capacitysetting in case of emergency. If you specify aninnodb_io_capacity setting atstartup and do not specify a value forinnodb_io_capacity_max theinnodb_io_capacity_max value defaults totwice the value ofinnodb_io_capacity with alower limit of 2000. 2000 is also the initial defaultinnodb_io_capacity_max configuration value.The innodb_io_capacity_maxsetting is a total limit for all buffer pool instances.For a brief period during MySQL 5.6 development this variablewas known as innodb_max_io_capacity. InMySQL 5.6.7 it was renamed toinnodb_io_capacity_max toemphasize its relationship to theinnodb_io_capacity option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_large_prefix", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_large_prefix", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"519", + "unit":"NULL", + "description":"Enable this option to allow index key prefixes longer than 767bytes (up to 3072 bytes) for InnoDB tablesthat use theDYNAMICandCOMPRESSEDrow formats. (Creating such tables also requires the optionvaluesinnodb_file_format=barracudaandinnodb_file_per_table=true.)See Section 14.6.7 Limits on InnoDB Tables for the relevantmaximums associated with index key prefixes under varioussettings.For tables using theREDUNDANTandCOMPACTrow formats this option does not affect the allowed keyprefix length." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"have_csv", + "deprecated":"f", + "valid_vals":"YES,NO,DISABLED", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"639", + "unit":"NULL", + "description":"YES if mysqld supportsCSV tables NO if not.This variable was removed in MySQL 5.6.1. UseSHOW ENGINES instead." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"innodb_limit_optimistic_insert_debug", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_limit_optimistic_insert_debug", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{Global}", + "id":"520", + "unit":"NULL", + "description":"Limits the number of records perB-tree page. A defaultvalue of 0 means that no limit is imposed. This option is onlyavailable if debugging support is compiled in using theWITH_DEBUGCMake option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"50", + "name":"innodb_lock_wait_timeout", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_lock_wait_timeout", + "vartype":"integer", + "max_value":"1073741824", + "scope":"{GlobalSession}", + "id":"521", + "unit":"NULL", + "description":"The length of time in seconds an InnoDBtransaction waits fora row lock before givingup. The default value is 50 seconds. A transaction that triesto access a row that is locked by anotherInnoDB transaction waits at most this manyseconds for write access to the row before issuing thefollowing error:When a lock wait timeout occurs the current statement isrolled back (not theentire transaction). To have the entire transaction roll backstart the server with the--innodb_rollback_on_timeoutoption. See also Section 14.19.4 InnoDB Error Handling.You might decrease this value for highly interactiveapplications or OLTP systemsto display user feedback quickly or put the update into aqueue for processing later. You might increase this value forlong-running back-end operations such as a transform step ina data warehouse that waits for other large insert or updateoperations to finish.innodb_lock_wait_timeout applies toInnoDB row locks only. A MySQLtable lock does nothappen inside InnoDB and this timeout doesnot apply to waits for table locks.The lock wait timeout value does not apply todeadlocks becauseInnoDB detects them immediately and rollsback one of the deadlocked transactions.innodb_lock_wait_timeout canbe set at runtime with the SET GLOBAL orSET SESSION statement. Changing theGLOBAL setting requires theSUPER privilege and affects the operationof all clients that subsequently connect. Any client canchange the SESSION setting forinnodb_lock_wait_timeoutwhich affects only that client." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_locks_unsafe_for_binlog", + "deprecated":"t", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_locks_unsafe_for_binlog", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"522", + "unit":"NULL", + "description":"This variable affects how InnoDB usesgap locking for searchesand index scans. As of MySQL 5.6.3innodb_locks_unsafe_for_binlog isdeprecated and will be removed in a future MySQL release.Normally InnoDB uses an algorithm callednext-key locking that combines index-row locking withgap locking.InnoDB performs row-level locking in such away that when it searches or scans a table index it setsshared or exclusive locks on the index records it encounters.Thus the row-level locks are actually index-record locks. Inaddition a next-key lock on an index record also affects thegap before that index record. That is anext-key lock is an index-record lock plus a gap lock on thegap preceding the index record. If one session has a shared orexclusive lock on record R in an indexanother session cannot insert a new index record in the gapimmediately before R in the index order.See Section 14.3.2 InnoDB Record Gap and Next-Key Locks.By default the value ofinnodb_locks_unsafe_for_binlog is 0(disabled) which means that gap locking is enabled:InnoDB uses next-key locks for searches andindex scans. To enable the variable set it to 1. This causesgap locking to be disabled: InnoDB usesonly index-record locks for searches and index scans.Enabling innodb_locks_unsafe_for_binlogdoes not disable the use of gap locking for foreign-keyconstraint checking or duplicate-key checking.The effect of enablinginnodb_locks_unsafe_for_binlog is similarto but not identical to setting the transaction isolationlevel to READ COMMITTED:READ COMMITTED thereforeoffers finer and more flexible control thaninnodb_locks_unsafe_for_binlog.For additional details about the effect of isolation level ongap locking see Section 13.3.6 SET TRANSACTION Syntax.Enabling innodb_locks_unsafe_for_binlog maycause phantom problems because other sessions can insert newrows into the gaps when gap locking is disabled. Suppose thatthere is an index on the id column of thechild table and that you want to read andlock all rows from the table having an identifier value largerthan 100 with the intention of updating some column in theselected rows later:The query scans the index starting from the first record whereid is greater than 100. If the locks set onthe index records in that range do not lock out inserts madein the gaps another session can insert a new row into thetable. Consequently if you were to execute the sameSELECT again within the sametransaction you would see a new row in the result setreturned by the query. This also means that if new items areadded to the database InnoDB does notguarantee serializability. Therefore ifinnodb_locks_unsafe_for_binlog is enabledInnoDB guarantees at most an isolationlevel of READ COMMITTED.(Conflict serializability is still guaranteed.) For additionalinformation about phantoms seeSection 14.3.3 Avoiding the Phantom Problem Using Next-Key Locking.Enabling innodb_locks_unsafe_for_binlog hasadditional effects:Consider the following example beginning with this table:In this case table has no indexes so searches and indexscans use the hidden clustered index for record locking (seeSection 14.2.5.2 Clustered and Secondary Indexes).Suppose that one client performs anUPDATE using these statements:Suppose also that a second client performs anUPDATE by executing thesestatements following those of the first client:As InnoDB executes eachUPDATE it first acquires anexclusive lock for each row and then determines whether tomodify it. If InnoDB does not modify therow and innodb_locks_unsafe_for_binlog isenabled it releases the lock. OtherwiseInnoDB retains the lock until the end ofthe transaction. This affects transaction processing asfollows.If innodb_locks_unsafe_for_binlog isdisabled the first UPDATEacquires x-locks and does not release any of them:The second UPDATE blocks assoon as it tries to acquire any locks (because first updatehas retained locks on all rows) and does not proceed untilthe first UPDATE commits orrolls back:If innodb_locks_unsafe_for_binlog isenabled the first UPDATEacquires x-locks and releases those for rows that it does notmodify:For the second UPDATEInnoDB does asemi-consistent read returning the latestcommitted version of each row to MySQL so that MySQL candetermine whether the row matches the WHEREcondition of the UPDATE:" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"8388608", + "name":"innodb_log_buffer_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"262144", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_log_buffer_size", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{Global}", + "id":"523", + "unit":"NULL", + "description":"The size in bytes of the buffer that InnoDBuses to write to the logfiles on disk. The default value is 8MB. A largelog buffer enableslarge transactions torun without a need to write the log to disk before thetransactions commit. Thusif you have transactions that update insert or delete manyrows making the log buffer larger saves disk I/O. For generalI/O tuning advice seeSection 8.5.8 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"ON", + "name":"innodb_log_compressed_pages", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_log_compressed_pages", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"524", + "unit":"NULL", + "description":"Specifies whether images ofre-compressedpages are stored inInnoDB redologs.This variable was added in MySQL 5.6.11." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"5242880", + "name":"innodb_log_file_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1048576", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_log_file_size", + "vartype":"integer", + "max_value":"4GB / innodb_log_files_in_group", + "scope":"{Global}", + "id":"525", + "unit":"NULL", + "description":"The size in bytes of each logfile in a loggroup. The combined size of log files(innodb_log_file_size *innodb_log_files_in_group)cannot exceed a maximum value that is slightly less than512GB. A pair of 255 GB log files for example would allowyou to approach the limit but not exceed it. The default valueis 48MB. Sensible values range from 1MB to1/N-th of the size of thebuffer pool whereN is the number of log files in thegroup. The larger the value the less checkpoint flushactivity is needed in the buffer pool saving disk I/O. Largerlog files also make crashrecovery slower although improvements to recoveryperformance in MySQL 5.5 and higher make the log file sizeless of a consideration. For general I/O tuning advice seeSection 8.5.8 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"2", + "name":"innodb_log_files_in_group", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"2", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_log_files_in_group", + "vartype":"integer", + "max_value":"100", + "scope":"{Global}", + "id":"526", + "unit":"NULL", + "description":"The number of log filesin the log group.InnoDB writes to the files in a circularfashion. The default (and recommended) value is 2. Thelocation of these files is specified byinnodb_log_group_home_dir.The combined size of log files(innodb_log_file_size *innodb_log_files_in_group) can be up to512GB." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"innodb_log_group_home_dir", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_log_group_home_dir", + "vartype":"directory name", + "max_value":"NULL", + "scope":"{Global}", + "id":"527", + "unit":"NULL", + "description":"The directory path to the InnoDBredo log files whosenumber is specified byinnodb_log_files_in_group. Ifyou do not specify any InnoDB logvariables the default is to create two files namedib_logfile0 andib_logfile1 in the MySQL data directory.Their size is given by the size of theinnodb_log_file_size systemvariable." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1024", + "name":"innodb_lru_scan_depth", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"100", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_lru_scan_depth", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"528", + "unit":"NULL", + "description":"A parameter that influences the algorithms and heuristics forthe flush operation for theInnoDBbuffer pool. Primarilyof interest to performance experts tuning I/O-intensiveworkloads. It specifies per buffer pool instance how fardown the buffer pool LRU list thepage_cleaner thread scans looking fordirty pages to flush.This is a background operation performed once a second. If youhave spare I/O capacity under a typical workload increase thevalue. If a write-intensive workload saturates your I/Ocapacity decrease the value especially if you have a largebuffer pool. For general I/O tuning advice seeSection 8.5.8 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"75", + "name":"innodb_max_dirty_pages_pct", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_max_dirty_pages_pct", + "vartype":"numeric", + "max_value":"99", + "scope":"{Global}", + "id":"529", + "unit":"NULL", + "description":"InnoDB tries toflush data from thebuffer pool so thatthe percentage of dirtypages does not exceed this value. Specify an integer inthe range from 0 to 99. The default value is 75.Theinnodb_max_dirty_pages_pctsetting establishes a target for flushing activity. It doesnot affect the rate of flushing. For information aboutmanaging the rate of flushing seeSection 14.4.3.2 Configuring the Rate of InnoDB Buffer Pool Flushing.For additional information about this variable seeSection 14.4.3.6 Tuning InnoDB Buffer Pool Flushing. For generalI/O tuning advice seeSection 8.5.8 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"innodb_max_dirty_pages_pct_lwm", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_max_dirty_pages_pct_lwm", + "vartype":"numeric", + "max_value":"99", + "scope":"{Global}", + "id":"530", + "unit":"NULL", + "description":"Low water mark representing percentage ofdirty pages wherepreflushing is enabled to control the dirty page ratio. Thedefault of 0 disables the pre-flushing behavior entirely. Foradditional information about this variable seeSection 14.4.3.6 Tuning InnoDB Buffer Pool Flushing." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"innodb_max_purge_lag", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_max_purge_lag", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{Global}", + "id":"531", + "unit":"NULL", + "description":"This variable controls how to delayINSERTUPDATE andDELETE operations whenpurge operations are lagging(see Section 14.2.2 InnoDB Multi-Versioning). The defaultvalue is 0 (no delays).The InnoDB transaction system maintains alist of transactions that have index records delete-marked byUPDATE orDELETE operations. The lengthof this list represents thepurge_lag value. Whenpurge_lag exceedsinnodb_max_purge_lag eachINSERTUPDATE andDELETE operation is delayed.To prevent excessive delays in extreme situations wherepurge_lag becomes huge you can puta cap on the amount of delay by setting theinnodb_max_purge_lag_delayconfiguration option. The delay is computed at the beginningof a purge batch.A typical setting for a problematic workload might be 1million assuming that transactions are small only 100 bytesin size and it is permissible to have 100MB of unpurgedInnoDB table rows.The lag value is displayed as the history list length in theTRANSACTIONS section of InnoDB Monitoroutput. For example if the output includes the followinglines the lag value is 20:For general I/O tuning advice seeSection 8.5.8 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"innodb_max_purge_lag_delay", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_max_purge_lag_delay", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"532", + "unit":"NULL", + "description":"Specifies the maximum delay in milliseconds for the delayimposed by theinnodb_max_purge_lagconfiguration option. Any non-zero value represents an upperlimit on the delay period computed from the formula based onthe value of innodb_max_purge_lag. Thedefault of zero means that there is no upper limit imposed onthe delay interval.For general I/O tuning advice seeSection 8.5.8 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1", + "name":"innodb_mirrored_log_groups", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"integer", + "max_value":"NULL", + "scope":"{NA}", + "id":"533", + "unit":"NULL", + "description":"Has no effect. This variable is deprecated as of MySQL 5.6.11and will be removed in a future MySQL release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"innodb_monitor_disable", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_monitor_disable", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"534", + "unit":"NULL", + "description":"Turns off one or morecounters in theINFORMATION_SCHEMA.INNODB_METRICStable. For usage information seeSection 21.29.19 The INFORMATION_SCHEMA INNODB_METRICS Table." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"innodb_monitor_enable", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_monitor_enable", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"535", + "unit":"NULL", + "description":"Turns on one or morecounters in theINFORMATION_SCHEMA.INNODB_METRICStable. For usage information seeSection 21.29.19 The INFORMATION_SCHEMA INNODB_METRICS Table." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"innodb_monitor_reset", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_monitor_reset", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"536", + "unit":"NULL", + "description":"Resets to zero the count value for one or morecounters in theINFORMATION_SCHEMA.INNODB_METRICStable. For usage information seeSection 21.29.19 The INFORMATION_SCHEMA INNODB_METRICS Table." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"innodb_monitor_reset_all", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_monitor_reset_all", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"537", + "unit":"NULL", + "description":"Resets all values (minimum maximum and so on) for one ormore counters in theINFORMATION_SCHEMA.INNODB_METRICStable. For usage information seeSection 21.29.19 The INFORMATION_SCHEMA INNODB_METRICS Table." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_numa_interleave", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_numa_interleave", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"538", + "unit":"NULL", + "description":"Enables the NUMA interleave memory policy for allocation ofthe InnoDB buffer pool. Wheninnodb_numa_interleave is enabled the NUMAmemory policy is set to MPOL_INTERLEAVE forthe mysqld process. After theInnoDB buffer pool is allocated the NUMAmemory policy is set back to MPOL_DEFAULT.For the innodb_numa_interleave option to beavailable MySQL must be compiled on a NUMA-enabled system." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"37", + "name":"innodb_old_blocks_pct", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"5", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_old_blocks_pct", + "vartype":"integer", + "max_value":"95", + "scope":"{Global}", + "id":"539", + "unit":"NULL", + "description":"Specifies the approximate percentage of theInnoDBbuffer pool used forthe old block sublist. Therange of values is 5 to 95. The default value is 37 (that is3/8 of the pool). Often used in combination withinnodb_old_blocks_time. SeeSection 14.4.3.3 Making the Buffer Pool Scan Resistant formore information. See Section 8.10.1 The InnoDB Buffer Pool forinformation about buffer pool management such as theLRU algorithm andeviction policies." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"20", + "name":"innodb_purge_batch_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_purge_batch_size", + "vartype":"integer", + "max_value":"5000", + "scope":"{Global}", + "id":"546", + "unit":"NULL", + "description":"The granularity of changes expressed in units ofredo log records thattrigger a purge operationflushing the changed bufferpool blocks to disk. This option is intended for tuningperformance in combination with the settinginnodb_purge_threads=nand typical users do not need to modify it." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"COLLATION", + "name":"collation_database", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for collation_database", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"601", + "unit":"NULL", + "description":"The collation used by the default database. The server setsthis variable whenever the default database changes. If thereis no default database the variable has the same value ascollation_server." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"innodb_old_blocks_time", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_old_blocks_time", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{Global}", + "id":"540", + "unit":"NULL", + "description":"Non-zero values protect against thebuffer pool beingfilled up by data that is referenced only for a brief periodsuch as during a fulltable scan. Increasing this value offers moreprotection against full table scans interfering with datacached in the buffer pool.Specifies how long in milliseconds (ms) a block inserted intothe old sublist must staythere after its first access before it can be moved to the newsublist. If the value is 0 a block inserted into the oldsublist moves immediately to the new sublist the first time itis accessed no matter how soon after insertion the accessoccurs. If the value is greater than 0 blocks remain in theold sublist until an access occurs at least that many ms afterthe first access. For example a value of 1000 causes blocksto stay in the old sublist for 1 second after the first accessbefore they become eligible to move to the new sublist.The default value is 1000 as of MySQL 5.6.6 0 before that.This variable is often used in combination withinnodb_old_blocks_pct. SeeSection 14.4.3.3 Making the Buffer Pool Scan Resistant formore information. See Section 8.10.1 The InnoDB Buffer Pool forinformation about buffer pool management such as theLRU algorithm andeviction policies." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"134217728", + "name":"innodb_online_alter_log_max_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"65536", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_online_alter_log_max_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"541", + "unit":"NULL", + "description":"Specifies an upper limit on the size of the temporary logfiles used during onlineDDL operations for InnoDB tables.There is one such log file for each index being created ortable being altered. This log file stores data insertedupdated or deleted in the table during the DDL operation. Thetemporary log file is extended when needed by the value ofinnodb_sort_buffer_size upto the maximum specified byinnodb_online_alter_log_max_size. If anytemporary log file exceeds the upper size limit theALTER TABLE operation fails andall uncommitted concurrent DML operations are rolled back.Thus a large value for this option allows more DML to happenduring an online DDL operation but also causes a longerperiod at the end of the DDL operation when the table islocked to apply the data from the log." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"300", + "name":"innodb_open_files", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"10", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_open_files", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{Global}", + "id":"542", + "unit":"NULL", + "description":"This variable is relevant only if you use multipleInnoDBtablespaces. Itspecifies the maximum number of.ibdfiles that MySQL can keep open at one time. The minimumvalue is 10. As of MySQL 5.6.6 the default value is 300 ifinnodb_file_per_table is notenabled and the higher of 300 andtable_open_cache otherwise.Before 5.6.6 the default value is 300.The file descriptors used for .ibd filesare for InnoDB tables only. They areindependent of those specified by the--open-files-limit serveroption and do not affect the operation of the table cache.For general I/O tuning advice seeSection 8.5.8 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_optimize_fulltext_only", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_optimize_fulltext_only", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"543", + "unit":"NULL", + "description":"Changes the way the OPTIMIZETABLE statement operates onInnoDB tables. Intended to be enabledtemporarily during maintenance operations forInnoDB tables withFULLTEXT indexes.By default OPTIMIZE TABLE reorganizes thedata in the clusteredindex of the table. When this option is enabledOPTIMIZE TABLE skips this reorganization ofthe table data and instead processes the newly addeddeleted and updated token data for aFULLTEXT index SeeSection 14.2.5.3 InnoDB FULLTEXT Indexes for more informationabout FULLTEXT indexes forInnoDB tables." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"16384", + "name":"innodb_page_size", + "deprecated":"f", + "valid_vals":"4k,8k,16k,4096,8192,16384", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_page_size", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"544", + "unit":"NULL", + "description":"Specifies the page sizefor all InnoDBtablespaces in a MySQLinstance. This value isset when the instance is created and remains constantafterwards. You can specify page size using the values16k (the default) 8kor 4k. Alternatively you can specify pagesize in bytes (40968192 16384).The default with the largest page size is appropriate for awide range of workloadsparticularly for queries involving table scans and DMLoperations involving bulk updates. Smaller page sizes might bemore efficient for OLTPworkloads involving many small writes where contention can bean issue when a single page contains many rows. Smaller pagesmight also be efficient withSSD storage devices whichtypically use small block sizes. Keeping theInnoDB page size close to the storagedevice block size minimizes the amount of unchanged data thatis rewritten to disk. For general I/O tuning advice seeSection 8.5.8 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_print_all_deadlocks", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_print_all_deadlocks", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"545", + "unit":"NULL", + "description":"When this option is enabled information about alldeadlocks inInnoDB user transactions is recorded in themysqld errorlog. Otherwise you see information about only the lastdeadlock using the SHOW ENGINE INNODBSTATUS command. An occasionalInnoDB deadlock is not necessarily anissue because InnoDB detects the conditionimmediately and rolls back one of the transactionsautomatically. You might use this option to troubleshoot whydeadlocks are happening if an application does not haveappropriate error-handling logic to detect the rollback andretry its operation. A large number of deadlocks mightindicate the need to restructure transactions that issueDML or SELECT ... FORUPDATE statements for multiple tables so that eachtransaction accesses the tables in the same order thusavoiding the deadlock condition." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"off", + "name":"bonjour", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"f", + "rank":"-1", + "summary":"Enables advertising the server via Bonjour.", + "vartype":"bool", + "max_value":"", + "scope":"{Global}", + "id":"1478", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"innodb_purge_threads", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_purge_threads", + "vartype":"integer", + "max_value":"1", + "scope":"{Global}", + "id":"547", + "unit":"NULL", + "description":"The number of background threads devoted to the InnoDBpurge operation. The newdefault and minimum value of 1 in MySQL 5.6.5 signifies thatthe purge operation is always performed by background threadsnever as part of the masterthread. Non-zero values runs the purge operation in oneor more background threads which can reduce internalcontention within InnoDB improving scalability. Increasingthe value to greater than 1 creates that many separate purgethreads which can improve efficiency on systems whereDML operations are performedon multiple tables. The maximum is 32." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_random_read_ahead", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_random_read_ahead", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"548", + "unit":"NULL", + "description":"Enables the randomread-ahead techniquefor optimizing InnoDB I/O. Randomread-ahead functionality was removed from the InnoDBPlugin (version 1.0.4) and was therefore notincluded in MySQL 5.5.0 when InnoDB Pluginbecame the built-in version ofInnoDB. Random read-ahead was reintroducedin MySQL 5.1.59 and 5.5.16 and higher along with theinnodb_random_read_ahead configurationoption which is disabled by default.See Section 14.4.3.1 Configuring InnoDB Buffer Pool Prefetching (Read-Ahead) fordetails about the performance considerations for the differenttypes of read-ahead requests. For general I/O tuning advicesee Section 8.5.8 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"56", + "name":"innodb_read_ahead_threshold", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_read_ahead_threshold", + "vartype":"integer", + "max_value":"64", + "scope":"{Global}", + "id":"549", + "unit":"NULL", + "description":"Controls the sensitivity of linearread-ahead thatInnoDB uses to prefetch pages into thebuffer pool. IfInnoDB reads at leastinnodb_read_ahead_threshold pagessequentially from an extent(64 pages) it initiates an asynchronous read for the entirefollowing extent. The permissible range of values is 0 to 64.As of MySQL 5.6.1 a value of 0 disables read-ahead. Prior to5.6.1 a value of 0 would trigger a read-ahead upon readingthe boundary page of a 64 page extent. For the default of 56InnoDB must read at least 56 pagessequentially from an extent to initiate an asynchronous readfor the following extent.Knowing how many pages are read through this read-aheadmechanism and how many of them are evicted from the bufferpool without ever being accessed can be useful to helpfine-tune theinnodb_read_ahead_thresholdparameter. As of MySQL 5.5SHOW ENGINEINNODB STATUS output displays counter informationfrom theInnodb_buffer_pool_read_aheadandInnodb_buffer_pool_read_ahead_evictedglobal status variables. These variables indicate the numberof pages brought into thebuffer pool byread-ahead requests and the number of such pagesevicted from the bufferpool without ever being accessed respectively. These countersprovide global values since the last server restart.SHOW ENGINE INNODB STATUS also shows therate at which the read-ahead pages are read in and the rate atwhich such pages are evicted without being accessed. Theper-second averages are based on the statistics collectedsince the last invocation of SHOW ENGINE INNODBSTATUS and are displayed in the BUFFER POOLAND MEMORY section of the output.See Section 14.4.3.1 Configuring InnoDB Buffer Pool Prefetching (Read-Ahead) for moreinformation. For general I/O tuning advice seeSection 8.5.8 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"4", + "name":"innodb_read_io_threads", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_read_io_threads", + "vartype":"integer", + "max_value":"64", + "scope":"{Global}", + "id":"550", + "unit":"NULL", + "description":"The number of I/O threads for read operations inInnoDB. The default value is 4. Itscounterpart for write threads isinnodb_write_io_threads. SeeSection 14.4.7 Configuring the Number of Background InnoDB I/O Threads formore information. For general I/O tuning advice seeSection 8.5.8 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_read_only", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_read_only", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"551", + "unit":"NULL", + "description":"Starts the server in read-only mode. For distributing databaseapplications or data sets on read-only media. Can also be usedin data warehouses to share the same data directory betweenmultiple instances. SeeSection 14.4.2 Configuring InnoDB for Read-Only Operation for usageinstructions." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"innodb_replication_delay", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_replication_delay", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{Global}", + "id":"552", + "unit":"NULL", + "description":"The replication thread delay (in ms) on a slave server ifinnodb_thread_concurrency isreached." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_rollback_on_timeout", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_rollback_on_timeout", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"553", + "unit":"NULL", + "description":"In MySQL 5.6 InnoDBrolls back only the laststatement on a transaction timeout by default. If--innodb_rollback_on_timeout isspecified a transaction timeout causesInnoDB to abort and roll back the entiretransaction (the same behavior as in MySQL 4.1)." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"128", + "name":"innodb_rollback_segments", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_rollback_segments", + "vartype":"integer", + "max_value":"128", + "scope":"{Global}", + "id":"554", + "unit":"NULL", + "description":"Defines how many of therollback segmentsin the systemtablespace are used for InnoDBtransactions. Thissetting while still valid is replaced byinnodb_undo_logs." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"innodb_saved_page_number_debug", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_saved_page_number_debug", + "vartype":"integer", + "max_value":"8388607", + "scope":"{Global}", + "id":"555", + "unit":"NULL", + "description":"Saves a page number. Setting theinnodb_fil_make_page_dirty_debugoption dirties the page defined byinnodb_saved_page_number_debug. Theinnodb_saved_page_number_debug option isonly available if debugging support is compiled in using theWITH_DEBUGCMake option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1048576", + "name":"innodb_sort_buffer_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"524288", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_sort_buffer_size", + "vartype":"integer", + "max_value":"67108864", + "scope":"{Global}", + "id":"556", + "unit":"NULL", + "description":"Specifies the size of sort buffers used for sorting dataduring creation of an InnoDB index. Thesize specified defines the amount of data filled in memory foran internal sort and written out to disk which can bereferred to as a run. During the merge phasepairs of buffers of the specified size are readin and merged. The larger the setting the fewerruns and merges there are which is importantto understand from a tuning perspective.This sort area is only used for merge sorts during indexcreation not during later index maintenance operations.Buffers are deallocated when index creation completes.The value of this option also controls the amount by which thetemporary log file is extended to record concurrent DMLduring online DDLoperations.Before this setting was made configurable the size washardcoded to 1048576 bytes (1MB) and that value remains thedefault.During an ALTER TABLE orCREATE TABLE statement thatcreates an index 3 buffers are allocated each with a sizedefined by this option. Additionally auxiliary pointers areallocated to rows in the sort buffer so that the sort can runon pointers (as opposed to moving rows during the sortoperation).For a typical sort operation a formula such as this can beused to estimate memory consumption:@@global.innodb_sort_buffer_size/dict_index_get_min_size(index)indicates the maximum tuples held. 2 *(@@global.innodb_sort_buffer_size/*dict_index_get_min_size(index)*/)* 8 /*64-bit size of *buf->tuples*/indicates auxiliary pointers allocated.For parallel sorts on a full-text index multiply by theinnodb_ft_sort_pll_degreesetting:" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"6", + "name":"innodb_spin_wait_delay", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_spin_wait_delay", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{Global}", + "id":"557", + "unit":"NULL", + "description":"The maximum delay between polls for aspin lock. The low-levelimplementation of this mechanism varies depending on thecombination of hardware and operating system so the delaydoes not correspond to a fixed time interval. The defaultvalue is 6. SeeSection 14.4.9 Configuring Spin Lock Polling formore information." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"ON", + "name":"innodb_stats_auto_recalc", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_stats_auto_recalc", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"558", + "unit":"NULL", + "description":"Causes InnoDB to automatically recalculatepersistentstatistics after the data in a table is changedsubstantially. The threshold value is currently 10% of therows in the table. This setting applies to tables created whenthe innodb_stats_persistentoption is enabled or where the clauseSTATS_PERSISTENT=1 is enabled by aCREATE TABLE orALTER TABLE statement. Theamount of data sampled to produce the statistics is controlledby theinnodb_stats_persistent_sample_pagesconfiguration option.For additional information aboutinnodb_stats_auto_recalc seeSection 14.4.11.1 Configuring Persistent Optimizer Statistics Parameters." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"nulls_equal", + "name":"innodb_stats_method", + "deprecated":"f", + "valid_vals":"nulls_equal,nulls_unequal,nulls_ignored", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_stats_method", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"559", + "unit":"NULL", + "description":"How the server treats NULL values whencollecting statisticsabout the distribution of index values forInnoDB tables. This variable has threepossible values nulls_equalnulls_unequal andnulls_ignored. Fornulls_equal all NULLindex values are considered equal and form a single valuegroup that has a size equal to the number ofNULL values. Fornulls_unequal NULLvalues are considered unequal and eachNULL forms a distinct value group of size1. For nulls_ignoredNULL values are ignored.The method that is used for generating table statisticsinfluences how the optimizer chooses indexes for queryexecution as described in Section 8.3.7 InnoDB and MyISAM Index Statistics Collection." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"ON", + "name":"innodb_stats_on_metadata", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_stats_on_metadata", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"560", + "unit":"NULL", + "description":"When this variable is enabled InnoDBupdates statistics whenmetadata statements such as SHOW TABLESTATUS or SHOW INDEXare run or when accessing theINFORMATION_SCHEMA.TABLES orINFORMATION_SCHEMA.STATISTICStables. (These updates are similar to what happens forANALYZE TABLE.) When disabledInnoDB does not update statistics duringthese operations. Leaving this setting disabled can improveaccess speed for schemas that have a large number of tables orindexes. It can also improve the stability ofexecutionplans for queries that involveInnoDB tables.To change the setting issue the statement SET GLOBALinnodb_stats_on_metadata=modewhere mode iseither ON or OFF (or1 or 0). Changing thissetting requires the SUPER privilege andimmediately affects the operation of all connections.This variable is disabled by default as of MySQL 5.6.6enabled before that." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"ON", + "name":"innodb_stats_persistent", + "deprecated":"f", + "valid_vals":"OFF,ON,0,1", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_stats_persistent", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"561", + "unit":"NULL", + "description":"Specifies whether InnoDB index statisticsare persisted to disk. Otherwise statistics may berecalculated frequently which can lead to variations inquery executionplans. This setting is stored with each table when thetable is created. You can setinnodb_stats_persistent at the global levelbefore creating a table or use theSTATS_PERSISTENT clause of theCREATE TABLE andALTER TABLE statements tooverride the system-wide setting and configure persistentstatistics for individual tables.For more information about this option seeSection 14.4.11.1 Configuring Persistent Optimizer Statistics Parameters." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"20", + "name":"innodb_stats_persistent_sample_pages", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_stats_persistent_sample_pages", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"562", + "unit":"NULL", + "description":"The number of index pages tosample when estimatingcardinality and otherstatistics for anindexed column such as those calculated byANALYZE TABLE. Increasing thevalue improves the accuracy of index statistics which canimprove the queryexecution plan at the expense of increased I/O duringthe execution of ANALYZE TABLEfor an InnoDB table. For additionalinformation see Section 14.4.11.1 Configuring Persistent Optimizer Statistics Parameters.This option only applies when theinnodb_stats_persistentsetting is turned on for a table; when that option is turnedoff for a table theinnodb_stats_transient_sample_pagessetting applies instead." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"8", + "name":"innodb_stats_sample_pages", + "deprecated":"t", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_stats_sample_pages", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"563", + "unit":"NULL", + "description":"Deprecated useinnodb_stats_transient_sample_pagesinstead." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"8", + "name":"innodb_stats_transient_sample_pages", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_stats_transient_sample_pages", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"564", + "unit":"NULL", + "description":"The number of index pages tosample when estimatingcardinality and otherstatistics for anindexed column such as those calculated byANALYZE TABLE. The defaultvalue is 8. Increasing the value improves the accuracy ofindex statistics which can improve thequery executionplan at the expense of increased I/O when opening anInnoDB table or recalculating statistics.For additional information seeSection 14.4.11.2 Configuring Non-Persistent Optimizer Statistics Parameters.This option only applies when theinnodb_stats_persistentsetting is turned off for a table; when this option is turnedon for a table theinnodb_stats_persistent_sample_pagessetting applies instead. Takes the place of theinnodb_stats_sample_pages option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_status_output", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_status_output", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"565", + "unit":"NULL", + "description":"Enables or disables periodic output for the standardInnoDB Monitor. Also used in combinationwithinnodb_status_output_locks toenable or disable periodic output for theInnoDB Lock Monitor. SeeSection 14.15 InnoDB Monitors for additional information." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_status_output_locks", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_status_output_locks", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"566", + "unit":"NULL", + "description":"Enables or disables the InnoDB LockMonitor. When enabled the InnoDB LockMonitor prints additional information about locks inSHOW ENGINE INNODB STATUS output and inperiodic output printed to the MySQL error log. Periodicoutput for the InnoDB Lock Monitor isprinted as part of the standard InnoDBMonitor output. The standard InnoDB Monitormust therefore be enabled for the InnoDBLock Monitor to print data to the MySQL error logperiodically. See Section 14.15 InnoDB Monitors for moreinformation." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_strict_mode", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_strict_mode", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"567", + "unit":"NULL", + "description":"When innodb_strict_mode isON InnoDB returnserrors rather than warnings for certain conditions. Thedefault value is OFF.Strict mode helpsguard against ignored typos and syntax errors in SQL or otherunintended consequences of various combinations of operationalmodes and SQL statements. Wheninnodb_strict_mode isON InnoDB raises errorconditions in certain cases rather than issuing a warning andprocessing the specified statement (perhaps with unintendedbehavior). This is analogous tosql_mode inMySQL which controls what SQL syntax MySQL accepts anddetermines whether it silently ignores errors or validatesinput syntax and data values.The innodb_strict_mode setting affects thehandling of syntax errors for CREATETABLE ALTER TABLEand CREATE INDEX statements.innodb_strict_mode also enables a recordsize check so that an INSERT orUPDATE never fails due to the record beingtoo large for the selected page size.Oracle recommends enablinginnodb_strict_mode when usingROW_FORMAT andKEY_BLOCK_SIZE clauses onCREATE TABLEALTER TABLE andCREATE INDEX statements. Wheninnodb_strict_mode isOFF InnoDB ignoresconflicting clauses and creates the table or index with onlya warning in the message log. The resulting table might havedifferent behavior than you intended such as having nocompression when you tried to create a compressed table. Wheninnodb_strict_mode isON such problems generate an immediateerror and the table or index is not created avoiding atroubleshooting session later.You can turn innodb_strict_modeON or OFF on the commandline when you start mysqld or in theconfigurationfile my.cnf ormy.ini. You can also enable or disableinnodb_strict_mode at runtime with thestatement SET [GLOBAL|SESSION]innodb_strict_mode=modewhere mode iseither ON or OFF.Changing the GLOBAL setting requires theSUPER privilege and affects the operationof all clients that subsequently connect. Any client canchange the SESSION setting forinnodb_strict_mode and the setting affectsonly that client." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"TRUE", + "name":"innodb_support_xa", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_support_xa", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"568", + "unit":"NULL", + "description":"Enables InnoDB support for two-phase commitin XA transactions causing anextra disk flush for transaction preparation. This setting isthe default. The XA mechanism is used internally and isessential for any server that has its binary log turned on andis accepting changes to its data from more than one thread. Ifyou turn it off transactions can be written to the binary login a different order from the one in which the live databaseis committing them. This can produce different data when thebinary log is replayed in disaster recovery or on areplication slave. Do not turn it off on a replication masterserver unless you have an unusual setup where only one threadis able to change data.For a server that is accepting data changes from only onethread it is safe and recommended to turn off this option toimprove performance for InnoDB tables. Forexample you can turn it off on replication slaves where onlythe replication SQL thread is changing data.You can also turn off this option if you do not need it forsafe binary logging or replication and you also do not use anexternal XA transaction manager." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1", + "name":"innodb_sync_array_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_sync_array_size", + "vartype":"integer", + "max_value":"1024", + "scope":"{Global}", + "id":"569", + "unit":"NULL", + "description":"Splits an internal data structure used to coordinate threadsfor higher concurrency in workloads with large numbers ofwaiting threads. This setting must be configured when theMySQL instance is starting up and cannot be changedafterward. Increasing this option value is recommended forworkloads that frequently produce a large number of waitingthreads typically greater than 768." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"30", + "name":"innodb_sync_spin_loops", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_sync_spin_loops", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{Global}", + "id":"570", + "unit":"NULL", + "description":"The number of times a thread waits for anInnoDB mutex to be freed before the threadis suspended. The default value is 30." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"TRUE", + "name":"innodb_table_locks", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_table_locks", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"571", + "unit":"NULL", + "description":"If autocommit = 0InnoDB honors LOCKTABLES; MySQL does not return from LOCKTABLES ... WRITE until all other threads havereleased all their locks to the table. The default value ofinnodb_table_locks is 1which means that LOCK TABLEScauses InnoDB to lock a table internally ifautocommit = 0.In MySQL 5.6innodb_table_locks = 0 has noeffect for tables locked explicitly withLOCK TABLES ...WRITE. It does have an effect for tables locked forread or write byLOCK TABLES ...WRITE implicitly (for example through triggers) orby LOCK TABLES... READ." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"avoid_temporal_upgrade", + "deprecated":"t", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for avoid_temporal_upgrade", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"586", + "unit":"NULL", + "description":"This variable controls whether ALTERTABLE implicitly upgrades temporal columns found tobe in pre-5.6.4 format (TIMEDATETIME andTIMESTAMP columns withoutsupport for fractional seconds precision). Upgrading suchcolumns requires a table rebuild which prevents any use offast alterations that might otherwise apply to the operationto be performed.This variable is disabled by default. Enabling it causesALTER TABLE not to rebuildtemporal columns and thereby be able to take advantage ofpossible fast alterations.This variable was added in MySQL 5.6.24. It is deprecated andwill be removed in a future MySQL release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"", + "name":"bonjour_name", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"f", + "rank":"-1", + "summary":"Sets the Bonjour service name.", + "vartype":"string", + "max_value":"", + "scope":"{Global}", + "id":"1479", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"NULL", + "name":"innodb_tmpdir", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_tmpdir", + "vartype":"directory name", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"572", + "unit":"NULL", + "description":"The innodb_tmpdir option is used to definean alternate directory for temporary sort files created duringonline ALTER TABLE operationsthat rebuild the table.Online ALTER TABLE operationsthat rebuild a table also create anintermediate table file in the samedirectory as the original table. Theinnodb_tmpdir option is not applicable tointermediate table files.A valid value is any directory path other than the MySQL datadirectory path. If the value is NULL (the default) temporaryfiles are created MySQL temporary directory(TMPDIR on Unix %TEMP%on Windows or the directory specified by the--tmpdir configurationoption). If an innodb_tmpdir directory isspecified existence of the directory and permissions are onlychecked when innodb_tmpdir is configuredusing aSETstatement. If a symlink is provided in a directory string thesymlink is resolved and stored as an absolute path. The pathshould not exceed 512 bytes. An onlineALTER TABLE operation reportsan error if innodb_tmpdir is set to aninvalid directory. innodb_tmpdir overridesthe MySQL tmpdir setting butonly for online ALTER TABLEoperations.The FILE privilege is required to configureinnodb_tmpdir.The innodb_tmpdir option was introduced tohelp avoid overflowing a temporary file directory located on atmpfs file system. Such overflows couldoccur as a result of large temporary sort files created duringonline ALTER TABLE operationsthat rebuild the table.In replication environments only consider replicating aninnodb_tmpdir setting if all servers havethe same operating system environment. Otherwise replicatingan innodb_tmpdir setting could result in areplication failure when running onlineALTER TABLE operations thatrebuild the table. If server operating environments differ itis recommended that you configureinnodb_tmpdir on each server individually.For related information seeWhere InnoDB Stores Temporary Files." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"innodb_thread_concurrency", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_thread_concurrency", + "vartype":"integer", + "max_value":"1000", + "scope":"{Global}", + "id":"573", + "unit":"NULL", + "description":"InnoDB tries to keep the number ofoperating system threads concurrently insideInnoDB less than or equal to the limitgiven by this variable (InnoDB usesoperating system threads to process user transactions). Oncethe number of threads reaches this limit additional threadsare placed into a wait state within a First In FirstOut (FIFO) queue for execution. Threads waiting forlocks are not counted in the number of concurrently executingthreads.The range of this variable is 0 to 1000. A value of 0 (thedefault) is interpreted as infinite concurrency (noconcurrency checking). Disabling thread concurrency checkingenables InnoDB to create as many threads asit needs. A value of 0 also disables the queriesinside InnoDB and queries in queuecounters in the ROW OPERATIONSsection of SHOW ENGINE INNODB STATUSoutput.Consider setting this variable if your MySQL instance sharesCPU resources with other applications or if your workload ornumber of concurrent users is growing. The correct settingdepends on workload computing environment and the version ofMySQL that you are running. You will need to test a range ofvalues to determine the setting that provides the bestperformance. innodb_thread_concurrency is adynamic variable which allows you to experiment withdifferent settings on a live test system. If a particularsetting performs poorly you can quickly setinnodb_thread_concurrency back to 0.Use the following guidelines to help find and maintain anappropriate setting:For related information seeSection 14.4.6 Configuring Thread Concurrency for InnoDB." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"10000", + "name":"innodb_thread_sleep_delay", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_thread_sleep_delay", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"574", + "unit":"NULL", + "description":"How long InnoDB threads sleep beforejoining the InnoDB queue in microseconds.The default value is 10000. A value of 0 disables sleep. InMySQL 5.6.3 and higher you can set the configuration optioninnodb_adaptive_max_sleep_delayto the highest value you would allow forinnodb_thread_sleep_delay and InnoDBautomatically adjustsinnodb_thread_sleep_delay up or downdepending on the current thread-scheduling activity. Thisdynamic adjustment helps the thread scheduling mechanism towork smoothly during times when the system is lightly loadedand when it is operating near full capacity.For more information seeSection 14.4.6 Configuring Thread Concurrency for InnoDB." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"innodb_trx_purge_view_update_only_debug", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_trx_purge_view_update_only_debug", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"575", + "unit":"NULL", + "description":"Pauses purging of delete-marked records while allowing thepurge view to be updated. This option artificially creates asituation in which the purge view is updated but purges havenot yet been performed. This option is only available ifdebugging support is compiled in using theWITH_DEBUGCMake option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"innodb_trx_rseg_n_slots_debug", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_trx_rseg_n_slots_debug", + "vartype":"integer", + "max_value":"1024", + "scope":"{Global}", + "id":"576", + "unit":"NULL", + "description":"Sets a debug flag that limitsTRX_RSEG_N_SLOTS to a given value for thetrx_rsegf_undo_find_free function whichlooks for a free slot for an undo log segment. This option isonly available if debugging support is compiled in using theWITH_DEBUGCMake option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":".", + "name":"innodb_undo_directory", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_undo_directory", + "vartype":"directory name", + "max_value":"NULL", + "scope":"{Global}", + "id":"577", + "unit":"NULL", + "description":"The relative or absolute directory path whereInnoDB creates separate tablespaces for theundo logs. Typically used to place those logs on a differentstorage device. Used in conjunction withinnodb_undo_logs andinnodb_undo_tablespaceswhich determine the disk layout of the undo logs outside thesystemtablespace. The default value of. represents the samedirectory where InnoDB creates its otherlog files by default.For more information about configuring separate tablespacesfor undo logs see Section 14.5.7 Storing InnoDB Undo Logs in Separate Tablespaces." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"128", + "name":"innodb_undo_logs", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_undo_logs", + "vartype":"integer", + "max_value":"128", + "scope":"{Global}", + "id":"578", + "unit":"NULL", + "description":"Defines the number of undo logs (otherwise referred to asrollbacksegments) used by InnoDB fordata-modifying transactions that generate undo records. Eachundo log can host up to a maximum of 1024 transactions.This setting is appropriate for tuning performance if youobserve mutex contention related to the undo logs. Theinnodb_undo_logs optionreplacesinnodb_rollback_segments. Forthe total number of available undo logs rather than thenumber of active ones see theInnodb_available_undo_logsstatus variable.Although you can increase or decrease the number of undo logsused by InnoDB the number of undo logsphysically present in the system never decreases. Thus youmight start with a low value for this parameter and graduallyincrease it to avoid allocating undo logs that are notrequired. If innodb_undo_logsis not set it defaults to the maximum value of 128.For more information about undo logs seeSection 14.2.2 InnoDB Multi-Versioning. For informationabout configuring separate tablespaces for undo logs seeSection 14.5.7 Storing InnoDB Undo Logs in Separate Tablespaces." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"latin1", + "name":"character_set_server", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for character-set-server", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"597", + "unit":"NULL", + "description":"The server's default character set." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"innodb_undo_tablespaces", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_undo_tablespaces", + "vartype":"integer", + "max_value":"126", + "scope":"{Global}", + "id":"579", + "unit":"NULL", + "description":"The number oftablespace files thatundo logs are dividedbetween when you use a non-zeroinnodb_undo_logs setting. Bydefault all undo logs are part of thesystemtablespace and the system tablespace always containsone undo tablespace in addition to those configured byinnodb_undo_tablespaces.Because undo logs can become large during long-runningtransactions having undo logs in multiple tablespaces reducesthe maximum size of any one tablespace. The undo tablespacefiles are created in the location defined byinnodb_undo_directory withnames in the form ofundoN whereN is a sequential series ofintegers (including leading zeros). The default size of anundo tablespace file is 10M. The number ofinnodb_undo_tablespaces mustbe set prior to initializing InnoDB.Attempting to restart InnoDB with a greaternumber of undo tablespaces than you specified when you firstcreated the MySQL instance will result in a failed start andan error stating that InnoDB did not findthe expected number of undo tablespaces.For more information about configuring separate tablespacesfor undo logs see Section 14.5.7 Storing InnoDB Undo Logs in Separate Tablespaces." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"ON", + "name":"innodb_use_native_aio", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_use_native_aio", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"580", + "unit":"NULL", + "description":"Specifies whether to use the Linux asynchronous I/O subsystem.This variable applies to Linux systems only and cannot bechanged while the server is running. Normally you do not needto touch this option because it is enabled by default.As of MySQL 5.5 theasynchronous I/Ocapability that InnoDB has on Windowssystems is available on Linux systems. (Other Unix-likesystems continue to use synchronous I/O calls.) This featureimproves the scalability of heavily I/O-bound systems whichtypically show many pending reads/writes in the output of thecommand SHOW ENGINE INNODB STATUSG.Running with a large number of InnoDB I/Othreads and especially running multiple such instances on thesame server machine can exceed capacity limits on Linuxsystems. In this case you may receive the following error:You can typically address this error by writing a higher limitto /proc/sys/fs/aio-max-nr.However if a problem with the asynchronous I/O subsystem inthe OS prevents InnoDB from starting youcan start the server withinnodb_use_native_aio=0disabled (useinnodb_use_native_aio=0 inthe option file). This option may also be turned offautomatically during startup if InnoDBdetects a potential problem such as a combination oftmpdir location tmpfsfilesystem and Linux kernel that does not support AIO ontmpfs." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"ON", + "name":"innodb_use_sys_malloc", + "deprecated":"t", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_use_sys_malloc", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"581", + "unit":"NULL", + "description":"Whether InnoDB uses the operating systemmemory allocator (ON) or its own(OFF). The default value isON. SeeSection 14.4.4 Configuring the Memory Allocator for InnoDB for moreinformation.As of MySQL 5.6.3innodb_use_sys_malloc isdeprecated and will be removed in a future MySQL release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"innodb_version", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"582", + "unit":"NULL", + "description":"The InnoDB version number. Starting in5.6.11 the separate numbering for InnoDBis discontinued and this value is the same as for theversion variable." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"4", + "name":"innodb_write_io_threads", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_write_io_threads", + "vartype":"integer", + "max_value":"64", + "scope":"{Global}", + "id":"583", + "unit":"NULL", + "description":"The number of I/O threads for write operations inInnoDB. The default value is 4. Itscounterpart for read threads isinnodb_read_io_threads. SeeSection 14.4.7 Configuring the Number of Background InnoDB I/O Threads formore information. For general I/O tuning advice seeSection 8.5.8 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"autocommit", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for autocommit", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"584", + "unit":"NULL", + "description":"The autocommit mode. If set to 1 all changes to a table takeeffect immediately. If set to 0 you must useCOMMIT to accept a transactionor ROLLBACKto cancel it. If autocommitis 0 and you change it to 1 MySQL performs an automaticCOMMIT of any open transaction.Another way to begin a transaction is to use aSTARTTRANSACTION orBEGINstatement. See Section 13.3.1 START TRANSACTION COMMIT and ROLLBACK Syntax.By default client connections begin withautocommit set to 1. To causeclients to begin with a default of 0 set the globalautocommit value by startingthe server with the--autocommit=0 option. To setthe variable using an option file include these lines:" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"TRUE", + "name":"automatic_sp_privileges", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for automatic_sp_privileges", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"585", + "unit":"NULL", + "description":"When this variable has a value of 1 (the default) the serverautomatically grants theEXECUTE andALTER ROUTINE privileges to thecreator of a stored routine if the user cannot alreadyexecute and alter or drop the routine. (TheALTER ROUTINE privilege isrequired to drop the routine.) The server also automaticallydrops those privileges from the creator when the routine isdropped. Ifautomatic_sp_privileges is 0the server does not automatically add or drop theseprivileges.The creator of a routine is the account used to execute theCREATE statement for it. This might not bethe same as the account named as theDEFINER in the routine definition.See also Section 20.2.2 Stored Routines and MySQL Privileges." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"utf8", + "name":"character_set_system", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for character_set_system", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"598", + "unit":"NULL", + "description":"The character set used by the server for storing identifiers.The value is always utf8." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"50", + "name":"back_log", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"f", + "rank":"-1", + "summary":"Options for back_log", + "vartype":"integer", + "max_value":"65535", + "scope":"{Global}", + "id":"587", + "unit":"NULL", + "description":"The number of outstanding connection requests MySQL can have.This comes into play when the main MySQL thread gets very manyconnection requests in a very short time. It then takes sometime (although very little) for the main thread to check theconnection and start a new thread. Theback_log value indicates howmany requests can be stacked during this short time beforeMySQL momentarily stops answering new requests. You need toincrease this only if you expect a large number of connectionsin a short period of time.In other words this value is the size of the listen queue forincoming TCP/IP connections. Your operating system has its ownlimit on the size of this queue. The manual page for the Unixlisten() system call should have moredetails. Check your OS documentation for the maximum value forthis variable. back_logcannot be set higher than your operating system limit.As of MySQL 5.6.6 the default value is based on the followingformula capped to a limit of 900:Before 5.6.6 the default is 50." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"big_tables", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for big-tables", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"588", + "unit":"NULL", + "description":"If set to 1 all temporary tables are stored on disk ratherthan in memory. This is a little slower but the errorThe table tbl_name isfull does not occur forSELECT operations that requirea large temporary table. The default value for a newconnection is 0 (use in-memory temporary tables). Normallyyou should never need to set this variable because in-memorytables are automatically converted to disk-based tables asrequired." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0.0.0.0", + "name":"bind_address", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for bind-address", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"589", + "unit":"NULL", + "description":"The value of the --bind-addressoption. This variable was added in MySQL 5.6.1." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"aes-128-ecb", + "name":"block_encryption_mode", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for block_encryption_mode", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"590", + "unit":"NULL", + "description":"This variable controls the block encryption mode forblock-based algorithms such as AES. It affects encryption forAES_ENCRYPT() andAES_DECRYPT().block_encryption_mode takes avalue inaes-keylen-modeformat where keylen is the keylength in bits and mode is theencryption mode. The value is not case sensitive. Permittedkeylen values are 128192 and256. Permitted encryption modes depend on whether MySQL wascompiled using OpenSSL or yaSSL:For example this statement causes the AES encryptionfunctions to use a key length of 256 bits and the CBC mode:An error occurs for attempts to setblock_encryption_mode to avalue containing an unsupported key length or a mode that theSSL library does not support.This variable was added in MySQL 5.6.17." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"8388608", + "name":"bulk_insert_buffer_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for bulk_insert_buffer_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{GlobalSession}", + "id":"591", + "unit":"NULL", + "description":"MyISAM uses a special tree-like cache tomake bulk inserts faster forINSERT ...SELECT INSERT ... VALUES (...) (...)... andLOAD DATAINFILE when adding data to nonempty tables. Thisvariable limits the size of the cache tree in bytes perthread. Setting it to 0 disables this optimization. Thedefault value is 8MB." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"CHARSET", + "name":"character_set_client", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for character_set_client", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"592", + "unit":"NULL", + "description":"The character set for statements that arrive from the client.The session value of this variable is set using the characterset requested by the client when the client connects to theserver. (Many clients support a--default-character-set option to enable thischaracter set to be specified explicitly. See alsoSection 10.1.5 Connection Character Sets and Collations.) The global value of thevariable is used to set the session value in cases when theclient-requested value is unknown or not available or theserver is configured to ignore client requests:ucs2 utf16utf16le and utf32cannot be used as a client character set which means thatthey also do not work for SET NAMES orSET CHARACTER SET." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"CHARSET", + "name":"character_set_connection", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for character_set_connection", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"593", + "unit":"NULL", + "description":"The character set used for literals that do not have acharacter set introducer and for number-to-string conversion." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"CHARSET", + "name":"character_set_database", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for character_set_database", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"594", + "unit":"NULL", + "description":"The character set used by the default database. The serversets this variable whenever the default database changes. Ifthere is no default database the variable has the same valueas character_set_server." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"binary", + "name":"character_set_filesystem", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for character-set-filesystem", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"595", + "unit":"NULL", + "description":"The file system character set. This variable is used tointerpret string literals that refer to file names such as inthe LOAD DATAINFILE andSELECT ... INTOOUTFILE statements and theLOAD_FILE() function. Such filenames are converted fromcharacter_set_client tocharacter_set_filesystembefore the file opening attempt occurs. The default value isbinary which means that no conversionoccurs. For systems on which multibyte file names arepermitted a different value may be more appropriate. Forexample if the system represents file names using UTF-8 setcharacter_set_filesystem to'utf8'." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"CHARSET", + "name":"character_set_results", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for character_set_results", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"596", + "unit":"NULL", + "description":"The character set used for returning query results such asresult sets or error messages to the client." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"NO_CHAIN", + "name":"completion_type", + "deprecated":"f", + "valid_vals":"NO_CHAIN,CHAIN,RELEASE,0,1,2", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for completion_type", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"603", + "unit":"NULL", + "description":"The transaction completion type. This variable can take thevalues shown in the following table. The variable can beassigned using either the name values or corresponding integervalues.completion_type affectstransactions that begin withSTARTTRANSACTION orBEGIN andend with COMMIT orROLLBACK. Itdoes not apply to implicit commits resulting from execution ofthe statements listed in Section 13.3.3 Statements That Cause an Implicit Commit. Italso does not apply forXACOMMITXAROLLBACK or whenautocommit=1." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"AUTO", + "name":"concurrent_insert", + "deprecated":"f", + "valid_vals":"NEVER,AUTO,ALWAYS,0,1,2", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for concurrent_insert", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"604", + "unit":"NULL", + "description":"If AUTO (the default) MySQL permitsINSERT andSELECT statements to runconcurrently for MyISAM tables that have nofree blocks in the middle of the data file. If you startmysqld with--skip-newthis variable is set to NEVER.This variable can take the values shown in the followingtable. The variable can be assigned using either the namevalues or corresponding integer values.See also Section 8.11.3 Concurrent Inserts." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"10", + "name":"connect_timeout", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"2", + "dynamic":"t", + "rank":"-1", + "summary":"Options for connect_timeout", + "vartype":"integer", + "max_value":"31536000", + "scope":"{Global}", + "id":"605", + "unit":"NULL", + "description":"The number of seconds that the mysqldserver waits for a connect packet before responding withBad handshake. The default value is 10seconds.Increasing theconnect_timeout value mighthelp if clients frequently encounter errors of the formLost connection to MySQL server at'XXX' system error:errno." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"core_file", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for core_file", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"606", + "unit":"NULL", + "description":"Whether to write a core file if the server crashes. Thisvariable is set by the--core-file option. It wasadded in MySQL 5.6.2." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"%Y-%m-%d", + "name":"date_format", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"607", + "unit":"NULL", + "description":"This variable is unused. It is deprecated as of MySQL 5.6.7and will be removed in a future MySQL release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"%Y-%m-%d %H:%i:%s", + "name":"datetime_format", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"608", + "unit":"NULL", + "description":"This variable is unused. It is deprecated as of MySQL 5.6.7and will be removed in a future MySQL release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"debug_sync", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for debug_sync", + "vartype":"string", + "max_value":"NULL", + "scope":"{Session}", + "id":"609", + "unit":"NULL", + "description":"This variable is the user interface to the Debug Syncfacility. Use of Debug Sync requires that MySQL be configuredwith the -DENABLE_DEBUG_SYNC=1CMake option (seeSection 2.9.4 MySQL Source-Configuration Options). If Debug Syncis not compiled in this system variable is not available.The global variable value is read only and indicates whetherthe facility is enabled. By default Debug Sync is disabledand the value of debug_syncis OFF. If the server is started with--debug-sync-timeout=Nwhere N is a timeout value greaterthan 0 Debug Sync is enabled and the value ofdebug_sync is ON -current signal followed by the signal name. AlsoN becomes the default timeout forindividual synchronization points.The session value can be read by any user and will have thesame value as the global variable. The session value can beset by users that have theSUPER privilege to controlsynchronization points.For a description of the Debug Sync facility and how to usesynchronization points seeMySQLInternals: Test Synchronization." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"InnoDB", + "name":"default_storage_engine", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for default-storage-engine", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"610", + "unit":"NULL", + "description":"The default storage engine. As of MySQL 5.6.3 this variablesets the storage engine for permanent tables only. To set thestorage engine for TEMPORARY tables setthedefault_tmp_storage_enginesystem variable.To see which storage engines are available and enabled usethe SHOW ENGINES statement orquery the INFORMATION_SCHEMAENGINES table.default_storage_engine shouldbe used in preference tostorage_engine which isdeprecated.If you disable the default storage engine at server startupyou must set the default engine for both permanent andTEMPORARY tables to a different engine orthe server will not start." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"InnoDB", + "name":"default_tmp_storage_engine", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for default_tmp_storage_engine", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"611", + "unit":"NULL", + "description":"The default storage engine for TEMPORARYtables (created withCREATE TEMPORARYTABLE). To set the storage engine for permanenttables set thedefault_storage_engine systemvariable.If you disable the default storage engine at server startupyou must set the default engine for both permanent andTEMPORARY tables to a different engine orthe server will not start.default_tmp_storage_enginewas added in MySQL 5.6.3." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"default_week_format", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for default_week_format", + "vartype":"integer", + "max_value":"7", + "scope":"{GlobalSession}", + "id":"612", + "unit":"NULL", + "description":"The default mode value to use for theWEEK() function. SeeSection 12.7 Date and Time Functions." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"have_dynamic_loading", + "deprecated":"f", + "valid_vals":"YES,NO,DISABLED", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"640", + "unit":"NULL", + "description":"YES if mysqld supportsdynamic loading of plugins NO if not." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"have_geometry", + "deprecated":"f", + "valid_vals":"YES,NO,DISABLED", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"641", + "unit":"NULL", + "description":"YES if the server supports spatial datatypes NO if not." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"ON", + "name":"delay_key_write", + "deprecated":"f", + "valid_vals":"ON,OFF,ALL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for delay-key-write", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"613", + "unit":"NULL", + "description":"This option applies only to MyISAM tables.It can have one of the following values to affect handling ofthe DELAY_KEY_WRITE table option that canbe used in CREATE TABLEstatements.If DELAY_KEY_WRITE is enabled for a tablethe key buffer is not flushed for the table on every indexupdate but only when the table is closed. This speeds upwrites on keys a lot but if you use this feature you shouldadd automatic checking of all MyISAM tablesby starting the server with the--myisam-recover-options option(for example--myisam-recover-options=BACKUPFORCE).See Section 5.1.3 Server Command Options andSection 15.2.1 MyISAM Startup Options." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"100", + "name":"delayed_insert_limit", + "deprecated":"t", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for delayed_insert_limit", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"614", + "unit":"NULL", + "description":"After insertingdelayed_insert_limit delayedrows into a nontransactional table theINSERT DELAYED handler threadchecks whether there are anySELECT statements pending. Ifso it permits them to execute before continuing to insertdelayed rows.As of MySQL 5.6.7 this system variable is deprecated (becauseDELAYED inserts are deprecated) and willbe removed in a future release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"300", + "name":"delayed_insert_timeout", + "deprecated":"t", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for delayed_insert_timeout", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"615", + "unit":"NULL", + "description":"How many seconds an INSERTDELAYED handler thread should wait forINSERT statements beforeterminating.As of MySQL 5.6.7 this system variable is deprecated (becauseDELAYED inserts are deprecated) and willbe removed in a future release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1000", + "name":"delayed_queue_size", + "deprecated":"t", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for delayed_queue_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"616", + "unit":"NULL", + "description":"This is a per-table limit on the number of rows to queue whenhandling INSERT DELAYEDstatements for nontransactional tables. If the queue becomesfull any client that issues an INSERTDELAYED statement waits until there is room in thequeue again.As of MySQL 5.6.7 this system variable is deprecated (becauseDELAYED inserts are deprecated) and willbe removed in a future release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"disconnect_on_expired_password", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for disconnect_on_expired_password", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Session}", + "id":"617", + "unit":"NULL", + "description":"This variable controls how the server handles clients withexpired passwords:For more information about the interaction of client andserver settings relating to expired-password handling seeSection 6.3.6 Password Expiration and Sandbox Mode.This variable was added in MySQL 5.6.10." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"4", + "name":"div_precision_increment", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for div_precision_increment", + "vartype":"integer", + "max_value":"30", + "scope":"{GlobalSession}", + "id":"618", + "unit":"NULL", + "description":"This variable indicates the number of digits by which toincrease the scale of the result of division operationsperformed with the/ operator.The default value is 4. The minimum and maximum values are 0and 30 respectively. The following example illustrates theeffect of increasing the default value." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"engine_condition_pushdown", + "deprecated":"t", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for engine-condition-pushdown", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"619", + "unit":"NULL", + "description":"This variable was removed in MySQL 5.6.1. Use theengine_condition_pushdown flag of theoptimizer_switch variableinstead. See Section 8.9.2 Controlling Switchable Optimizations." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"end_markers_in_json", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for end_markers_in_json", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"620", + "unit":"NULL", + "description":"Whether optimizer JSON output should add end markers." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"10", + "name":"eq_range_index_dive_limit", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for eq_range_index_dive_limit", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{GlobalSession}", + "id":"621", + "unit":"NULL", + "description":"This variable indicates the number of equality ranges in anequality comparison condition when the optimizer should switchfrom using index dives to index statistics in estimating thenumber of qualifying rows. It applies to evaluation ofexpressions that have either of these equivalent forms wherethe optimizer uses a nonunique index to look upcol_name values:In both cases the expression containsN equality ranges. The optimizercan make row estimates using index dives or index statistics.If eq_range_index_dive_limitis greater than 0 the optimizer uses existing indexstatistics instead of index dives if there areeq_range_index_dive_limit ormore equality ranges. Thus to permit use of index dives forup to N equality ranges seteq_range_index_dive_limit toN + 1. To disable use of indexstatistics and always use index dives regardless ofN seteq_range_index_dive_limit to0For more information seeSection 8.2.1.3.3 Equality Range Optimization of Many-Valued Comparisons.This variable was added in MySQL 5.6.5. Before 5.6.5 theoptimizer makes row estimates using index dives in all cases.To update table index statistics for best estimates useANALYZE TABLE." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"INTERNAL", + "name":"error_count", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"integer", + "max_value":"NULL", + "scope":"{NA}", + "id":"622", + "unit":"NULL", + "description":"The number of errors that resulted from the last statementthat generated messages. This variable is read only. SeeSection 13.7.5.18 SHOW ERRORS Syntax." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"event_scheduler", + "deprecated":"f", + "valid_vals":"ON,OFF,DISABLED", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for event-scheduler", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"623", + "unit":"NULL", + "description":"This variable indicates the status of the Event Scheduler;possible values are ONOFF and DISABLED withthe default being OFF. This variable andits effects on the Event Scheduler's operation are discussedin greater detail in theOverview sectionof the Events chapter." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"expire_logs_days", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for expire_logs_days", + "vartype":"integer", + "max_value":"99", + "scope":"{Global}", + "id":"624", + "unit":"NULL", + "description":"The number of days for automatic binary log file removal. Thedefault is 0 which means no automatic removal.Possible removals happen at startup and when the binary log isflushed. Log flushing occurs as indicated inSection 5.4 MySQL Server Logs.To remove binary log files manually use thePURGE BINARY LOGS statement.See Section 13.4.1.1 PURGE BINARY LOGS Syntax." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"FALSE", + "name":"explicit_defaults_for_timestamp", + "deprecated":"t", + "valid_vals":"TRUE,FALSE", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for explicit_defaults_for_timestamp", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"625", + "unit":"NULL", + "description":"In MySQL the TIMESTAMP datatype differs in nonstandard ways from other data types:Those nonstandard behaviors remain the default forTIMESTAMP but as of MySQL 5.6.6are deprecated and this warning appears at startup:As indicated by the warning to turn off the nonstandardbehaviors enable theexplicit_defaults_for_timestampsystem variable at server startup. With this variable enabledthe server handles TIMESTAMP asfollows instead:This variable was added in MySQL 5.6.6." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"external_user", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for external_user", + "vartype":"string", + "max_value":"NULL", + "scope":"{Session}", + "id":"626", + "unit":"NULL", + "description":"The external user name used during the authentication processas set by the plugin used to authenticate the client. Withnative (built-in) MySQL authentication or if the plugin doesnot set the value this variable is NULL.See Section 6.3.8 Proxy Users." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"flush_time", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for flush_time", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"627", + "unit":"NULL", + "description":"If this is set to a nonzero value all tables are closed everyflush_time seconds to free upresources and synchronize unflushed data to disk. This optionis best used only on systems with minimal resources. Thedefault is 0 except that before MySQL 5.6.6 the default is1800 on Windows." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"foreign_key_checks", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{NA}", + "id":"628", + "unit":"NULL", + "description":"If set to 1 (the default) foreign key constraints forInnoDB tables are checked. If set to 0foreign key constraints are ignored with a couple ofexceptions. When re-creating a table that was dropped anerror is returned if the table definition does not conform tothe foreign key constraints referencing the table. Likewisean ALTER TABLE operationreturns an error if a foreign key definition is incorrectlyformed. For more information seeSection 13.1.17.3 Using FOREIGN KEY Constraints.Beginning with MySQL Cluster NDB 7.3.2 setting this variablehas the same effect on NDB tablesas it does for InnoDBtablespreviously the setting was ignored and all suchchecks were enforced (Bug #14095855). Typically you leave thissetting enabled during normal operation to enforcereferentialintegrity.Disabling foreign key checking can be useful for reloadingsuch tables in an order different from that required by theirparent/child relationships. SeeSection 14.6.6 InnoDB and FOREIGN KEY Constraints.Setting foreign_key_checks to 0 alsoaffects data definition statements:DROPSCHEMA drops a schema even if it contains tablesthat have foreign keys that are referred to by tables outsidethe schema and DROP TABLEdrops tables that have foreign keys that are referred to byother tables." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"+ -><()~*:&|", + "name":"ft_boolean_syntax", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for ft_boolean_syntax", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"629", + "unit":"NULL", + "description":"The list of operators supported by boolean full-text searchesperformed using IN BOOLEAN MODE. SeeSection 12.9.2 Boolean Full-Text Searches.The default variable value is'+ -><()~*:&|'. The rulesfor changing the value are as follows:" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"84", + "name":"ft_max_word_len", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"10", + "dynamic":"f", + "rank":"-1", + "summary":"Options for ft_max_word_len", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"630", + "unit":"NULL", + "description":"The maximum length of the word to be included in aMyISAM FULLTEXT index." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"4", + "name":"ft_min_word_len", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"f", + "rank":"-1", + "summary":"Options for ft_min_word_len", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"631", + "unit":"NULL", + "description":"The minimum length of the word to be included in aMyISAM FULLTEXT index." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"20", + "name":"ft_query_expansion_limit", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"Options for ft_query_expansion_limit", + "vartype":"integer", + "max_value":"1000", + "scope":"{Global}", + "id":"632", + "unit":"NULL", + "description":"The number of top matches to use for full-text searchesperformed using WITH QUERY EXPANSION." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"ft_stopword_file", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for ft_stopword_file", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"633", + "unit":"NULL", + "description":"The file from which to read the list of stopwords forfull-text searches on MyISAM tables. Theserver looks for the file in the data directory unless anabsolute path name is given to specify a different directory.All the words from the file are used; comments arenot honored. By default a built-in listof stopwords is used (as defined in thestorage/myisam/ft_static.c file). Settingthis variable to the empty string ('')disables stopword filtering. See alsoSection 12.9.4 Full-Text Stopwords." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"general_log", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for general-log", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"634", + "unit":"NULL", + "description":"Whether the general query log is enabled. The value can be 0(or OFF) to disable the log or 1 (orON) to enable the log. The default valuedepends on whether the--general_log option is given.The destination for log output is controlled by thelog_output system variable;if that value is NONE no log entries arewritten even if the log is enabled." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"host_name.log", + "name":"general_log_file", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for general_log_file", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"635", + "unit":"NULL", + "description":"The name of the general query log file. The default value ishost_name.logbut the initial value can be changed with the--general_log_file option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"have_innodb", + "deprecated":"f", + "valid_vals":"YES,NO,DISABLED", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"642", + "unit":"NULL", + "description":"YES if mysqld supportsInnoDB tables. DISABLEDif--skip-innodbis used.This variable was removed in MySQL 5.6.1. UseSHOW ENGINES instead." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"have_openssl", + "deprecated":"f", + "valid_vals":"YES,NO,DISABLED", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"643", + "unit":"NULL", + "description":"This variable is an alias forhave_ssl." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"have_partitioning", + "deprecated":"f", + "valid_vals":"YES,NO,DISABLED", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"644", + "unit":"NULL", + "description":"YES if mysqld supportspartitioning.This variable was removed in MySQL 5.6.1. UseSHOW PLUGINS instead. For moreinformation see Chapter 19 Partitioning." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"have_profiling", + "deprecated":"f", + "valid_vals":"YES,NO,DISABLED", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"645", + "unit":"NULL", + "description":"YES if statement profiling capability ispresent NO if not. If present theprofiling system variable controls whetherthis capability is enabled or disabled. SeeSection 13.7.5.32 SHOW PROFILES Syntax.This variable is deprecated in MySQL 5.6.8 and will be removedin a future MySQL release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"have_query_cache", + "deprecated":"f", + "valid_vals":"YES,NO,DISABLED", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"646", + "unit":"NULL", + "description":"YES if mysqld supportsthe query cache NO if not." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"have_rtree_keys", + "deprecated":"f", + "valid_vals":"YES,NO,DISABLED", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"647", + "unit":"NULL", + "description":"YES if RTREE indexes areavailable NO if not. (These are used forspatial indexes in MyISAM tables.)" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"have_ssl", + "deprecated":"f", + "valid_vals":"YES,NO,DISABLED", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"648", + "unit":"NULL", + "description":"YES if mysqld supportsSSL connections NO if not.DISABLED indicates that the server wascompiled with SSL support but was not started with theappropriate--ssl-xxx options.For more information seeSection 6.3.9.2 Building MySQL with Support for Secure Connections." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"have_symlink", + "deprecated":"f", + "valid_vals":"YES,NO,DISABLED", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"649", + "unit":"NULL", + "description":"YES if symbolic link support is enabledNO if not. This is required on Unix forsupport of the DATA DIRECTORY andINDEX DIRECTORY table options and onWindows for support of data directory symlinks. If the serveris started with the--skip-symbolic-linksoption the value is DISABLED." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"128", + "name":"host_cache_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for host_cache_size", + "vartype":"integer", + "max_value":"65536", + "scope":"{Global}", + "id":"650", + "unit":"NULL", + "description":"The size of the internal host cache (seeSection 8.12.6.2 DNS Lookup Optimization and the Host Cache). Setting the size to 0 disablesthe host cache. Changing the cache size at runtime implicitlycauses a FLUSHHOSTS operation to clear the host cache and truncatethe host_cache table.The default value is 128 plus 1 for a value ofmax_connections up to 500plus 1 for every increment of 20 over 500 in themax_connections value cappedto a limit of 2000. Before MySQL 5.6.8 the default is 128.Use of --skip-host-cache issimilar to setting thehost_cache_size systemvariable to 0 buthost_cache_size is moreflexible because it can also be used to resize enable ordisable the host cache at runtime not just at server startup.If you start the server with--skip-host-cache that doesnot prevent changes to the value ofhost_cache_size but suchchanges have no effect and the cache is not re-enabled even ifhost_cache_size is set largerthan 0.This variable was added in MySQL 5.6.5." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"hostname", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for hostname", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"651", + "unit":"NULL", + "description":"The server sets this variable to the server host name atstartup." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"INTERNAL", + "name":"identity", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"integer", + "max_value":"NULL", + "scope":"{NA}", + "id":"652", + "unit":"NULL", + "description":"This variable is a synonym for thelast_insert_id variable. Itexists for compatibility with other database systems. You canread its value with SELECT @@identity andset it using SET identity." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"ignore_db_dirs", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for ignore_db_dirs", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"653", + "unit":"NULL", + "description":"A comma-separated list of names that are not considered asdatabase directories in the data directory. The value is setfrom any instances of--ignore-db-dir given at serverstartup.This variable was added in MySQL 5.6.3." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"init_connect", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for init_connect", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"654", + "unit":"NULL", + "description":"A string to be executed by the server for each client thatconnects. The string consists of one or more SQL statementsseparated by semicolon characters. For example each clientsession begins by default with autocommit mode enabled. Forolder servers (before MySQL 5.5.8) there is no globalautocommit system variable tospecify that autocommit should be disabled by default but asa workaround init_connect canbe used to achieve the same effect:The init_connect variable canalso be set on the command line or in an option file. To setthe variable as just shown using an option file include theselines:The content of init_connectis not executed for users that have theSUPER privilege. This is doneso that an erroneous value forinit_connect does not preventall clients from connecting. For example the value mightcontain a statement that has a syntax error thus causingclient connections to fail. Not executinginit_connect for users thathave the SUPER privilegeenables them to open a connection and fix theinit_connect value.The server discards any result sets produced by statements inthe value of of init_connect." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"init_file", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for init-file", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"655", + "unit":"NULL", + "description":"The name of the file specified with the--init-file option when youstart the server. This should be a file containing SQLstatements that you want the server to execute when it starts.Each statement must be on a single line and should not includecomments. For more information see the description of--init-file." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"INTERNAL", + "name":"insert_id", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"integer", + "max_value":"NULL", + "scope":"{NA}", + "id":"656", + "unit":"NULL", + "description":"The value to be used by the followingINSERT orALTER TABLE statement wheninserting an AUTO_INCREMENT value. This ismainly used with the binary log." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"28800", + "name":"interactive_timeout", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for interactive_timeout", + "vartype":"integer", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"657", + "unit":"NULL", + "description":"The number of seconds the server waits for activity on aninteractive connection before closing it. An interactiveclient is defined as a client that uses theCLIENT_INTERACTIVE option tomysql_real_connect(). See alsowait_timeout." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"131072", + "name":"join_buffer_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"128", + "dynamic":"t", + "rank":"-1", + "summary":"Options for join_buffer_size", + "vartype":"integer", + "max_value":"18446744073709547520", + "scope":"{GlobalSession}", + "id":"658", + "unit":"NULL", + "description":"The minimum size of the buffer that is used for plain indexscans range index scans and joins that do not use indexesand thus perform full table scans. Normally the best way toget fast joins is to add indexes. Increase the value ofjoin_buffer_size to get afaster full join when adding indexes is not possible. One joinbuffer is allocated for each full join between two tables. Fora complex join between several tables for which indexes arenot used multiple join buffers might be necessary.Unless Batched Key Access (BKA) is used there is no gain fromsetting the buffer larger than required to hold each matchingrow and all joins allocate at least the minimum size so usecaution in setting this variable to a large value globally. Itis better to keep the global setting small and change to alarger setting only in sessions that are doing large joins.Memory allocation time can cause substantial performance dropsif the global size is larger than needed by most queries thatuse it.When BKA is used the value ofjoin_buffer_size defines howlarge the batch of keys is in each request to the storageengine. The larger the buffer the more sequential access willbe to the right hand table of a join operation which cansignificantly improve performance.The default is 256KB as of MySQL 5.6.6 128KB before that. Themaximum permissible setting forjoin_buffer_size is4GB1. Larger values are permitted for 64-bit platforms(except 64-bit Windows for which large values are truncatedto 4GB1 with a warning).For additional information about join buffering seeSection 8.2.1.10 Nested-Loop Join Algorithms. For information aboutBatched Key Access seeSection 8.2.1.14 Block Nested-Loop and Batched Key Access Joins." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"keep_files_on_create", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for keep_files_on_create", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"659", + "unit":"NULL", + "description":"If a MyISAM table is created with noDATA DIRECTORY option the.MYD file is created in the databasedirectory. By default if MyISAM finds anexisting .MYD file in this case itoverwrites it. The same applies to .MYIfiles for tables created with no INDEXDIRECTORY option. To suppress this behavior set thekeep_files_on_create variableto ON (1) in which caseMyISAM will not overwrite existing filesand returns an error instead. The default value isOFF (0).If a MyISAM table is created with aDATA DIRECTORY or INDEXDIRECTORY option and an existing.MYD or .MYI file isfound MyISAM always returns an error. It will not overwrite afile in the specified directory." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"8388608", + "name":"key_buffer_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"8", + "dynamic":"t", + "rank":"-1", + "summary":"Options for key_buffer_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"660", + "unit":"NULL", + "description":"Index blocks for MyISAM tables are bufferedand are shared by all threads.key_buffer_size is the sizeof the buffer used for index blocks. The key buffer is alsoknown as the key cache.The maximum permissible setting forkey_buffer_size is4GB1 on 32-bit platforms. Larger values are permittedfor 64-bit platforms. The effective maximum size might beless depending on your available physical RAM and per-processRAM limits imposed by your operating system or hardwareplatform. The value of this variable indicates the amount ofmemory requested. Internally the server allocates as muchmemory as possible up to this amount but the actualallocation might be less.You can increase the value to get better index handling forall reads and multiple writes; on a system whose primaryfunction is to run MySQL using theMyISAM storage engine 25% of themachine's total memory is an acceptable value for thisvariable. However you should be aware that if you make thevalue too large (for example more than 50% of themachine's total memory) your system might start to pageand become extremely slow. This is because MySQL relies on theoperating system to perform file system caching for datareads so you must leave some room for the file system cache.You should also consider the memory requirements of any otherstorage engines that you may be using in addition toMyISAM.For even more speed when writing many rows at the same timeuse LOCK TABLES. SeeSection 8.2.2.1 Speed of INSERT Statements.You can check the performance of the key buffer by issuing aSHOW STATUS statement andexamining theKey_read_requestsKey_readsKey_write_requests andKey_writes status variables.(See Section 13.7.5 SHOW Syntax.) TheKey_reads/Key_read_requests ratio shouldnormally be less than 0.01. TheKey_writes/Key_write_requests ratio isusually near 1 if you are using mostly updates and deletesbut might be much smaller if you tend to do updates thataffect many rows at the same time or if you are using theDELAY_KEY_WRITE table option.The fraction of the key buffer in use can be determined usingkey_buffer_size inconjunction with theKey_blocks_unused statusvariable and the buffer block size which is available fromthe key_cache_block_sizesystem variable:This value is an approximation because some space in the keybuffer is allocated internally for administrative structures.Factors that influence the amount of overhead for thesestructures include block size and pointer size. As block sizeincreases the percentage of the key buffer lost to overheadtends to decrease. Larger blocks results in a smaller numberof read operations (because more keys are obtained per read)but conversely an increase in reads of keys that are notexamined (if not all keys in a block are relevant to a query).It is possible to create multiple MyISAMkey caches. The size limit of 4GB applies to each cacheindividually not as a group. SeeSection 8.10.2 The MyISAM Key Cache." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"300", + "name":"key_cache_age_threshold", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"100", + "dynamic":"t", + "rank":"-1", + "summary":"Options for key_cache_age_threshold", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"661", + "unit":"NULL", + "description":"This value controls the demotion of buffers from the hotsublist of a key cache to the warm sublist. Lower values causedemotion to happen more quickly. The minimum value is 100. Thedefault value is 300. See Section 8.10.2 The MyISAM Key Cache." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1024", + "name":"key_cache_block_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"512", + "dynamic":"t", + "rank":"-1", + "summary":"Options for key_cache_block_size", + "vartype":"integer", + "max_value":"16384", + "scope":"{Global}", + "id":"662", + "unit":"NULL", + "description":"The size in bytes of blocks in the key cache. The defaultvalue is 1024. See Section 8.10.2 The MyISAM Key Cache." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"100", + "name":"key_cache_division_limit", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for key_cache_division_limit", + "vartype":"integer", + "max_value":"100", + "scope":"{Global}", + "id":"663", + "unit":"NULL", + "description":"The division point between the hot and warm sublists of thekey cache buffer list. The value is the percentage of thebuffer list to use for the warm sublist. Permissible valuesrange from 1 to 100. The default value is 100. SeeSection 8.10.2 The MyISAM Key Cache." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"large_files_support", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for large_files_support", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"664", + "unit":"NULL", + "description":"Whether mysqld was compiled with optionsfor large file support." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"FALSE", + "name":"large_pages", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for large-pages", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"665", + "unit":"NULL", + "description":"Whether large page support is enabled (via the--large-pages option). SeeSection 8.12.5.2 Enabling Large Page Support." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"large_page_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for large_page_size", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"666", + "unit":"NULL", + "description":"If large page support is enabled this shows the size ofmemory pages. Large memory pages are supported only on Linux;on other platforms the value of this variable is always 0.See Section 8.12.5.2 Enabling Large Page Support." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"INTERNAL", + "name":"last_insert_id", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"integer", + "max_value":"NULL", + "scope":"{NA}", + "id":"667", + "unit":"NULL", + "description":"The value to be returned fromLAST_INSERT_ID(). This isstored in the binary log when you useLAST_INSERT_ID() in a statementthat updates a table. Setting this variable does not updatethe value returned by themysql_insert_id() C APIfunction." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"10000", + "name":"performance_schema_events_statements_history_long_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_events_statements_history_long_size", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"844", + "unit":"NULL", + "description":"The number of rows in theevents_statements_history_longtable. This variable was added in MySQL 5.6.3." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"en_US", + "name":"lc_messages", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for lc-messages", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"668", + "unit":"NULL", + "description":"The locale to use for error messages. The default isen_US. The server converts the argument toa language name and combines it with the value oflc_messages_dir to producethe location for the error message file. SeeSection 10.2 Setting the Error Message Language." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"lc_messages_dir", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for lc-messages-dir", + "vartype":"directory name", + "max_value":"NULL", + "scope":"{Global}", + "id":"669", + "unit":"NULL", + "description":"The directory where error messages are located. The serveruses the value together with the value oflc_messages to produce thelocation for the error message file. SeeSection 10.2 Setting the Error Message Language." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"LOCALE", + "name":"lc_time_names", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for lc_time_names", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"670", + "unit":"NULL", + "description":"This variable specifies the locale that controls the languageused to display day and month names and abbreviations. Thisvariable affects the output from theDATE_FORMAT()DAYNAME() andMONTHNAME() functions. Localenames are POSIX-style values such as'ja_JP' or 'pt_BR'. Thedefault value is 'en_US' regardless of yoursystem's locale setting. For further information seeSection 10.7 MySQL Server Locale Support." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"GPL", + "name":"license", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for license", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"671", + "unit":"NULL", + "description":"The type of license the server has." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"local_infile", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for local_infile", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"672", + "unit":"NULL", + "description":"Whether LOCAL is supported forLOAD DATAINFILE statements. If this variable is disabledclients cannot use LOCAL inLOAD DATA statements. SeeSection 6.1.6 Security Issues with LOAD DATA LOCAL." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"31536000", + "name":"lock_wait_timeout", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for lock_wait_timeout", + "vartype":"integer", + "max_value":"31536000", + "scope":"{GlobalSession}", + "id":"673", + "unit":"NULL", + "description":"This variable specifies the timeout in seconds for attempts toacquire metadata locks. The permissible values range from 1 to31536000 (1 year). The default is 31536000.This timeout applies to all statements that use metadatalocks. These include DML and DDL operations on tables viewsstored procedures and stored functions as well asLOCK TABLESFLUSH TABLES WITH READLOCK and HANDLERstatements.This timeout does not apply to implicit accesses to systemtables in the mysql database such as granttables modified by GRANT orREVOKE statements or tablelogging statements. The timeout does apply to system tablesaccessed directly such as withSELECT orUPDATE.The timeout value applies separately for each metadata lockattempt. A given statement can require more than one lock soit is possible for the statement to block for longer than thelock_wait_timeout valuebefore reporting a timeout error. When lock timeout occursER_LOCK_WAIT_TIMEOUT isreported.lock_wait_timeout does notapply to delayed inserts which always execute with a timeoutof 1 year. This is done to avoid unnecessary timeouts becausea session that issues a delayed insert receives nonotification of delayed insert timeouts." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"locked_in_memory", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for locked_in_memory", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"674", + "unit":"NULL", + "description":"Whether mysqld was locked in memory with--memlock." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"FALSE", + "name":"log_bin_trust_function_creators", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for log-bin-trust-function-creators", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"675", + "unit":"NULL", + "description":"This variable applies when binary logging is enabled. Itcontrols whether stored function creators can be trusted notto create stored functions that will cause unsafe events to bewritten to the binary log. If set to 0 (the default) usersare not permitted to create or alter stored functions unlessthey have the SUPER privilegein addition to the CREATEROUTINE or ALTERROUTINE privilege. A setting of 0 also enforces therestriction that a function must be declared with theDETERMINISTIC characteristic or with theREADS SQL DATA or NO SQLcharacteristic. If the variable is set to 1 MySQL does notenforce these restrictions on stored function creation. Thisvariable also applies to trigger creation. SeeSection 20.7 Binary Logging of Stored Programs." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"log_error", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for log-error", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"676", + "unit":"NULL", + "description":"The location of the error log or empty if the server iswriting error message to the standard error output. SeeSection 5.4.2 The Error Log." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"FILE", + "name":"log_output", + "deprecated":"f", + "valid_vals":"TABLE,FILE,NONE", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for log-output", + "vartype":"set", + "max_value":"NULL", + "scope":"{Global}", + "id":"677", + "unit":"NULL", + "description":"The destination for general query log and slow query logoutput. The value can be a comma-separated list of one or moreof the words TABLE (log to tables)FILE (log to files) orNONE (do not log to tables or files). Thedefault value is FILE.NONE if present takes precedence over anyother specifiers. If the value is NONE logentries are not written even if the logs are enabled. If thelogs are not enabled no logging occurs even if the value oflog_output is notNONE. For more information seeSection 5.4.1 Selecting General Query and Slow Query Log Output Destinations." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"log_queries_not_using_indexes", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for log-queries-not-using-indexes", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"678", + "unit":"NULL", + "description":"Whether queries that do not use indexes are logged to the slowquery log. See Section 5.4.5 The Slow Query Log." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"10", + "name":"performance_schema_events_statements_history_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_events_statements_history_size", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"845", + "unit":"NULL", + "description":"The number of rows per thread in theevents_statements_history table.This variable was added in MySQL 5.6.3." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"log_slow_admin_statements", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for log_slow_admin_statements", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"679", + "unit":"NULL", + "description":"Include slow administrative statements in the statementswritten to the slow query log. Administrative statementsinclude ALTER TABLEANALYZE TABLECHECK TABLECREATE INDEXDROP INDEXOPTIMIZE TABLE andREPAIR TABLE.This variable was added in MySQL 5.6.11 as a replacement forthe --log-slow-admin-statementsoption. The system variable can be set on the command line orin option files the same way as the option so there is noneed for any changes at server startup but the systemvariable also makes it possible to examine or set the value atruntime." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"log_slow_queries", + "deprecated":"t", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for log-slow-queries", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"680", + "unit":"NULL", + "description":"This variable was removed in MySQL 5.6.1. Useslow_query_log instead." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"log_throttle_queries_not_using_indexes", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for log_throttle_queries_not_using_indexes", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"681", + "unit":"NULL", + "description":"Iflog_queries_not_using_indexesis enabled thelog_throttle_queries_not_using_indexesvariable limits the number of such queries per minute that canbe written to the slow query log. A value of 0 (the default)means no limit. For more information seeSection 5.4.5 The Slow Query Log.This variable was added in MySQL 5.6.5." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"log_warnings", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for log-warnings", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"682", + "unit":"NULL", + "description":"Whether to produce additional warning messages to the errorlog. This variable is enabled (1) by default and can bedisabled by setting it to 0. The server logs messages aboutstatements that are unsafe for statement-based logging if thevalue is greater than 0. Aborted connections and access-deniederrors for new connection attempts are logged if the value isgreater than 1." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"10", + "name":"long_query_time", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for long_query_time", + "vartype":"numeric", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"683", + "unit":"NULL", + "description":"If a query takes longer than this many seconds the serverincrements the Slow_queriesstatus variable. If the slow query log is enabled the queryis logged to the slow query log file. This value is measuredin real time not CPU time so a query that is under thethreshold on a lightly loaded system might be above thethreshold on a heavily loaded one. The minimum and defaultvalues of long_query_time are0 and 10 respectively. The value can be specified to aresolution of microseconds. For logging to a file times arewritten including the microseconds part. For logging totables only integer times are written; the microseconds partis ignored. See Section 5.4.5 The Slow Query Log." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"FALSE", + "name":"low_priority_updates", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for low-priority-updates", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"684", + "unit":"NULL", + "description":"If set to 1 allINSERTUPDATEDELETE and LOCK TABLEWRITE statements wait until there is no pendingSELECT or LOCK TABLEREAD on the affected table. This affects onlystorage engines that use only table-level locking (such asMyISAM MEMORY andMERGE)." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"lower_case_file_system", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for lower_case_file_system", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"685", + "unit":"NULL", + "description":"This variable describes the case sensitivity of file names onthe file system where the data directory is located.OFF means file names are case sensitiveON means they are not case sensitive. Thisvariable is read only because it reflects a file systemattribute and setting it would have no effect on the filesystem." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"lower_case_table_names", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"Options for lower_case_table_names", + "vartype":"integer", + "max_value":"2", + "scope":"{Global}", + "id":"686", + "unit":"NULL", + "description":"If set to 0 table names are stored as specified andcomparisons are case sensitive. If set to 1 table names arestored in lowercase on disk and comparisons are not casesensitive. If set to 2 table names are stored as given butcompared in lowercase. This option also applies to databasenames and table aliases. For additional information seeSection 9.2.2 Identifier Case Sensitivity.On Windows the default value is 1. On OS X the default valueis 2.You should not setlower_case_table_names to 0if you are running MySQL on a system where the data directoryresides on a case-insensitive file system (such as on Windowsor OS X). It is an unsupported combination that could resultin a hang condition when running an INSERT INTO ...SELECT ... FROM tbl_nameoperation with the wrong tbl_nameletter case. With MyISAM accessing tablenames using different letter cases could cause indexcorruption.As of MySQL 5.6.27 an error message is printed and the serverexits if you attempt to start the server with--lower_case_table_names=0 ona case-insensitive file system.If you are using InnoDB tables you shouldset this variable to 1 on all platforms to force names to beconverted to lowercase.The setting of this variable in MySQL 5.6 affectsthe behavior of replication filtering options with regard tocase sensitivity. This is a change from previous versions ofMySQL. (Bug #51639) See Section 17.2.3 How Servers Evaluate Replication Filtering Rulesfor more information.In previous versions of MySQL using different settings forlower_case_table_names on replicationmasters and slaves could cause replication to fail when theslave used a case-sensitive file system. This issue isresolved in MySQL 5.6.1. For more information seeSection 17.4.1.36 Replication and Variables." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1048576", + "name":"max_allowed_packet", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1024", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_allowed_packet", + "vartype":"integer", + "max_value":"1073741824", + "scope":"{GlobalSession}", + "id":"687", + "unit":"NULL", + "description":"The maximum size of one packet or any generated/intermediatestring or any parameter sent by themysql_stmt_send_long_data() CAPI function. The default is 4MB as of MySQL 5.6.6 1MB beforethat.The packet message buffer is initialized tonet_buffer_length bytes butcan grow up tomax_allowed_packet bytes whenneeded. This value by default is small to catch large(possibly incorrect) packets.You must increase this value if you are using largeBLOB columns or long strings.It should be as big as the largestBLOB you want to use. Theprotocol limit formax_allowed_packet is 1GB.The value should be a multiple of 1024; nonmultiples arerounded down to the nearest multiple.When you change the message buffer size by changing the valueof the max_allowed_packetvariable you should also change the buffer size on the clientside if your client program permits it. The defaultmax_allowed_packet valuebuilt in to the client library is 1GB but individual clientprograms might override this. For examplemysql and mysqldump havedefaults of 16MB and 24MB respectively. They also enable youto change the client-side value by settingmax_allowed_packet on thecommand line or in an option file.The session value of this variable is read only. The clientcan receive up to as many bytes as the session value. Howeverthe server will not send to the client more bytes than thecurrent globalmax_allowed_packet value.(The global value could be less than the session value if theglobal value is changed after the client connects.)" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"hex", + "name":"bytea_output", + "deprecated":"f", + "valid_vals":"escape,hex", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the output format for bytea.", + "vartype":"enum", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1480", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"10", + "name":"max_connect_errors", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_connect_errors", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"688", + "unit":"NULL", + "description":"If more than this many successive connection requests from ahost are interrupted without a successful connection theserver blocks that host from further connections. You canunblock blocked hosts by flushing the host cache. To do soissue a FLUSHHOSTS statement or execute a mysqladminflush-hosts command. If a connection is establishedsuccessfully within fewer thanmax_connect_errors attemptsafter a previous connection was interrupted the error countfor the host is cleared to zero. However once a host isblocked flushing the host cache is the only way to unblockit. The default is 100 as of MySQL 5.6.6 10 before that." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"151", + "name":"max_connections", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_connections", + "vartype":"integer", + "max_value":"100000", + "scope":"{Global}", + "id":"689", + "unit":"NULL", + "description":"The maximum permitted number of simultaneous clientconnections. By default this is 151. SeeSection B.5.2.7 Too many connections for more information.Increasing this value increases the number of file descriptorsthat mysqld requires. If the requirednumber of descriptors are not available the server reducesthe value of max_connections.See Section 8.4.3.1 How MySQL Opens and Closes Tables for comments on filedescriptor limits.Connections refused because themax_connections limit isreached increment theConnection_errors_max_connectionsstatus variable." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"20", + "name":"max_delayed_threads", + "deprecated":"t", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_delayed_threads", + "vartype":"integer", + "max_value":"16384", + "scope":"{GlobalSession}", + "id":"690", + "unit":"NULL", + "description":"Do not start more than this number of threads to handleINSERT DELAYED statements fornontransactional tables. If you try to insert data into a newtable after all INSERT DELAYEDthreads are in use the row is inserted as if theDELAYED attribute was not specified. If youset this to 0 MySQL never creates a thread to handleDELAYED rows; in effect this disablesDELAYED entirely.For the SESSION value of this variable theonly valid values are 0 or the GLOBALvalue.As of MySQL 5.6.7 this system variable is deprecated (becauseDELAYED inserts are deprecated) and willbe removed in a future release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1024", + "name":"max_digest_length", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"Options for max_digest_length", + "vartype":"integer", + "max_value":"1048576", + "scope":"{Global}", + "id":"691", + "unit":"NULL", + "description":"The maximum number of bytes available for computing statementdigests (seeSection 22.7 Performance Schema Statement Digests). Whenthis amount of space is used for computing the digest for astatement no further tokens from the parsed statement arecollected or figure into the digest value. Statementsdiffering only after that many bytes of parsed statementtokens produce the same digest and are aggregated for digeststatistics.Decreasing themax_digest_length valuereduces memory use but causes the digest value of morestatements to become indistinguishable if they differ only atthe end. Increasing the value permits longer statements to bedistinguished but increases memory use particularly forworkloads that involve large numbers of simultaneous sessions(max_digest_length bytes areallocated per session).This variable was added in MySQL 5.6.24. Until 5.6.26 thisvariable applies to Performance Schema and to other serverfunctions that use digests such as MySQL Enterprise Firewall. As of 5.6.26 itno longer applies to Performance Schema; instead useperformance_schema_max_digest_length." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"64", + "name":"max_error_count", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_error_count", + "vartype":"integer", + "max_value":"65535", + "scope":"{GlobalSession}", + "id":"692", + "unit":"NULL", + "description":"The maximum number of error warning and note messages to bestored for display by the SHOWERRORS and SHOWWARNINGS statements. This is the same as the numberof condition areas in the diagnostics area and thus thenumber of conditions that can be inspected byGET DIAGNOSTICS." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"16777216", + "name":"max_heap_table_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"16384", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_heap_table_size", + "vartype":"integer", + "max_value":"1844674407370954752", + "scope":"{GlobalSession}", + "id":"693", + "unit":"NULL", + "description":"This variable sets the maximum size to which user-createdMEMORY tables are permitted to grow. Thevalue of the variable is used to calculateMEMORY table MAX_ROWSvalues. Setting this variable has no effect on any existingMEMORY table unless the table isre-created with a statement such asCREATE TABLE or altered withALTER TABLE orTRUNCATE TABLE. A serverrestart also sets the maximum size of existingMEMORY tables to the globalmax_heap_table_size value.This variable is also used in conjunction withtmp_table_size to limit thesize of internal in-memory tables. SeeSection 8.4.4 Internal Temporary Table Use in MySQL.max_heap_table_size is not replicated. SeeSection 17.4.1.22 Replication and MEMORY Tables andSection 17.4.1.36 Replication and Variables for moreinformation." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"20", + "name":"max_insert_delayed_threads", + "deprecated":"t", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_insert_delayed_threads", + "vartype":"integer", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"694", + "unit":"NULL", + "description":"This variable is a synonym formax_delayed_threads.As of MySQL 5.6.7 this system variable is deprecated (becauseDELAYED inserts are deprecated) and willbe removed in a future release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1024", + "name":"metadata_locks_cache_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"f", + "rank":"-1", + "summary":"Options for metadata_locks_cache_size", + "vartype":"integer", + "max_value":"1048576", + "scope":"{Global}", + "id":"705", + "unit":"NULL", + "description":"The size of the metadata locks cache. The server uses thiscache to avoid creation and destruction of synchronizationobjects. This is particularly helpful on systems where suchoperations are expensive such as Windows XP. This variablewas added in MySQL 5.6.4." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"4096", + "name":"query_cache_min_res_unit", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"512", + "dynamic":"t", + "rank":"-1", + "summary":"Options for query_cache_min_res_unit", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"746", + "unit":"NULL", + "description":"The minimum size (in bytes) for blocks allocated by the querycache. The default value is 4096 (4KB). Tuning information forthis variable is given inSection 8.10.3.3 Query Cache Configuration." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"18446744073709551615", + "name":"max_join_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_join_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{GlobalSession}", + "id":"695", + "unit":"NULL", + "description":"Do not permit statements that probably need to examine morethan max_join_size rows (forsingle-table statements) or row combinations (formultiple-table statements) or that are likely to do more thanmax_join_size disk seeks. Bysetting this value you can catch statements where keys arenot used properly and that would probably take a long time.Set it if your users tend to perform joins that lack aWHERE clause that take a long time orthat return millions of rows.Setting this variable to a value other thanDEFAULT resets the value ofsql_big_selects to0. If you set thesql_big_selects value againthe max_join_size variable isignored.If a query result is in the query cache no result size checkis performed because the result has previously been computedand it does not burden the server to send it to the client." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1024", + "name":"max_length_for_sort_data", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"4", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_length_for_sort_data", + "vartype":"integer", + "max_value":"8388608", + "scope":"{GlobalSession}", + "id":"696", + "unit":"NULL", + "description":"The cutoff on the size of index values that determines whichfilesort algorithm to use. SeeSection 8.2.1.15 ORDER BY Optimization." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"16382", + "name":"max_prepared_stmt_count", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_prepared_stmt_count", + "vartype":"integer", + "max_value":"1048576", + "scope":"{Global}", + "id":"697", + "unit":"NULL", + "description":"This variable limits the total number of prepared statementsin the server. (The sum of the number of prepared statementsacross all sessions.) It can be used in environments wherethere is the potential for denial-of-service attacks based onrunning the server out of memory by preparing huge numbers ofstatements. If the value is set lower than the current numberof prepared statements existing statements are not affectedand can be used but no new statements can be prepared untilthe current number drops below the limit. The default value is16382. The permissible range of values is from 0 to 1million. Setting the value to 0 disables prepared statements." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"max_relay_log_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_relay_log_size", + "vartype":"integer", + "max_value":"1073741824", + "scope":"{Global}", + "id":"698", + "unit":"NULL", + "description":"If a write by a replication slave to its relay log causes thecurrent log file size to exceed the value of this variablethe slave rotates the relay logs (closes the current file andopens the next one). Ifmax_relay_log_size is 0 theserver uses max_binlog_sizefor both the binary log and the relay log. Ifmax_relay_log_size is greaterthan 0 it constrains the size of the relay log which enablesyou to have different sizes for the two logs. You must setmax_relay_log_size to between4096 bytes and 1GB (inclusive) or to 0. The default value is0. See Section 17.2.1 Replication Implementation Details." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"18446744073709551615", + "name":"max_seeks_for_key", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_seeks_for_key", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{GlobalSession}", + "id":"699", + "unit":"NULL", + "description":"Limit the assumed maximum number of seeks when looking up rowsbased on a key. The MySQL optimizer assumes that no more thanthis number of key seeks are required when searching formatching rows in a table by scanning an index regardless ofthe actual cardinality of the index (seeSection 13.7.5.23 SHOW INDEX Syntax). By setting this to a low value(say 100) you can force MySQL to prefer indexes instead oftable scans." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1024", + "name":"max_sort_length", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"4", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_sort_length", + "vartype":"integer", + "max_value":"8388608", + "scope":"{GlobalSession}", + "id":"700", + "unit":"NULL", + "description":"The number of bytes to use when sorting data values. Theserver uses only the firstmax_sort_length bytes of eachvalue and ignores the rest. Consequently values that differonly after the firstmax_sort_length bytes compareas equal for GROUP BY ORDERBY and DISTINCT operations.Increasing the value ofmax_sort_length may requireincreasing the value ofsort_buffer_size as well. Fordetails see Section 8.2.1.15 ORDER BY Optimization" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"max_sp_recursion_depth", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_sp_recursion_depth", + "vartype":"integer", + "max_value":"255", + "scope":"{GlobalSession}", + "id":"701", + "unit":"NULL", + "description":"The number of times that any given stored procedure may becalled recursively. The default value for this option is 0which completely disables recursion in stored procedures. Themaximum value is 255.Stored procedure recursion increases the demand on threadstack space. If you increase the value ofmax_sp_recursion_depth itmay be necessary to increase thread stack size by increasingthe value of thread_stack atserver startup." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"max_tmp_tables", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"integer", + "max_value":"NULL", + "scope":"{NA}", + "id":"702", + "unit":"NULL", + "description":"This variable is unused. It is deprecated as of MySQL 5.6.7and will be removed in a future MySQL release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"max_user_connections", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_user_connections", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{GlobalSession}", + "id":"703", + "unit":"NULL", + "description":"The maximum number of simultaneous connections permitted toany given MySQL user account. A value of 0 (the default) meansno limit.This variable has a global value that can be set at serverstartup or runtime. It also has a read-only session value thatindicates the effective simultaneous-connection limit thatapplies to the account associated with the current session.The session value is initialized as follows:Account resource limits are specified using theGRANT statement. SeeSection 6.3.4 Setting Account Resource Limits and Section 13.7.1.4 GRANT Syntax." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"18446744073709551615", + "name":"max_write_lock_count", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_write_lock_count", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"704", + "unit":"NULL", + "description":"After this many write locks permit some pending read lockrequests to be processed in between." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"INTERNAL", + "name":"pseudo_thread_id", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for pseudo_thread_id", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Session}", + "id":"743", + "unit":"NULL", + "description":"This variable is for internal server use." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"8", + "name":"metadata_locks_hash_instances", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"f", + "rank":"-1", + "summary":"Options for metadata_locks_hash_instances", + "vartype":"integer", + "max_value":"1024", + "scope":"{Global}", + "id":"706", + "unit":"NULL", + "description":"The set of metadata locks can be partitioned into separatehashes to permit connections accessing different objects touse different locking hashes and reduce contention. Themetadata_locks_hash_instancessystem variable specifies the number of hashes (default 8).This variable was added in MySQL 5.6.8." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"256", + "name":"multi_range_count", + "deprecated":"t", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for multi_range_count", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{GlobalSession}", + "id":"707", + "unit":"NULL", + "description":"This variable has no effect. It is deprecated as of MySQL5.6.7 and will be removed in a future MySQL release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"6", + "name":"myisam_data_pointer_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"2", + "dynamic":"t", + "rank":"-1", + "summary":"Options for myisam_data_pointer_size", + "vartype":"integer", + "max_value":"7", + "scope":"{Global}", + "id":"708", + "unit":"NULL", + "description":"The default pointer size in bytes to be used byCREATE TABLE forMyISAM tables when noMAX_ROWS option is specified. This variablecannot be less than 2 or larger than 7. The default value is6. See Section B.5.2.12 The table is full." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"9223372036854775807", + "name":"myisam_max_sort_file_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for myisam_max_sort_file_size", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"709", + "unit":"NULL", + "description":"The maximum size of the temporary file that MySQL is permittedto use while re-creating a MyISAM index(during REPAIR TABLEALTER TABLE orLOAD DATAINFILE). If the file size would be larger than thisvalue the index is created using the key cache instead whichis slower. The value is given in bytes.If MyISAM index files exceed this size anddisk space is available increasing the value may helpperformance. The space must be available in the file systemcontaining the directory where the original index file islocated." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"18446744073709551615", + "name":"myisam_mmap_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"7", + "dynamic":"f", + "rank":"-1", + "summary":"Options for myisam_mmap_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"710", + "unit":"NULL", + "description":"The maximum amount of memory to use for memory mappingcompressed MyISAM files. If manycompressed MyISAM tables are used thevalue can be decreased to reduce the likelihood ofmemory-swapping problems." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"BACKUP", + "name":"myisam_recover_options", + "deprecated":"f", + "valid_vals":"OFF,DEFAULT,BACKUP,FORCE,QUICK,", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for myisam_recover_options", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"711", + "unit":"NULL", + "description":"The value of the--myisam-recover-optionsoption. See Section 5.1.3 Server Command Options." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"myisam_repair_threads", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for myisam_repair_threads", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global,Session}", + "id":"712", + "unit":"NULL", + "description":"If this value is greater than 1 MyISAMtable indexes are created in parallel (each index in its ownthread) during the Repair by sortingprocess. The default value is 1." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"8388608", + "name":"myisam_sort_buffer_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"4096", + "dynamic":"t", + "rank":"-1", + "summary":"Options for myisam_sort_buffer_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{GlobalSession}", + "id":"713", + "unit":"NULL", + "description":"The size of the buffer that is allocated when sortingMyISAM indexes during aREPAIR TABLE or when creatingindexes with CREATE INDEX orALTER TABLE.The maximum permissible setting formyisam_sort_buffer_size is4GB1. Larger values are permitted for 64-bit platforms(except 64-bit Windows prior to MySQL 5.6.5 for which largevalues are truncated to 4GB1 with a warning)." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"nulls_unequal", + "name":"myisam_stats_method", + "deprecated":"f", + "valid_vals":"nulls_equal,nulls_unequal,nulls_ignored", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for myisam_stats_method", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"714", + "unit":"NULL", + "description":"How the server treats NULL values whencollecting statistics about the distribution of index valuesfor MyISAM tables. This variable has threepossible values nulls_equalnulls_unequal andnulls_ignored. Fornulls_equal all NULLindex values are considered equal and form a single valuegroup that has a size equal to the number ofNULL values. Fornulls_unequal NULLvalues are considered unequal and eachNULL forms a distinct value group of size1. For nulls_ignoredNULL values are ignored.The method that is used for generating table statisticsinfluences how the optimizer chooses indexes for queryexecution as described in Section 8.3.7 InnoDB and MyISAM Index Statistics Collection." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"myisam_use_mmap", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for myisam_use_mmap", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"715", + "unit":"NULL", + "description":"Use memory mapping for reading and writingMyISAM tables." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"named_pipe", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for named_pipe", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"716", + "unit":"NULL", + "description":"(Windows only.) Indicates whether the server supportsconnections over named pipes." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"16384", + "name":"net_buffer_length", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1024", + "dynamic":"t", + "rank":"-1", + "summary":"Options for net_buffer_length", + "vartype":"integer", + "max_value":"1048576", + "scope":"{GlobalSession}", + "id":"717", + "unit":"NULL", + "description":"Each client thread is associated with a connection buffer andresult buffer. Both begin with a size given bynet_buffer_length but aredynamically enlarged up tomax_allowed_packet bytes asneeded. The result buffer shrinks tonet_buffer_length after eachSQL statement.This variable should not normally be changed but if you havevery little memory you can set it to the expected length ofstatements sent by clients. If statements exceed this lengththe connection buffer is automatically enlarged. The maximumvalue to whichnet_buffer_length can be setis 1MB.The session value of this variable is read only." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"8192", + "name":"query_alloc_block_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1024", + "dynamic":"t", + "rank":"-1", + "summary":"Options for query_alloc_block_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{GlobalSession}", + "id":"744", + "unit":"1024", + "description":"The allocation size of memory blocks that are allocated forobjects created during statement parsing and execution. If youhave problems with memory fragmentation it might help toincrease this parameter." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"30", + "name":"net_read_timeout", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for net_read_timeout", + "vartype":"integer", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"718", + "unit":"NULL", + "description":"The number of seconds to wait for more data from a connectionbefore aborting the read. When the server is reading from theclient net_read_timeout isthe timeout value controlling when to abort. When the serveris writing to the clientnet_write_timeout is thetimeout value controlling when to abort. See alsoslave_net_timeout." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"10", + "name":"net_retry_count", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for net_retry_count", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{GlobalSession}", + "id":"719", + "unit":"NULL", + "description":"If a read or write on a communication port is interruptedretry this many times before giving up. This value should beset quite high on FreeBSD because internal interrupts are sentto all threads." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"60", + "name":"net_write_timeout", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for net_write_timeout", + "vartype":"integer", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"720", + "unit":"NULL", + "description":"The number of seconds to wait for a block to be written to aconnection before aborting the write. See alsonet_read_timeout." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"FALSE", + "name":"new", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for new", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"721", + "unit":"NULL", + "description":"This variable was used in MySQL 4.0 to turn on some 4.1behaviors and is retained for backward compatibility. Itsvalue is always OFF.In MySQL Cluster setting this variable toON makes it possible to employ partitioningtypes other than KEY or LINEARKEY with NDB tables.This feature is experimental only and not supportedin production. For additional information seeUser-defined partitioning and the NDB storage engine (MySQL Cluster)." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"old", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for old", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"722", + "unit":"NULL", + "description":"old is a compatibilityvariable. It is disabled by default but can be enabled atstartup to revert the server to behaviors present in olderversions.When old is enabled itchanges the default scope of index hints to that used prior toMySQL 5.1.17. That is index hints with noFOR clause apply only to how indexes areused for row retrieval and not to resolution of ORDERBY or GROUP BY clauses. (SeeSection 8.9.3 Index Hints.) Take care about enabling thisin a replication setup. With statement-based binary logginghaving different modes for the master and slaves might lead toreplication errors." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"old_alter_table", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for old-alter-table", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"723", + "unit":"NULL", + "description":"When this variable is enabled the server does not use theoptimized method of processing an ALTERTABLE operation. It reverts to using a temporarytable copying over the data and then renaming the temporarytable to the original as used by MySQL 5.0 and earlier. Formore information on the operation ofALTER TABLE seeSection 13.1.7 ALTER TABLE Syntax." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"old_passwords", + "deprecated":"f", + "valid_vals":"1,0", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for old_passwords", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"724", + "unit":"NULL", + "description":"This variable controls the password hashing method used by thePASSWORD() function. It alsoinfluences password hashing performed byCREATE USER andGRANT statements that specify apassword using an IDENTIFIED BY clause.The following table shows the permitted values ofold_passwords the passwordhashing method for each value and which authenticationplugins use passwords hashed with each method. These valuesare permitted as of MySQL 5.6.6. Before 5.6.6 the permittedvalues are 0 (or OFF) and 1 (orON).If old_passwords=1PASSWORD(str)returns the same value asOLD_PASSWORD(str).The latter function is not affected by the value ofold_passwords.If you set old_passwords=2follow the instructions for using thesha256_password plugin atSection 6.4.1.4 The SHA-256 Authentication Plugin.As of MySQL 5.6.6 the server sets the globalold_passwords value duringstartup to be consistent with the password hashing methodrequired by the default authentication plugin. The defaultplugin is mysql_native_password unless the--default-authentication-pluginoption is set otherwise.As of MySQL 5.6.10 when a client successfully connects to theserver the server sets the sessionold_passwords valueappropriately for the account authentication method. Forexample if the account uses thesha256_password authentication plugin theserver sets old_passwords=2.For additional information about authentication plugins andhashing formats seeSection 6.3.7 Pluggable Authentication andSection 6.1.2.4 Password Hashing in MySQL." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"open_files_limit", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"Options for open-files-limit", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"725", + "unit":"NULL", + "description":"The number of files that the operating system permitsmysqld to open. The value of this variableat runtime is the real value permitted by the system and mightbe different from the value you specify at server startup. Thevalue is 0 on systems where MySQL cannot change the number ofopen files.The effectiveopen_files_limit value isbased on the value specified at system startup (if any) andthe values of max_connectionsand table_open_cache usingthese formulas:The server attempts to obtain the number of file descriptorsusing the maximum of those three values. If that manydescriptors cannot be obtained the server attempts to obtainas many as the system will permit." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"4", + "name":"optimizer_join_cache_level", + "deprecated":"t", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for optimizer_join_cache_level", + "vartype":"integer", + "max_value":"4", + "scope":"{Global,Session}", + "id":"726", + "unit":"NULL", + "description":"Before MySQL 5.6.3 this variable is used for join buffermanagement. It controls how join buffers are used for joinoperations. As of MySQL 5.6.3 it is removed and theoptimizer_switch variable isused instead. See Section 8.2.1.14 Block Nested-Loop and Batched Key Access Joins.The following table shows the permissibleoptimizer_join_cache_levelvalues." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"optimizer_prune_level", + "deprecated":"f", + "valid_vals":"1,0", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for optimizer_prune_level", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"727", + "unit":"NULL", + "description":"Controls the heuristics applied during query optimization toprune less-promising partial plans from the optimizer searchspace. A value of 0 disables heuristics so that the optimizerperforms an exhaustive search. A value of 1 causes theoptimizer to prune plans based on the number of rows retrievedby intermediate plans." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1048576", + "name":"query_cache_limit", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for query_cache_limit", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"745", + "unit":"NULL", + "description":"Do not cache results that are larger than this number ofbytes. The default value is 1MB." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"62", + "name":"optimizer_search_depth", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for optimizer_search_depth", + "vartype":"integer", + "max_value":"62", + "scope":"{GlobalSession}", + "id":"728", + "unit":"NULL", + "description":"The maximum depth of search performed by the query optimizer.Values larger than the number of relations in a query resultin better query plans but take longer to generate anexecution plan for a query. Values smaller than the number ofrelations in a query return an execution plan quicker but theresulting plan may be far from being optimal. If set to 0 thesystem automatically picks a reasonable value." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"index_merge=onindex_merge_union=on index_merge_sort_union=onindex_merge_intersection=on engine_condition_pushdown=on", + "name":"optimizer_switch", + "deprecated":"f", + "valid_vals":"engine_condition_pushdown=on|off,index_merge=on|off,index_merge_intersection=on|off,index_merge_sort_union=on|off,index_merge_union=on|off", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for optimizer_switch", + "vartype":"set", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"729", + "unit":"NULL", + "description":"The optimizer_switch systemvariable enables control over optimizer behavior. The value ofthis variable is a set of flags each of which has a value ofon or off to indicatewhether the corresponding optimizer behavior is enabled ordisabled. This variable has global and session values and canbe changed at runtime. The global default can be set at serverstartup.To see the current set of optimizer flags select the variablevalue:For more information about the syntax of this variable and theoptimizer behaviors that it controls seeSection 8.9.2 Controlling Switchable Optimizations." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"enabled=off", + "name":"optimizer_trace", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for optimizer_trace", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"730", + "unit":"NULL", + "description":"This variable controls optimizer tracing. For details seeMySQLInternals: Tracing the Optimizer. This variable wasadded in MySQL 5.6.3." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"enabled=off", + "name":"optimizer_trace_features", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for optimizer_trace_features", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"731", + "unit":"NULL", + "description":"This variable enables or disables selected optimizer tracingfeatures. For details seeMySQLInternals: Tracing the Optimizer. This variable wasadded in MySQL 5.6.3." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"optimizer_trace_limit", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for optimizer_trace_limit", + "vartype":"integer", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"732", + "unit":"NULL", + "description":"The maximum number of optimizer traces to display. Fordetails seeMySQLInternals: Tracing the Optimizer. This variable wasadded in MySQL 5.6.3." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"16384", + "name":"optimizer_trace_max_mem_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for optimizer_trace_max_mem_size", + "vartype":"integer", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"733", + "unit":"NULL", + "description":"The maximum cumulative size of stored optimizer traces. Fordetails seeMySQLInternals: Tracing the Optimizer. This variable wasadded in MySQL 5.6.3." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"-1", + "name":"optimizer_trace_offset", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for optimizer_trace_offset", + "vartype":"integer", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"734", + "unit":"NULL", + "description":"The offset of optimizer traces to display. For details seeMySQLInternals: Tracing the Optimizer. This variable wasadded in MySQL 5.6.3." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"pid_file", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for pid-file", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"735", + "unit":"NULL", + "description":"The path name of the process ID (PID) file. This variable canbe set with the --pid-fileoption." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"BASEDIR/lib/plugin", + "name":"plugin_dir", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for plugin_dir", + "vartype":"directory name", + "max_value":"NULL", + "scope":"{Global}", + "id":"736", + "unit":"NULL", + "description":"The path name of the plugin directory.If the plugin directory is writable by the server it may bepossible for a user to write executable code to a file in thedirectory using SELECT... INTO DUMPFILE. This can be prevented by makingplugin_dir read only to theserver or by setting--secure-file-priv to adirectory where SELECT writescan be made safely." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"32768", + "name":"preload_buffer_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1024", + "dynamic":"t", + "rank":"-1", + "summary":"Options for preload_buffer_size", + "vartype":"integer", + "max_value":"1073741824", + "scope":"{GlobalSession}", + "id":"737", + "unit":"NULL", + "description":"The size of the buffer that is allocated when preloadingindexes." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"profiling", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{NA}", + "id":"738", + "unit":"NULL", + "description":"If set to 0 or OFF (the default) statementprofiling is disabled. If set to 1 or ONstatement profiling is enabled and theSHOW PROFILE andSHOW PROFILES statementsprovide access to profiling information. SeeSection 13.7.5.32 SHOW PROFILES Syntax.This variable is deprecated in MySQL 5.6.8 and will be removedin a future MySQL release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"15", + "name":"profiling_history_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"integer", + "max_value":"100", + "scope":"{NA}", + "id":"739", + "unit":"NULL", + "description":"The number of statements for which to maintain profilinginformation if profiling isenabled. The default value is 15. The maximum value is 100.Setting the value to 0 effectively disables profiling. SeeSection 13.7.5.32 SHOW PROFILES Syntax.This variable is deprecated in MySQL 5.6.8 and will be removedin a future MySQL release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"protocol_version", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for protocol_version", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"740", + "unit":"NULL", + "description":"The version of the client/server protocol used by the MySQLserver." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"proxy_user", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for proxy_user", + "vartype":"string", + "max_value":"NULL", + "scope":"{Session}", + "id":"741", + "unit":"NULL", + "description":"If the current client is a proxy for another user thisvariable is the proxy user account name. Otherwise thisvariable is NULL. SeeSection 6.3.8 Proxy Users." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"INTERNAL", + "name":"pseudo_slave_mode", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for pseudo_slave_mode", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Session}", + "id":"742", + "unit":"NULL", + "description":"This variable is for internal server use. It was added inMySQL 5.6.10." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"query_cache_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for query_cache_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"747", + "unit":"NULL", + "description":"The amount of memory allocated for caching query results. Bydefault the query cache is disabled. This is achieved using adefault value of 1M with a default forquery_cache_type of 0. (Before MySQL 5.6.8the default size is 0 with a defaultquery_cache_type of 1. To reduce overheadsignificantly you should also start the server withquery_cache_type=0 if youwill not be using the query cache.)The permissible values are multiples of 1024; other values arerounded down to the nearest multiple.The query cache needs a minimum size of about 40KB to allocateits structures. (The exact size depends on systemarchitecture.) If you set the value ofquery_cache_size too small awarning will occur as described inSection 8.10.3.3 Query Cache Configuration." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1", + "name":"query_cache_type", + "deprecated":"f", + "valid_vals":"0,1,2", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for query_cache_type", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"748", + "unit":"NULL", + "description":"Set the query cache type. Setting theGLOBAL value sets the type for all clientsthat connect thereafter. Individual clients can set theSESSION value to affect their own use ofthe query cache. Possible values are shown in the followingtable.This variable defaults to OFF as of MySQL5.6.8 ON before that.If the server is started withquery_cache_type set to 0 it does notacquire the query cache mutex at all which means that thequery cache cannot be enabled at runtime and there is reducedoverhead in query execution." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"FALSE", + "name":"query_cache_wlock_invalidate", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for query_cache_wlock_invalidate", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"749", + "unit":"NULL", + "description":"Normally when one client acquires a WRITElock on a MyISAM table other clients arenot blocked from issuing statements that read from the tableif the query results are present in the query cache. Settingthis variable to 1 causes acquisition of aWRITE lock for a table to invalidate anyqueries in the query cache that refer to the table. Thisforces other clients that attempt to access the table to waitwhile the lock is in effect." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"8192", + "name":"query_prealloc_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"8192", + "dynamic":"t", + "rank":"-1", + "summary":"Options for query_prealloc_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{GlobalSession}", + "id":"750", + "unit":"1024", + "description":"The size of the persistent buffer used for statement parsingand execution. This buffer is not freed between statements. Ifyou are running complex queries a largerquery_prealloc_size valuemight be helpful in improving performance because it canreduce the need for the server to perform memory allocationduring query execution operations." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"rand_seed1", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"integer", + "max_value":"NULL", + "scope":"{NA}", + "id":"751", + "unit":"NULL", + "description":"The rand_seed1 andrand_seed2 variables exist assession variables only and can be set but not read. Thevariablesbut not their valuesare shown in theoutput of SHOW VARIABLES.The purpose of these variables is to support replication ofthe RAND() function. Forstatements that invoke RAND()the master passes two values to the slave where they are usedto seed the random number generator. The slave uses thesevalues to set the session variablesrand_seed1 andrand_seed2 so thatRAND() on the slave generatesthe same value as on the master." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"rand_seed2", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"integer", + "max_value":"NULL", + "scope":"{NA}", + "id":"752", + "unit":"NULL", + "description":"See the description forrand_seed1." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"4096", + "name":"range_alloc_block_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"4096", + "dynamic":"t", + "rank":"-1", + "summary":"Options for range_alloc_block_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{GlobalSession}", + "id":"753", + "unit":"1024", + "description":"The size of blocks that are allocated when doing rangeoptimization." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"131072", + "name":"read_buffer_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"8200", + "dynamic":"t", + "rank":"-1", + "summary":"Options for read_buffer_size", + "vartype":"integer", + "max_value":"2147479552", + "scope":"{GlobalSession}", + "id":"754", + "unit":"NULL", + "description":"Each thread that does a sequential scan for aMyISAM table allocates a buffer of thissize (in bytes) for each table it scans. If you do manysequential scans you might want to increase this value whichdefaults to 131072. The value of this variable should be amultiple of 4KB. If it is set to a value that is not amultiple of 4KB its value will be rounded down to the nearestmultiple of 4KB.This option is also used in the following context for allstorage engines:and in one other storage engine-specific way: to determine thememory block size for MEMORYtables.The maximum permissible setting forread_buffer_size is 2GB.For more information about memory use during differentoperations see Section 8.12.5.1 How MySQL Uses Memory." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"read_only", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for read_only", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"755", + "unit":"NULL", + "description":"When the read_only systemvariable is enabled the server permits no client updatesexcept from users who have theSUPER privilege. This variableis disabled by default.Even with read_only enabledthe server permits these operations:read_only exists only as aGLOBAL variable so changes to its valuerequire the SUPER privilege.Changes to read_only on amaster server are not replicated to slave servers. The valuecan be set on a slave server independent of the setting on themaster.The following conditions apply to attempts to enableread_only:" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"skip_networking", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for skip-networking", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"779", + "unit":"NULL", + "description":"This is ON if the server permits only local(non-TCP/IP) connections. On Unix local connections use aUnix socket file. On Windows local connections use a namedpipe or shared memory. This variable can be set toON with the--skip-networking option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"on", + "name":"check_function_bodies", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Check function bodies during CREATE FUNCTION.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1481", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"262144", + "name":"read_rnd_buffer_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for read_rnd_buffer_size", + "vartype":"integer", + "max_value":"2147483647", + "scope":"{GlobalSession}", + "id":"756", + "unit":"NULL", + "description":"This variable is used for reads from MyISAMtables and for any storage engine for Multi-Range Readoptimization.When reading rows from a MyISAM table insorted order following a key-sorting operation the rows areread through this buffer to avoid disk seeks. SeeSection 8.2.1.15 ORDER BY Optimization. Setting the variableto a large value can improve ORDER BYperformance by a lot. However this is a buffer allocated foreach client so you should not set the global variable to alarge value. Instead change the session variable only fromwithin those clients that need to run large queries.The maximum permissible setting forread_rnd_buffer_size is 2GB.For more information about memory use during differentoperations see Section 8.12.5.1 How MySQL Uses Memory. For informationabout Multi-Range Read optimization seeSection 8.2.1.13 Multi-Range Read Optimization." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"TRUE", + "name":"relay_log_purge", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for relay_log_purge", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"757", + "unit":"NULL", + "description":"Disables or enables automatic purging of relay log files assoon as they are not needed any more. The default value is 1(ON)." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"relay_log_space_limit", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"Options for relay_log_space_limit", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"758", + "unit":"NULL", + "description":"The maximum amount of space to use for all relay logs." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"report_host", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for report-host", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"759", + "unit":"NULL", + "description":"The value of the --report-hostoption." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"report_password", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for report-password", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"760", + "unit":"NULL", + "description":"The value of the--report-password option. Notthe same as the password used for the MySQL replication useraccount." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"report_port", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"Options for report-port", + "vartype":"integer", + "max_value":"65535", + "scope":"{Global}", + "id":"761", + "unit":"NULL", + "description":"The value of the --report-portoption." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"report_user", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for report-user", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"762", + "unit":"NULL", + "description":"The value of the --report-useroption. Not the same as the name for the MySQL replicationuser account." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"rpl_semi_sync_master_enabled", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for rpl_semi_sync_master_enabled", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"763", + "unit":"NULL", + "description":"Controls whether semisynchronous replication is enabled on themaster. To enable or disable the plugin set this variable toON or OFF (or 1 or 0)respectively. The default is OFF.This variable is available only if the master-sidesemisynchronous replication plugin is installed." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"10000", + "name":"rpl_semi_sync_master_timeout", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for rpl_semi_sync_master_timeout", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"764", + "unit":"NULL", + "description":"A value in milliseconds that controls how long the masterwaits on a commit for acknowledgment from a slave beforetiming out and reverting to asynchronous replication. Thedefault value is 10000 (10 seconds).This variable is available only if the master-sidesemisynchronous replication plugin is installed." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"32", + "name":"rpl_semi_sync_master_trace_level", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for rpl_semi_sync_master_trace_level", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"765", + "unit":"NULL", + "description":"The semisynchronous replication debug trace level on themaster. Four levels are defined:This variable is available only if the master-sidesemisynchronous replication plugin is installed." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"rpl_semi_sync_master_wait_no_slave", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for rpl_semi_sync_master_wait_no_slave", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"766", + "unit":"NULL", + "description":"With semisynchronous replication for each transaction themaster waits until timeout for acknowledgment of receipt fromsome semisynchronous slave. If no response occurs during thisperiod the master reverts to normal replication. Thisvariable controls whether the master waits for the timeout toexpire before reverting to normal replication even if theslave count drops to zero during the timeout period.If the value is ON (the default) it ispermissible for the slave count to drop to zero during thetimeout period (for example if slaves disconnect). The masterstill waits for the timeout so as long as some slavereconnects and acknowledges the transaction within the timeoutinterval semisynchronous replication continues.If the value is OFF the master reverts tonormal replication if the slave count drops to zero during thetimeout period.This variable is available only if the master-sidesemisynchronous replication plugin is installed." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"rpl_semi_sync_slave_enabled", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for rpl_semi_sync_slave_enabled", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"767", + "unit":"NULL", + "description":"Controls whether semisynchronous replication is enabled on theslave. To enable or disable the plugin set this variable toON or OFF (or 1 or 0)respectively. The default is OFF.This variable is available only if the slave-sidesemisynchronous replication plugin is installed." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"32", + "name":"rpl_semi_sync_slave_trace_level", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for rpl_semi_sync_slave_trace_level", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"768", + "unit":"NULL", + "description":"The semisynchronous replication debug trace level on theslave. Seerpl_semi_sync_master_trace_levelfor the permissible values.This variable is available only if the slave-sidesemisynchronous replication plugin is installed." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"%H:%i:%s", + "name":"time_format", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"820", + "unit":"NULL", + "description":"This variable is unused. It is deprecated as of MySQL 5.6.7and will be removed in a future MySQL release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"secure_auth", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for secure-auth", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"769", + "unit":"NULL", + "description":"If this variable is enabled the server blocks connections byclients that attempt to use accounts that have passwordsstored in the old (pre-4.1) format.Enable this variable to prevent all use of passwords employingthe old format (and hence insecure communication over thenetwork). Before MySQL 5.6.5 this variable is disabled bydefault. As of MySQL 5.6.5 it is enabled by default.Server startup fails with an error if this variable is enabledand the privilege tables are in pre-4.1 format. SeeSection B.5.2.4 Client does not support authentication protocol." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"empty", + "name":"secure_file_priv", + "deprecated":"f", + "valid_vals":"empty,dirname", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for secure-file-priv", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"770", + "unit":"NULL", + "description":"This variable is used to limit the effect of data import andexport operations such as those performed by theLOAD DATA andSELECT ... INTOOUTFILE statements and theLOAD_FILE() function. Bydefault this variable is empty. If set to the name of adirectory it limits import and export operations to work onlywith files in that directory." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"server_id", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for server-id", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{Global}", + "id":"771", + "unit":"NULL", + "description":"The server ID used in replication to give each master andslave a unique identity. This variable is set by the--server-id option. For eachserver participating in replication you should pick apositive integer in the range from 1 to2321 to act as thatserver's ID." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"private_key.pem", + "name":"sha256_password_private_key_path", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for sha256_password_private_key_path", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"772", + "unit":"NULL", + "description":"This variable is available if MySQL was compiled using OpenSSL(see Section 6.3.9.1 OpenSSL Versus yaSSL). Its value is thepath name of the RSA private key file for thesha256_password authentication plugin. Ifthe file is named as a relative path it is interpretedrelative to the server data directory. The file must be in PEMformat. Because this file stores a private key its accessmode should be restricted so that only the MySQL server canread it.For information about sha256_passwordincluding instructions for creating the RSA key files seeSection 6.4.1.4 The SHA-256 Authentication Plugin.This variable was added in MySQL 5.6.6." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"public_key.pem", + "name":"sha256_password_public_key_path", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for sha256_password_public_key_path", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"773", + "unit":"NULL", + "description":"This variable is available if MySQL was compiled using OpenSSL(see Section 6.3.9.1 OpenSSL Versus yaSSL). Its value is thepath name of the RSA public key file for thesha256_password authentication plugin. Ifthe file is named as a relative path it is interpretedrelative to the server data directory. The file must be in PEMformat. Because this file stores a public key copies can befreely distributed to client users. (Clients that explicitlyspecify a public key when connecting to the server using RSApassword encryption must use the same public key as that usedby the server.)For information about sha256_passwordincluding instructions for creating the RSA key files and howclients specify the RSA public key seeSection 6.4.1.4 The SHA-256 Authentication Plugin.This variable was added in MySQL 5.6.6." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"FALSE", + "name":"shared_memory", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for shared_memory", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"774", + "unit":"NULL", + "description":"(Windows only.) Whether the server permits shared-memoryconnections." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"MYSQL", + "name":"shared_memory_base_name", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for shared_memory_base_name", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"775", + "unit":"NULL", + "description":"(Windows only.) The name of shared memory to use forshared-memory connections. This is useful when runningmultiple MySQL instances on a single physical machine. Thedefault name is MYSQL. The name is casesensitive." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"show_old_temporals", + "deprecated":"t", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for show_old_temporals", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"776", + "unit":"NULL", + "description":"Whether SHOW CREATE TABLEoutput includes comments to flag temporal columns found to bein pre-5.6.4 format (TIMEDATETIME andTIMESTAMP columns withoutsupport for fractional seconds precision). This variable isdisabled by default. If enabled SHOWCREATE TABLE output looks like this:Output for the COLUMN_TYPE column of theINFORMATION_SCHEMA.COLUMNS tableis affected similarly.This variable was added in MySQL 5.6.24. It is deprecated andwill be removed in a future MySQL release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"skip_external_locking", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for skip_external_locking", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"777", + "unit":"NULL", + "description":"This is OFF if mysqlduses external locking (system locking) ONif external locking is disabled. This affects onlyMyISAM table access.This variable is set by the--external-locking or--skip-external-lockingoption. External locking is disabled by default.External locking affects onlyMyISAM table access. For moreinformation including conditions under which it can andcannot be used see Section 8.11.5 External Locking." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"skip_name_resolve", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for skip-name-resolve", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"778", + "unit":"NULL", + "description":"This variable is set from the value of the--skip-name-resolve option. Ifit is OFF mysqldresolves host names when checking client connections. If it isON mysqld uses only IPnumbers; in this case all Host columnvalues in the grant tables must be IP addresses orlocalhost. SeeSection 8.12.6.2 DNS Lookup Optimization and the Host Cache." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"50000", + "name":"performance_schema_max_table_instances", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_table_instances", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"864", + "unit":"NULL", + "description":"The maximum number of instrumented table objects." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"skip_show_database", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for skip-show-database", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"780", + "unit":"NULL", + "description":"This prevents people from using the SHOWDATABASES statement if they do not have theSHOW DATABASES privilege. Thiscan improve security if you have concerns about users beingable to see databases belonging to other users. Its effectdepends on the SHOW DATABASESprivilege: If the variable value is ON theSHOW DATABASES statement ispermitted only to users who have the SHOWDATABASES privilege and the statement displays alldatabase names. If the value is OFFSHOW DATABASES is permitted toall users but displays the names of only those databases forwhich the user has the SHOWDATABASES or other privilege. (Note thatany global privilege is considered aprivilege for the database.)" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"2", + "name":"slow_launch_time", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for slow_launch_time", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"781", + "unit":"NULL", + "description":"If creating a thread takes longer than this many seconds theserver increments theSlow_launch_threads statusvariable." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"slow_query_log", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for slow-query-log", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"782", + "unit":"NULL", + "description":"Whether the slow query log is enabled. The value can be 0 (orOFF) to disable the log or 1 (orON) to enable the log. The default valuedepends on whether the--slow_query_log option isgiven. The destination for log output is controlled by thelog_output system variable;if that value is NONE no log entries arewritten even if the log is enabled.Slow is determined by the value of thelong_query_time variable. SeeSection 5.4.5 The Slow Query Log." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"host_name-slow.log", + "name":"slow_query_log_file", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for slow_query_log_file", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"783", + "unit":"NULL", + "description":"The name of the slow query log file. The default value ishost_name-slow.logbut the initial value can be changed with the--slow_query_log_file option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"2097144", + "name":"sort_buffer_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"32768", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sort_buffer_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{GlobalSession}", + "id":"784", + "unit":"NULL", + "description":"Each session that must perform a sort allocates a buffer ofthis size. sort_buffer_sizeis not specific to any storage engine and applies in a generalmanner for optimization. At minimum thesort_buffer_size value mustbe large enough to accommodate fifteen tuples in the sortbuffer. Also increasing the value ofmax_sort_length may requireincreasing the value ofsort_buffer_size. For moreinformation see Section 8.2.1.15 ORDER BY OptimizationIf you see manySort_merge_passes per secondin SHOW GLOBALSTATUS output you can consider increasing thesort_buffer_size value tospeed up ORDER BY or GROUPBY operations that cannot be improved with queryoptimization or improved indexing.As of MySQL 5.6.4 the optimizer tries to work out how muchspace is needed but can allocate more up to the limit. BeforeMySQL 5.6.4 the optimizer allocates the entire buffer even ifit is not all needed. In either case setting it larger thanrequired globally will slow down most queries that sort. It isbest to increase it as a session setting and only for thesessions that need a larger size. On Linux there arethresholds of 256KB and 2MB where larger values maysignificantly slow down memory allocation so you shouldconsider staying below one of those values. Experiment to findthe best value for your workload. SeeSection B.5.3.5 Where MySQL Stores Temporary Files.The maximum permissible setting forsort_buffer_size is4GB1. Larger values are permitted for 64-bit platforms(except 64-bit Windows for which large values are truncatedto 4GB1 with a warning)." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"sql_auto_is_null", + "deprecated":"f", + "valid_vals":"1,0", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sql_auto_is_null", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"785", + "unit":"NULL", + "description":"If this variable is set to 1 then after a statement thatsuccessfully inserts an automatically generatedAUTO_INCREMENT value you can find thatvalue by issuing a statement of the following form:If the statement returns a row the value returned is the sameas if you invoked theLAST_INSERT_ID() function. Fordetails including the return value after a multiple-rowinsert see Section 12.14 Information Functions. If noAUTO_INCREMENT value was successfullyinserted the SELECT statementreturns no row.The behavior of retrieving anAUTO_INCREMENT value by using anIS NULL comparison is used bysome ODBC programs such as Access. SeeObtaining Auto-Increment Values.This behavior can be disabled by settingsql_auto_is_null to 0.The default value ofsql_auto_is_null is 0." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"sql_big_selects", + "deprecated":"f", + "valid_vals":"1,0", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sql_big_selects", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"786", + "unit":"NULL", + "description":"If set to 0 MySQL abortsSELECT statements that arelikely to take a very long time to execute (that isstatements for which the optimizer estimates that the numberof examined rows exceeds the value ofmax_join_size). This isuseful when an inadvisable WHERE statementhas been issued. The default value for a new connection is 1which permits all SELECTstatements.If you set the max_join_sizesystem variable to a value other thanDEFAULTsql_big_selects is set to 0." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"sql_buffer_result", + "deprecated":"f", + "valid_vals":"1,0", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sql_buffer_result", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"787", + "unit":"NULL", + "description":"If set to 1sql_buffer_result forcesresults from SELECT statementsto be put into temporary tables. This helps MySQL free thetable locks early and can be beneficial in cases where ittakes a long time to send results to the client. The defaultvalue is 0." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"sql_log_bin", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sql_log_bin", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Session}", + "id":"788", + "unit":"NULL", + "description":"This variable controls whether logging to the binary log isdone. The default value is 1 (do logging). To change loggingfor the current session change the session value of thisvariable. The session user must have theSUPER privilege to set thisvariable.Setting this variable to 0 prevents GTIDs from beingassigned to transactions in the binary log. If youare using GTIDs for replication this means that even whenbinary logging is later enabled once again the GTIDs writteninto the log from this point do not account for anytransactions that occurred in the meantimein effectthose transactions are lost.In MySQL 5.6 it is not possible to set@@session.sql_log_bin within a transactionor subquery. (Bug #53437)" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"sql_log_off", + "deprecated":"f", + "valid_vals":"1,0", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sql_log_off", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"789", + "unit":"NULL", + "description":"This variable controls whether logging to the general querylog is done. The default value is 0 (do logging). To changelogging for the current session change the session value ofthis variable. The session user must have theSUPER privilege to set thisoption. The default value is 0." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"''", + "name":"sql_mode", + "deprecated":"f", + "valid_vals":"ALLOW_INVALID_DATES,ANSI_QUOTES,ERROR_FOR_DIVISION_BY_ZERO,HIGH_NOT_PRECEDENCE,IGNORE_SPACE,NO_AUTO_CREATE_USER,NO_AUTO_VALUE_ON_ZERO,NO_BACKSLASH_ESCAPES,NO_DIR_IN_CREATE,NO_ENGINE_SUBSTITUTION,NO_FIELD_OPTIONS,NO_KEY_OPTIONS,NO_TABLE_OPTIONS,NO_UNSIGNED_SUBTRACTION,NO_ZERO_DATE,NO_ZERO_IN_DATE,ONLY_FULL_GROUP_BY,PAD_CHAR_TO_FULL_LENGTH,PIPES_AS_CONCAT,REAL_AS_FLOAT,STRICT_ALL_TABLES,STRICT_TRANS_TABLES", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sql-mode", + "vartype":"set", + "max_value":"NULL", + "scope":"{Global,Session}", + "id":"790", + "unit":"NULL", + "description":"The current server SQL mode which can be set dynamically. Thedefault as of MySQL 5.6.6 isNO_ENGINE_SUBSTITUTION;previously it was an empty string. For details seeSection 5.1.7 Server SQL Modes." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"sql_notes", + "deprecated":"f", + "valid_vals":"1,0", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{NA}", + "id":"791", + "unit":"NULL", + "description":"If set to 1 (the default) warnings of Notelevel increment warning_count and theserver records them. If set to 0 Notewarnings do not incrementwarning_count and the serverdoes not record them. mysqldump includesoutput to set this variable to 0 so that reloading the dumpfile does not produce warnings for events that do not affectthe integrity of the reload operation." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"sql_quote_show_create", + "deprecated":"f", + "valid_vals":"1,0", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{NA}", + "id":"792", + "unit":"NULL", + "description":"If set to 1 (the default) the server quotes identifiers forSHOW CREATE TABLE andSHOW CREATE DATABASEstatements. If set to 0 quoting is disabled. This option isenabled by default so that replication works for identifiersthat require quoting. See Section 13.7.5.12 SHOW CREATE TABLE Syntaxand Section 13.7.5.8 SHOW CREATE DATABASE Syntax." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"sql_safe_updates", + "deprecated":"f", + "valid_vals":"1,0", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{NA}", + "id":"793", + "unit":"NULL", + "description":"If set to 1 MySQL abortsUPDATE orDELETE statements that do notuse a key in the WHERE clause or aLIMIT clause. (SpecificallyUPDATE statements must have aWHERE clause that uses a key or aLIMIT clause or both.DELETE statements must haveboth.) This makes it possible to catchUPDATE orDELETE statements where keysare not used properly and that would probably change or deletea large number of rows. The default value is 0." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"18446744073709551615", + "name":"sql_select_limit", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sql_select_limit", + "vartype":"integer", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"794", + "unit":"NULL", + "description":"The maximum number of rows to return fromSELECT statements. The defaultvalue for a new connection is the maximum number of rows thatthe server permits per table. Typical default values are(232)1 or(264)1. If you have changedthe limit the default value can be restored by assigning avalue of DEFAULT.If a SELECT has aLIMIT clause the LIMITtakes precedence over the value ofsql_select_limit." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"sql_warnings", + "deprecated":"f", + "valid_vals":"1,0", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{NA}", + "id":"795", + "unit":"NULL", + "description":"This variable controls whether single-rowINSERT statements produce aninformation string if warnings occur. The default is 0. Setthe value to 1 to produce an information string." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"ssl_ca", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for ssl-ca", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"796", + "unit":"NULL", + "description":"The path to a file with a list of trusted SSL CAs." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"ssl_capath", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for ssl-capath", + "vartype":"directory name", + "max_value":"NULL", + "scope":"{Global}", + "id":"797", + "unit":"NULL", + "description":"The path to a directory that contains trusted SSL CAcertificates in PEM format." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"ssl_cert", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for ssl-cert", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"798", + "unit":"NULL", + "description":"The name of the SSL certificate file to use for establishing asecure connection." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"ssl_cipher", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for ssl-cipher", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"799", + "unit":"NULL", + "description":"A list of permissible ciphers to use for SSL encryption." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"ssl_crl", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for ssl-crl", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"800", + "unit":"NULL", + "description":"The path to a file containing certificate revocation lists inPEM format. Revocation lists work for MySQL distributionscompiled using OpenSSL (but not yaSSL). SeeSection 6.3.9.1 OpenSSL Versus yaSSL.This variable was added in MySQL 5.6.3." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"ssl_crlpath", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for ssl-crlpath", + "vartype":"directory name", + "max_value":"NULL", + "scope":"{Global}", + "id":"801", + "unit":"NULL", + "description":"The path to a directory that contains files containingcertificate revocation lists in PEM format. Revocation listswork for MySQL distributions compiled using OpenSSL (but notyaSSL). See Section 6.3.9.1 OpenSSL Versus yaSSL.This variable was added in MySQL 5.6.3." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"ssl_key", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for ssl-key", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"802", + "unit":"NULL", + "description":"The name of the SSL key file to use for establishing a secureconnection." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"InnoDB", + "name":"storage_engine", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for storage_engine", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"803", + "unit":"NULL", + "description":"The default storage engine (table type). To set the storageengine at server startup use the--default-storage-engineoption. See Section 5.1.3 Server Command Options.This variable is deprecated. Usedefault_storage_engineinstead." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"256", + "name":"stored_program_cache", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"256", + "dynamic":"t", + "rank":"-1", + "summary":"Options for stored_program_cache", + "vartype":"integer", + "max_value":"524288", + "scope":"{Global}", + "id":"804", + "unit":"NULL", + "description":"Sets a soft upper limit for the number of cached storedroutines per connection. The value of this variable isspecified in terms of the number of stored routines held ineach of the two caches maintained by the MySQL Server forrespectively stored procedures and stored functions.Whenever a stored routine is executed this cache size ischecked before the first or top-level statement in the routineis parsed; if the number of routines of the same type (storedprocedures or stored functions according to which is beingexecuted) exceeds the limit specified by this variable thecorresponding cache is flushed and memory previously allocatedfor cached objects is freed. This allows the cache to beflushed safely even when there are dependencies betweenstored routines." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"TRUE", + "name":"sync_frm", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sync_frm", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"805", + "unit":"NULL", + "description":"If this variable is set to 1 when any nontemporary table iscreated its .frm file is synchronized todisk (using fdatasync()). This is slowerbut safer in case of a crash. The default is 1." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"system_time_zone", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for system_time_zone", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"806", + "unit":"NULL", + "description":"The server system time zone. When the server begins executingit inherits a time zone setting from the machine defaultspossibly modified by the environment of the account used forrunning the server or the startup script. The value is used toset system_time_zone.Typically the time zone is specified by theTZ environment variable. It also can bespecified using the--timezone option of themysqld_safe script.The system_time_zone variablediffers from time_zone.Although they might have the same value the latter variableis used to initialize the time zone for each client thatconnects. See Section 10.6 MySQL Server Time Zone Support." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"400", + "name":"table_definition_cache", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"400", + "dynamic":"t", + "rank":"-1", + "summary":"Options for table_definition_cache", + "vartype":"integer", + "max_value":"524288", + "scope":"{Global}", + "id":"807", + "unit":"NULL", + "description":"The number of table definitions (from.frm files) that can be stored in thedefinition cache. If you use a large number of tables you cancreate a large table definition cache to speed up opening oftables. The table definition cache takes less space and doesnot use file descriptors unlike the normal table cache. Theminimum value is 400. The default value is based on thefollowing formula capped to a limit of 2000:Before MySQL 5.6.8 the default is 400.For InnoDBtable_definition_cache actsas a soft limit for the number of open table instances in theInnoDB data dictionary cache. If the numberof open table instances exceeds thetable_definition_cachesetting the LRU mechanism begins to mark table instances foreviction and eventually removes them from the data dictionarycache. The limit helps address situations in which significantamounts of memory would be used to cache rarely used tableinstances until the next server restart. The number of tableinstances with cached metadata could be higher than the limitdefined bytable_definition_cachebecause InnoDB system table instances andparent and child table instances with foreign keyrelationships are not placed on the LRU list and are notsubject to eviction from memory.Additionallytable_definition_cachedefines a soft limit for the number ofInnoDB file-per-table tablespacesthat can be open at one time which is also controlled byinnodb_open_files. If bothtable_definition_cache andinnodb_open_files are setthe highest setting is used. If neither variable is settable_definition_cache whichhas a higher default value is used. If the number of opentablespace file handles exceeds the limit defined bytable_definition_cache orinnodb_open_files the LRUmechanism searches the tablespace file LRU list for files thatare fully flushed and are not currently being extended. Thisprocess is performed each time a new tablespace is opened. Ifthere are no inactive tablespaces notablespace files are closed." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"400", + "name":"table_open_cache", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for table_open_cache", + "vartype":"integer", + "max_value":"524288", + "scope":"{Global}", + "id":"808", + "unit":"NULL", + "description":"The number of open tables for all threads. Increasing thisvalue increases the number of file descriptors thatmysqld requires. You can check whether youneed to increase the table cache by checking theOpened_tables statusvariable. See Section 5.1.6 Server Status Variables. Ifthe value of Opened_tablesis large and you do not useFLUSH TABLESoften (which just forces all tables to be closed andreopened) then you should increase the value of thetable_open_cache variable.For more information about the table cache seeSection 8.4.3.1 How MySQL Opens and Closes Tables." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1", + "name":"table_open_cache_instances", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"f", + "rank":"-1", + "summary":"Options for table_open_cache_instances", + "vartype":"integer", + "max_value":"64", + "scope":"{Global}", + "id":"809", + "unit":"NULL", + "description":"The number of open tables cache instances (default 1). Toimprove scalability by reducing contention among sessions theopen tables cache can be partitioned into several smallercache instances of sizetable_open_cache /table_open_cache_instances .A session needs to lock only one instance to access it for DMLstatements. This segments cache access among instancespermitting higher performance for operations that use thecache when there are many sessions accessing tables. (DDLstatements still require a lock on the entire cache but suchstatements are much less frequent than DML statements.)A value of 8 or 16 is recommended on systems that routinelyuse 16 or more cores.This variable was added in MySQL 5.6.6." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"thread_cache_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for thread_cache_size", + "vartype":"integer", + "max_value":"16384", + "scope":"{Global}", + "id":"810", + "unit":"NULL", + "description":"How many threads the server should cache for reuse. When aclient disconnects the client's threads are put in the cacheif there are fewer thanthread_cache_size threadsthere. Requests for threads are satisfied by reusing threadstaken from the cache if possible and only when the cache isempty is a new thread created. This variable can be increasedto improve performance if you have a lot of new connections.Normally this does not provide a notable performanceimprovement if you have a good thread implementation. Howeverif your server sees hundreds of connections per second youshould normally setthread_cache_size high enoughso that most new connections use cached threads. By examiningthe difference between theConnections andThreads_created statusvariables you can see how efficient the thread cache is. Fordetails see Section 5.1.6 Server Status Variables.The default value is based on the following formula capped toa limit of 100:Before MySQL 5.6.8 the default is 0." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"10", + "name":"performance_schema_events_stages_history_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_events_stages_history_size", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"843", + "unit":"NULL", + "description":"The number of rows per thread in theevents_stages_history table. Thisvariable was added in MySQL 5.6.3." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"10", + "name":"thread_concurrency", + "deprecated":"t", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"f", + "rank":"-1", + "summary":"Options for thread_concurrency", + "vartype":"integer", + "max_value":"512", + "scope":"{Global}", + "id":"811", + "unit":"NULL", + "description":"This variable is specific to Solaris 8 and earlier systemsfor which mysqld invokes thethr_setconcurrency() function with thevariable value. This function enables applications to give thethreads system a hint about the desired number of threads thatshould be run at the same time. Current Solaris versionsdocument this as having no effect.This variable is deprecated as of MySQL 5.6.1 and is removedin MySQL 5.7. You should remove this from MySQL configurationfiles whenever you see it unless they are for Solaris 8 orearlier." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"one-thread-per-connection", + "name":"thread_handling", + "deprecated":"f", + "valid_vals":"no-threads,one-thread-per-connection,dynamically-loaded", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for thread_handling", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"812", + "unit":"NULL", + "description":"The thread-handling model used by the server for connectionthreads. The permissible values areno-threads (the server uses a single threadto handle one connection) andone-thread-per-connection (the server usesone thread to handle each client connection).no-threads is useful for debugging underLinux; see Section 24.5 Debugging and Porting MySQL.If the thread pool plugin is enabled the server sets thethread_handling value todynamically-loaded. SeeSection 8.12.7.1 Thread Pool Components and Installation." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"thread_pool_algorithm", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"Options for thread_pool_algorithm", + "vartype":"integer", + "max_value":"1", + "scope":"{Global}", + "id":"813", + "unit":"NULL", + "description":"This variable controls which algorithm the thread pool pluginuses:" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"thread_pool_high_priority_connection", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for thread_pool_high_priority_connection", + "vartype":"integer", + "max_value":"1", + "scope":"{GlobalSession}", + "id":"814", + "unit":"NULL", + "description":"This variable affects queuing of new statements prior toexecution. If the value is 0 (false the default) statementqueuing uses both the low-priority and high-priority queues.If the value is 1 (true) queued statements always go to thehigh-priority queue.This variable was added in MySQL 5.6.10. It is available onlyif the thread pool plugin is enabled. SeeSection 8.12.7 The Thread Pool Plugin" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"thread_pool_max_unused_threads", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for thread_pool_max_unused_threads", + "vartype":"integer", + "max_value":"4096", + "scope":"{Global}", + "id":"815", + "unit":"NULL", + "description":"The maximum permitted number of unused threads in the threadpool. This variable makes it possible to limit the amount ofmemory used by sleeping threads.A value of 0 (the default) means no limit on the number ofsleeping threads. A value of Nwhere N is greater than 0 means 1consumer thread and N1reserve threads. In this case if a thread is ready to sleepbut the number of sleeping threads is already at the maximumthe thread exits rather than going to sleep.A sleeping thread is either sleeping as a consumer thread or areserve thread. The thread pool permits one thread to be theconsumer thread when sleeping. If a thread goes to sleep andthere is no existing consumer thread it will sleep as aconsumer thread. When a thread must be woken up a consumerthread is selected if there is one. A reserve thread isselected only when there is no consumer thread to wake up.This variable was added in MySQL 5.6.10. It is available onlyif the thread pool plugin is enabled. SeeSection 8.12.7 The Thread Pool Plugin" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1000", + "name":"thread_pool_prio_kickup_timer", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for thread_pool_prio_kickup_timer", + "vartype":"integer", + "max_value":"4294967294", + "scope":"{GlobalSession}", + "id":"816", + "unit":"NULL", + "description":"This variable affects statements waiting for execution in thelow-priority queue. The value is the number of millisecondsbefore a waiting statement is moved to the high-priorityqueue. The default is 1000 (1 second). The range of values is0 to 2322.This variable was added in MySQL 5.6.10. It is available onlyif the thread pool plugin is enabled. SeeSection 8.12.7 The Thread Pool Plugin" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"16", + "name":"thread_pool_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"f", + "rank":"-1", + "summary":"Options for thread_pool_size", + "vartype":"integer", + "max_value":"64", + "scope":"{Global}", + "id":"817", + "unit":"NULL", + "description":"The number of thread groups in the thread pool. This is themost important parameter controlling thread pool performance.It affects how many statements can execute simultaneously. Thedefault value is 16 with a range from 1 to 64 of permissiblevalues. If a value outside this range is specified the threadpool plugin does not load and the server writes a message tothe error log.This variable was added in MySQL 5.6.10. It is available onlyif the thread pool plugin is enabled. SeeSection 8.12.7 The Thread Pool Plugin" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"6", + "name":"thread_pool_stall_limit", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"4", + "dynamic":"t", + "rank":"-1", + "summary":"Options for thread_pool_stall_limit", + "vartype":"integer", + "max_value":"600", + "scope":"{Global}", + "id":"818", + "unit":"NULL", + "description":"This variable affects executing statements. The value is theamount of time a statement has to finish after starting toexecute before it becomes defined as stalled at which pointthe thread pool permits the thread group to begin executinganother statement. The value is measured in 10 millisecondunits so a value of 6 (the default) means 60ms. The range ofvalues is 4 to 600 (40ms to 6s). Short wait values permitthreads to start more quickly. Short values are also betterfor avoiding deadlock situations. Long wait values are usefulfor workloads that include long-running statements to avoidstarting too many new statements while the current onesexecute.This variable was added in MySQL 5.6.10. It is available onlyif the thread pool plugin is enabled. SeeSection 8.12.7 The Thread Pool Plugin" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"262144", + "name":"thread_stack", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"131072", + "dynamic":"f", + "rank":"-1", + "summary":"Options for thread_stack", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"819", + "unit":"1024", + "description":"The stack size for each thread. Many of the limits detected bythe crash-me test are dependent on thisvalue. See Section 8.13.2 The MySQL Benchmark Suite. The default of192KB (256KB for 64-bit systems) is large enough for normaloperation. If the thread stack size is too small it limitsthe complexity of the SQL statements that the server canhandle the recursion depth of stored procedures and othermemory-consuming actions." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"time_zone", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for time_zone", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"821", + "unit":"NULL", + "description":"The current time zone. This variable is used to initialize thetime zone for each client that connects. By default theinitial value of this is 'SYSTEM' (whichmeans use the value ofsystem_time_zone).The value can be specified explicitly at server startup withthe --default-time-zone option.See Section 10.6 MySQL Server Time Zone Support." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"timed_mutexes", + "deprecated":"t", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for timed_mutexes", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"822", + "unit":"NULL", + "description":"This variable is deprecated; it has no use. It will be removedin a future MySQL release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"DEFAULT", + "name":"timestamp", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for timestamp", + "vartype":"numeric", + "max_value":"NULL", + "scope":"{Session}", + "id":"823", + "unit":"NULL", + "description":"Set the time for this client. This is used to get the originaltimestamp if you use the binary log to restore rows.timestamp_value should be a Unixepoch timestamp (a value like that returned byUNIX_TIMESTAMP() not a valuein 'YYYY-MM-DD hh:mm:ss' format) orDEFAULT.Setting timestamp to aconstant value causes it to retain that value until it ischanged again. Settingtimestamp toDEFAULT causes its value to be the currentdate and time as of the time it is accessed.As of MySQL 5.6.4 timestampis a DOUBLE rather thanBIGINT because its value includes amicroseconds part.SET timestamp affects the value returned byNOW() but not bySYSDATE(). This means thattimestamp settings in the binary log have no effect oninvocations of SYSDATE(). Theserver can be started with the--sysdate-is-now option tocause SYSDATE() to be an aliasfor NOW() in which caseSET timestamp affects both functions." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"16777216", + "name":"tmp_table_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1024", + "dynamic":"t", + "rank":"-1", + "summary":"Options for tmp_table_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{GlobalSession}", + "id":"824", + "unit":"NULL", + "description":"The maximum size of internal in-memory temporary tables. Thisvariable does not apply to user-createdMEMORY tables.The actual limit is determined as the minimum oftmp_table_size andmax_heap_table_size. If anin-memory temporary table exceeds the limit MySQLautomatically converts it to an on-diskMyISAM table. Increase the value oftmp_table_size (andmax_heap_table_size ifnecessary) if you do many advanced GROUP BYqueries and you have lots of memory.You can compare the number of internal on-disk temporarytables created to the total number of internal temporarytables created by comparing the values of theCreated_tmp_disk_tables andCreated_tmp_tablesvariables.See also Section 8.4.4 Internal Temporary Table Use in MySQL." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"8192", + "name":"transaction_alloc_block_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1024", + "dynamic":"t", + "rank":"-1", + "summary":"Options for transaction_alloc_block_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{GlobalSession}", + "id":"825", + "unit":"1024", + "description":"The amount in bytes by which to increase a per-transactionmemory pool which needs memory. See the description oftransaction_prealloc_size." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"4096", + "name":"transaction_prealloc_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1024", + "dynamic":"t", + "rank":"-1", + "summary":"Options for transaction_prealloc_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{GlobalSession}", + "id":"826", + "unit":"1024", + "description":"There is a per-transaction memory pool from which varioustransaction-related allocations take memory. The initial sizeof the pool in bytes istransaction_prealloc_size.For every allocation that cannot be satisfied from the poolbecause it has insufficient memory available the pool isincreased bytransaction_alloc_block_sizebytes. When the transaction ends the pool is truncated totransaction_prealloc_sizebytes.By makingtransaction_prealloc_sizesufficiently large to contain all statements within a singletransaction you can avoid many malloc()calls." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"REPEATABLE-READ", + "name":"tx_isolation", + "deprecated":"f", + "valid_vals":"READ-UNCOMMITTED,READ-COMMITTED,REPEATABLE-READ, SERIALIZABLE ", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for tx_isolation", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"827", + "unit":"NULL", + "description":"The default transaction isolation level. Defaults toREPEATABLE-READ.This variable can be set directly or indirectly using theSET TRANSACTION statement. SeeSection 13.3.6 SET TRANSACTION Syntax. If you settx_isolation directly to anisolation level name that contains a space the name should beenclosed within quotation marks with the space replaced by adash. For example:Any unique prefix of a valid value may be used to set thevalue of this variable.The default transaction isolation level can also be set atstartup using the--transaction-isolation serveroption." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"tx_read_only", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for tx_read_only", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"828", + "unit":"NULL", + "description":"The default transaction access mode. The value can beOFF (read/write the default) orON (read only).This variable can be set directly or indirectly using theSET TRANSACTION statement. SeeSection 13.3.6 SET TRANSACTION Syntax.To set the default transaction access mode at startup use the--transaction-read-only serveroption.This variable was added in MySQL 5.6.5." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"YES", + "default_val":"1", + "name":"unique_checks", + "deprecated":"f", + "valid_vals":"1,0", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for unique_checks", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"829", + "unit":"NULL", + "description":"If set to 1 (the default) uniqueness checks for secondaryindexes in InnoDB tables are performed. Ifset to 0 storage engines are permitted to assume thatduplicate keys are not present in input data. If you know forcertain that your data does not contain uniqueness violationsyou can set this to 0 to speed up large table imports toInnoDB.Setting this variable to 0 does notrequire storage engines to ignoreduplicate keys. An engine is still permitted to check for themand issue duplicate-key errors if it detects them." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"0.5", + "name":"checkpoint_completion_target", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Time spent flushing dirty buffers during checkpoint as fraction of checkpoint interval.", + "vartype":"real", + "max_value":"1", + "scope":"{Global}", + "id":"1482", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"updatable_views_with_limit", + "deprecated":"f", + "valid_vals":"1,0", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for updatable_views_with_limit", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global,Session}", + "id":"830", + "unit":"NULL", + "description":"This variable controls whether updates to a view can be madewhen the view does not contain all columns of the primary keydefined in the underlying table if the update statementcontains a LIMIT clause. (Such updatesoften are generated by GUI tools.) An update is anUPDATE orDELETE statement. Primary keyhere means a PRIMARY KEY or aUNIQUE index in which no column can containNULL.The variable can have two values:" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"validate_user_plugins", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for validate_user_plugins", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"831", + "unit":"NULL", + "description":"If this variable is enabled (the default) the server checkseach user account and produces a warning if conditions arefound that would make the account unusable:Enabling validate_user_plugins slows downserver initialization and FLUSH PRIVILEGES.If you do not require the additional checking you can disablethis variable at startup to avoid the performance decrement.This variable was added in MySQL 5.6.11." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"INTERNAL", + "name":"version_comment", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for version_comment", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"832", + "unit":"NULL", + "description":"The CMake configuration program has aCOMPILATION_COMMENT option thatpermits a comment to be specified when building MySQL. Thisvariable contains the value of that comment. SeeSection 2.9.4 MySQL Source-Configuration Options." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"INTERNAL", + "name":"version_compile_machine", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for version_compile_machine", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"833", + "unit":"NULL", + "description":"The type of the server binary." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"INTERNAL", + "name":"version_compile_os", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for version_compile_os", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"834", + "unit":"NULL", + "description":"The type of operating system on which MySQL was built." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"28800", + "name":"wait_timeout", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for wait_timeout", + "vartype":"integer", + "max_value":"31536000", + "scope":"{GlobalSession}", + "id":"835", + "unit":"NULL", + "description":"The number of seconds the server waits for activity on anoninteractive connection before closing it.On thread startup the sessionwait_timeout value isinitialized from the globalwait_timeout value or fromthe globalinteractive_timeout valuedepending on the type of client (as defined by theCLIENT_INTERACTIVE connect option tomysql_real_connect()). Seealso interactive_timeout." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"INTERNAL", + "name":"warning_count", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"integer", + "max_value":"NULL", + "scope":"{NA}", + "id":"836", + "unit":"NULL", + "description":"The number of errors warnings and notes that resulted fromthe last statement that generated messages. This variable isread only. See Section 13.7.5.41 SHOW WARNINGS Syntax." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"auto_increment_increment", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for auto_increment_increment", + "vartype":"integer", + "max_value":"65535", + "scope":"{GlobalSession}", + "id":"837", + "unit":"NULL", + "description":"auto_increment_incrementand auto_increment_offsetare intended for use with master-to-master replication andcan be used to control the operation ofAUTO_INCREMENT columns. Both variableshave global and session values and each can assume aninteger value between 1 and 65535 inclusive. Setting thevalue of either of these two variables to 0 causes its valueto be set to 1 instead. Attempting to set the value ofeither of these two variables to an integer greater than65535 or less than 0 causes its value to be set to 65535instead. Attempting to set the value ofauto_increment_increment orauto_increment_offset to anoninteger value produces an error and the actual value ofthe variable remains unchanged.These two variables affect AUTO_INCREMENTcolumn behavior as follows:If either of these variables is changed and then new rowsinserted into a table containing anAUTO_INCREMENT column the results mayseem counterintuitive because the series ofAUTO_INCREMENT values is calculatedwithout regard to any values already present in the columnand the next value inserted is the least value in the seriesthat is greater than the maximum existing value in theAUTO_INCREMENT column. The series iscalculated like this:auto_increment_offset +N auto_increment_incrementwhere N is a positive integervalue in the series [123 ...]. For example:The values shown forauto_increment_incrementand auto_increment_offsetgenerate the series 5 + N 10 that is [515253545 ...]. The highest valuepresent in the col column prior to theINSERT is 31 and the nextavailable value in the AUTO_INCREMENTseries is 35 so the inserted values forcol begin at that point and the resultsare as shown for the SELECTquery.It is not possible to restrict the effects of these twovariables to a single table; these variables control thebehavior of all AUTO_INCREMENT columns inall tables on the MySQL server. If theglobal value of either variable is set its effects persistuntil the global value is changed or overridden by settingthe session value or until mysqld isrestarted. If the local value is set the new value affectsAUTO_INCREMENT columns for all tablesinto which new rows are inserted by the current user for theduration of the session unless the values are changedduring that session.The default value ofauto_increment_increment is1. SeeSection 17.4.1.1 Replication and AUTO_INCREMENT." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"auto_increment_offset", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for auto_increment_offset", + "vartype":"integer", + "max_value":"65535", + "scope":"{Global,Session}", + "id":"838", + "unit":"NULL", + "description":"This variable has a default value of 1. For moreinformation see the description forauto_increment_increment." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"performance_schema", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"839", + "unit":"NULL", + "description":"The value of this variable is ON orOFF to indicate whether the PerformanceSchema is enabled. By default the value isON by default as of MySQL 5.6.6 andOFF before that. At server startup you canspecify this variable with no value or a value ofON or 1 to enable it or with a value ofOFF or 0 to disable it." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"10", + "name":"performance_schema_accounts_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_accounts_size", + "vartype":"integer", + "max_value":"1048576", + "scope":"{Global}", + "id":"840", + "unit":"NULL", + "description":"The number of rows in theaccounts table. If this variableis 0 the Performance Schema does not maintain connectionstatistics in the accounts table.This variable was added in MySQL 5.6.3." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"-1", + "name":"performance_schema_digests_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"-1", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_digests_size", + "vartype":"integer", + "max_value":"1048576", + "scope":"{Global}", + "id":"841", + "unit":"NULL", + "description":"The maximum number of rows in theevents_statements_summary_by_digesttable. This variable was added in MySQL 5.6.5. If this maximumis exceeded such that a digest cannot be instrumented thePerformance Schema increments thePerformance_schema_digest_loststatus variable." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"10000", + "name":"performance_schema_events_stages_history_long_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_events_stages_history_long_size", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"842", + "unit":"NULL", + "description":"The number of rows in theevents_stages_history_long table.This variable was added in MySQL 5.6.3." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"10000", + "name":"performance_schema_events_waits_history_long_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_events_waits_history_long_size", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"846", + "unit":"NULL", + "description":"The number of rows in theevents_waits_history_long table." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"10", + "name":"performance_schema_events_waits_history_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_events_waits_history_size", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"847", + "unit":"NULL", + "description":"The number of rows per thread in theevents_waits_history table." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"10", + "name":"performance_schema_hosts_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_hosts_size", + "vartype":"integer", + "max_value":"1048576", + "scope":"{Global}", + "id":"848", + "unit":"NULL", + "description":"The number of rows in the hoststable. If this variable is 0 the Performance Schema does notmaintain connection statistics in thehosts table. This variable wasadded in MySQL 5.6.3." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"80", + "name":"performance_schema_max_cond_classes", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_cond_classes", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"849", + "unit":"NULL", + "description":"The maximum number of condition instruments." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1000", + "name":"performance_schema_max_cond_instances", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_cond_instances", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"850", + "unit":"NULL", + "description":"The maximum number of instrumented condition objects." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1024", + "name":"performance_schema_max_digest_length", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_digest_length", + "vartype":"integer", + "max_value":"1048576", + "scope":"{Global}", + "id":"851", + "unit":"NULL", + "description":"The maximum number of bytes available for computing statementdigests (seeSection 22.7 Performance Schema Statement Digests). Thisvariable is likemax_digest_length butapplies to the Performance Schema only. For more informationsee the description of that variable inSection 5.1.4 Server System VariablesThis variable was added in MySQL 5.6.26.max_digest_length. In MySQL5.6.24 and 5.6.25 usemax_digest_length instead.Before 5.6.24 the value cannot be changed." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"50", + "name":"performance_schema_max_file_classes", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_file_classes", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"852", + "unit":"NULL", + "description":"The maximum number of file instruments." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"32768", + "name":"performance_schema_max_file_handles", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_file_handles", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"853", + "unit":"NULL", + "description":"The maximum number of opened file objects.The value ofperformance_schema_max_file_handlesshould be greater than the value ofopen_files_limit:open_files_limit affects themaximum number of open file handles the server can support andperformance_schema_max_file_handlesaffects how many of these file handles can be instrumented." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"10000", + "name":"performance_schema_max_file_instances", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_file_instances", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"854", + "unit":"NULL", + "description":"The maximum number of instrumented file objects." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"200", + "name":"performance_schema_max_mutex_classes", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_mutex_classes", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"855", + "unit":"NULL", + "description":"The maximum number of mutex instruments." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1000", + "name":"performance_schema_max_mutex_instances", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_mutex_instances", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"856", + "unit":"NULL", + "description":"The maximum number of instrumented mutex objects." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"20", + "name":"performance_schema_max_rwlock_classes", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_rwlock_classes", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"857", + "unit":"NULL", + "description":"The maximum number of rwlock instruments." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1000", + "name":"performance_schema_max_rwlock_instances", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_rwlock_instances", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"858", + "unit":"NULL", + "description":"The maximum number of instrumented rwlock objects." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"10", + "name":"performance_schema_max_socket_classes", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_socket_classes", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"859", + "unit":"NULL", + "description":"The maximum number of socket instruments. This variable wasadded in MySQL 5.6.3." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1000", + "name":"performance_schema_max_socket_instances", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_socket_instances", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"860", + "unit":"NULL", + "description":"The maximum number of instrumented socket objects. Thisvariable was added in MySQL 5.6.3." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"150", + "name":"performance_schema_max_stage_classes", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_stage_classes", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"861", + "unit":"NULL", + "description":"The maximum number of stage instruments. This variable wasadded in MySQL 5.6.3." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"-1", + "name":"performance_schema_max_statement_classes", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_statement_classes", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"862", + "unit":"NULL", + "description":"The maximum number of statement instruments. The default valueis calculated at server build time based on the number ofcommands in the client/server protocol and the number of SQLstatement types supported by the server.This variable should not be changed unless to set it to 0 todisable all statement instrumentation and save all memoryassociated with it. Setting the variable to nonzero valuesother than the default has no benefit; in particular valueslarger than the default cause more memory to be allocated thenis needed.This variable was added in MySQL 5.6.3." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"100000", + "name":"performance_schema_max_table_handles", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_table_handles", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"863", + "unit":"NULL", + "description":"The maximum number of opened table objects." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1000", + "name":"performance_schema_max_thread_instances", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_thread_instances", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"866", + "unit":"NULL", + "description":"The maximum number of instrumented thread objects. The valuecontrols the size of the threadstable. If this maximum is exceeded such that a thread cannotbe instrumented the Performance Schema increments thePerformance_schema_thread_instances_loststatus variable.The max_connections systemvariable affects how many threads are run in the server.performance_schema_max_thread_instancesaffects how many of these running threads can be instrumented.The default value ofperformance_schema_max_thread_instancesis autosized based on the value ofmax_connections." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"-1", + "name":"performance_schema_session_connect_attrs_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"-1", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_session_connect_attrs_size", + "vartype":"integer", + "max_value":"1048576", + "scope":"{Global}", + "id":"867", + "unit":"NULL", + "description":"The amount of preallocated memory per thread used to holdconnection attribute strings. If the connection attributestrings are larger than the reserved storage thePerformance_schema_session_connect_attrs_loststatus variable is incremented. This variable was added inMySQL 5.6.7." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"100", + "name":"performance_schema_setup_actors_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_setup_actors_size", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"868", + "unit":"NULL", + "description":"The number of rows in thesetup_actors table." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"100", + "name":"performance_schema_setup_objects_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_setup_objects_size", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"869", + "unit":"NULL", + "description":"The number of rows in thesetup_objects table." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"10", + "name":"performance_schema_users_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_users_size", + "vartype":"integer", + "max_value":"1048576", + "scope":"{Global}", + "id":"870", + "unit":"NULL", + "description":"The number of rows in the userstable. If this variable is 0 the Performance Schema does notmaintain connection statistics in theusers table. This variable wasadded in MySQL 5.6.3." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"validate_password_dictionary_file", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for validate_password_dictionary_file", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"871", + "unit":"NULL", + "description":"The path name of the dictionary file used by thevalidate_password plugin for checkingpasswords. This variable is unavailable unless that pluginis installed.By default this variable has an empty value and dictionarychecks are not performed. To enable dictionary checks youmust set this variable to a nonempty value. If the file isnamed as a relative path it is interpreted relative to theserver data directory. Its contents should be lowercase oneword per line. Contents are treated as having a characterset of utf8. The maximum permitted filesize is 1MB.For the dictionary file to be used during password checkingthe password policy must be set to 2(STRONG); see the description of thevalidate_password_policysystem variable. Assuming that is true each substring ofthe password of length 4 up to 100 is compared to the wordsin the dictionary file. Any match causes the password to berejected. Comparisons are not case sensitive.ForVALIDATE_PASSWORD_STRENGTH()the password is checked against all policies includingSTRONG so the strength assessmentincludes the dictionary check regardless of thevalidate_password_policyvalue.Before MySQL 5.6.26 changes to the dictionary file whilethe server is running require a restart for the server torecognize the changes. As of MySQL 5.6.26validate_password_dictionary_filecan be set at runtime and assigning a value causes the namedfile to be read without a restart." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"8", + "name":"validate_password_length", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for validate_password_length", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"872", + "unit":"NULL", + "description":"The minimum number of characters that passwords checked bythe validate_password plugin must have.This variable is unavailable unless that plugin isinstalled.Thevalidate_password_lengthminimum value is a function of several other related systemvariables. As of MySQL 5.6.10 the server will not set thevalue less than the value of this expression:If the validate_password plugin adjuststhe value ofvalidate_password_lengthdue to the preceding constraint it writes a message to theerror log." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"validate_password_mixed_case_count", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for validate_password_mixed_case_count", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"873", + "unit":"NULL", + "description":"The minimum number of lowercase and uppercase charactersthat passwords checked by thevalidate_password plugin must have if thepassword policy is MEDIUM or stronger.This variable is unavailable unless that plugin isinstalled." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"validate_password_number_count", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for validate_password_number_count", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"874", + "unit":"NULL", + "description":"The minimum number of numeric (digit) characters thatpasswords checked by thevalidate_password plugin must have if thepassword policy is MEDIUM or stronger.This variable is unavailable unless that plugin isinstalled." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"validate_password_policy", + "deprecated":"f", + "valid_vals":"0,1,2", + "dbms_id":"3", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for validate_password_policy", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"875", + "unit":"NULL", + "description":"The password policy enforced by thevalidate_password plugin. This variableis unavailable unless that plugin is installed.Thevalidate_password_policyvalue can be specified using numeric values 012 or thecorresponding symbolic values LOWMEDIUM STRONG. Thefollowing table describes the tests performed for eachpolicy. For the length test the required length is thevalue of thevalidate_password_lengthsystem variable. Similarly the required values for theother tests are given by othervalidate_password_xxxvariables." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"validate_password_special_char_count", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"3", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for validate_password_special_char_count", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"876", + "unit":"NULL", + "description":"The minimum number of nonalphanumeric characters thatpasswords checked by thevalidate_password plugin must have if thepassword policy is MEDIUM or stronger.This variable is unavailable unless that plugin isinstalled." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"20", + "name":"ft_query_expansion_limit", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"Options for ft_query_expansion_limit", + "vartype":"integer", + "max_value":"1000", + "scope":"{Global}", + "id":"987", + "unit":"NULL", + "description":"The number of top matches to use for full-text searchesperformed using WITH QUERY EXPANSION." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1048576", + "name":"audit_log_buffer_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"4096", + "dynamic":"f", + "rank":"-1", + "summary":"Options for audit_log_buffer_size", + "vartype":"integer", + "max_value":"18446744073709547520", + "scope":"{Global}", + "id":"877", + "unit":"NULL", + "description":"When the audit log plugin writes events to the logasynchronously it uses a buffer to store event contentsprior to writing them. This variable controls the size ofthat buffer in bytes. The server adjusts the value to amultiple of 4096. The plugin uses a single buffer which itallocates when it initializes and removes when itterminates. The plugin allocates this buffer only if loggingis asynchronous." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ALL", + "name":"audit_log_connection_policy", + "deprecated":"f", + "valid_vals":"ALL,ERRORS,NONE", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for audit_log_connection_policy", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"878", + "unit":"NULL", + "description":"The policy controlling how the audit log plugin writesconnection events to its log file. The following table showsthe permitted values." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"audit_log_current_session", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for audit_log_current_session", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"879", + "unit":"NULL", + "description":"Whether audit logging is enabled for the current session.The session value of this variable is read only. It is setwhen the session begins based on the values of theaudit_log_include_accountsandaudit_log_exclude_accountssystem variables. The audit log plugin uses the sessionvalue to determine whether to audit events for the session.(There is a global value but the plugin does not use it.)" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"NULL", + "name":"audit_log_exclude_accounts", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for audit_log_exclude_accounts", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"880", + "unit":"NULL", + "description":"The accounts for which events should not be logged. Thevalue should be NULL or a stringcontaining a list of one or more comma-separated accountnames. For more information seeSection 6.4.4.4 Audit Log Plugin Logging Control.Modifications toaudit_log_exclude_accountsaffect only connections created subsequent to themodification not existing connections." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"audit.log", + "name":"audit_log_file", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for audit_log_file", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"881", + "unit":"NULL", + "description":"The name of the file to which the audit log plugin writesevents. The default value is audit.log.If the file name is a relative path the server interpretsit relative to the data directory. For security reasons theaudit log file should be written to a directory accessibleonly to the MySQL server and users with a legitimate reasonto view the log." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"audit_log_flush", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for audit_log_flush", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"882", + "unit":"NULL", + "description":"When this variable is set to enabled (1 orON) the audit log plugin closes andreopens its log file to flush it. (The value remainsOFF so that you need not disable itexplicitly before enabling it again to perform anotherflush.) Enabling this variable has no effect unlessaudit_log_rotate_on_size is0" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"NEW", + "name":"audit_log_format", + "deprecated":"f", + "valid_vals":"OLD,NEW", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for audit_log_format", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"883", + "unit":"NULL", + "description":"The audit log file format. Permitted values areOLD and NEW (defaultNEW). For details about each format seeSection 6.4.4.3 The Audit Log File.If you change the value ofaudit_log_format use thisprocedure to avoid writing log entries in one format to anexisting log file that contains entries in a differentformat:" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"NULL", + "name":"audit_log_include_accounts", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for audit_log_include_accounts", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"884", + "unit":"NULL", + "description":"The accounts for which events should be logged. The valueshould be NULL or a string containing alist of one or more comma-separated account names. For moreinformation seeSection 6.4.4.4 Audit Log Plugin Logging Control.Modifications toaudit_log_include_accountsaffect only connections created subsequent to themodification not existing connections." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ALL", + "name":"audit_log_policy", + "deprecated":"f", + "valid_vals":"ALL,LOGINS,QUERIES,NONE", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for audit_log_policy", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"885", + "unit":"NULL", + "description":"The policy controlling how the audit log plugin writesevents to its log file. The following table shows thepermitted values.audit_log_policy can be setonly at server startup. At runtime it is a read-onlyvariable. Two other system variablesaudit_log_connection_policyandaudit_log_statement_policyprovide finer control over logging policy and can be seteither at startup or at runtime. If you useaudit_log_policy at startupinstead of the other two variables the server uses itsvalue to set those variables. For more information about thepolicy variables and their interaction seeSection 6.4.4.4 Audit Log Plugin Logging Control." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"audit_log_rotate_on_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for audit_log_rotate_on_size", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"886", + "unit":"NULL", + "description":"If theaudit_log_rotate_on_sizevalue is greater than 0 the audit log plugin closes andreopens its log file if a write to the file causes its sizeto exceed this value. The original file is renamed to have atimestamp extension.If theaudit_log_rotate_on_sizevalue is 0 the plugin does not close and reopen its logbased on size. Instead useaudit_log_flush to closeand reopen the log on demand. In this case rename the fileexternally to the server before flushing it.For more information about audit log file rotation andtimestamp interpretation seeSection 6.4.4.4 Audit Log Plugin Logging Control.If you set this variable to a value that is not a multipleof 4096 it is truncated to the nearest multiple. (Thussetting it to a value less than 4096 has the effect ofsetting it to 0 and no rotation occurs.)" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ALL", + "name":"audit_log_statement_policy", + "deprecated":"f", + "valid_vals":"ALL,ERRORS,NONE", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for audit_log_statement_policy", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"887", + "unit":"NULL", + "description":"The policy controlling how the audit log plugin writesstatement events to its log file. The following table showsthe permitted values." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ASYNCHRONOUS", + "name":"audit_log_strategy", + "deprecated":"f", + "valid_vals":"ASYNCHRONOUS,PERFORMANCE,SEMISYNCHRONOUS,SYNCHRONOUS", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for audit_log_strategy", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"888", + "unit":"NULL", + "description":"The logging method used by the audit log plugin. Thefollowing table describes the permitted values." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"performance_schema", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"889", + "unit":"NULL", + "description":"The value of this variable is ON orOFF to indicate whether the PerformanceSchema is enabled. By default the value isON by default. At server startup you canspecify this variable with no value or a value ofON or 1 to enable it or with a value ofOFF or 0 to disable it.As of MySQL 5.7.8 even when the Performance Schema isdisabled it continues to populate theglobal_variablessession_variablesglobal_status andsession_status tables. Thisoccurs as necessary to permit the results for theSHOW VARIABLES andSHOW STATUS statements to bedrawn from those tables depending on the setting of theshow_compatibiliy_56 system variable." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"-1", + "name":"performance_schema_accounts_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"-1", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_accounts_size", + "vartype":"integer", + "max_value":"1048576", + "scope":"{Global}", + "id":"890", + "unit":"NULL", + "description":"The number of rows in theaccounts table. If this variableis 0 the Performance Schema does not maintain connectionstatistics in the accounts tableor status variable information in thestatus_by_account table." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"-1", + "name":"performance_schema_digests_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"-1", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_digests_size", + "vartype":"integer", + "max_value":"1048576", + "scope":"{Global}", + "id":"891", + "unit":"NULL", + "description":"The maximum number of rows in theevents_statements_summary_by_digesttable. If this maximum is exceeded such that a digest cannotbe instrumented the Performance Schema increments thePerformance_schema_digest_loststatus variable." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"-1", + "name":"performance_schema_events_stages_history_long_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_events_stages_history_long_size", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"892", + "unit":"NULL", + "description":"The number of rows in theevents_stages_history_long table." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"-1", + "name":"performance_schema_events_stages_history_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_events_stages_history_size", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"893", + "unit":"NULL", + "description":"The number of rows per thread in theevents_stages_history table." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"-1", + "name":"performance_schema_events_statements_history_long_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_events_statements_history_long_size", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"894", + "unit":"NULL", + "description":"The number of rows in theevents_statements_history_longtable." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"-1", + "name":"performance_schema_events_statements_history_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_events_statements_history_size", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"895", + "unit":"NULL", + "description":"The number of rows per thread in theevents_statements_history table." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"-1", + "name":"performance_schema_events_transactions_history_long_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_events_transactions_history_long_size", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"896", + "unit":"NULL", + "description":"The number of rows in theevents_transactions_history_longtable. This variable was added in MySQL 5.7.3." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"-1", + "name":"performance_schema_events_transactions_history_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_events_transactions_history_size", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"897", + "unit":"NULL", + "description":"The number of rows per thread in theevents_transactions_historytable. This variable was added in MySQL 5.7.3." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"-1", + "name":"performance_schema_events_waits_history_long_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_events_waits_history_long_size", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"898", + "unit":"NULL", + "description":"The number of rows in theevents_waits_history_long table." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"-1", + "name":"performance_schema_events_waits_history_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_events_waits_history_size", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"899", + "unit":"NULL", + "description":"The number of rows per thread in theevents_waits_history table." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"-1", + "name":"performance_schema_hosts_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"-1", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_hosts_size", + "vartype":"integer", + "max_value":"1048576", + "scope":"{Global}", + "id":"900", + "unit":"NULL", + "description":"The number of rows in the hoststable. If this variable is 0 the Performance Schema does notmaintain connection statistics in thehosts table or status variableinformation in the status_by_hosttable." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"80", + "name":"performance_schema_max_cond_classes", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_cond_classes", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"901", + "unit":"NULL", + "description":"The maximum number of condition instruments." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"-1", + "name":"performance_schema_max_cond_instances", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_cond_instances", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"902", + "unit":"NULL", + "description":"The maximum number of instrumented condition objects." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"disconnect_on_expired_password", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for disconnect_on_expired_password", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Session}", + "id":"972", + "unit":"NULL", + "description":"This variable controls how the server handles clients withexpired passwords:For more information about the interaction of client andserver settings relating to expired-password handling seeSection 6.3.7 Password Expiration and Sandbox Mode." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1024", + "name":"performance_schema_max_digest_length", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_digest_length", + "vartype":"integer", + "max_value":"1048576", + "scope":"{Global}", + "id":"903", + "unit":"NULL", + "description":"The maximum number of bytes available for computing statementdigests (seeSection 22.7 Performance Schema Statement Digests). Thisvariable is likemax_digest_length butapplies to the Performance Schema only. For more informationsee the description of that variable inSection 5.1.4 Server System VariablesThis variable was added in MySQL 5.7.8. In MySQL 5.7.6 and5.7.7 use max_digest_lengthinstead. Before 5.7.6 the value cannot be changed." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"50", + "name":"performance_schema_max_file_classes", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_file_classes", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"904", + "unit":"NULL", + "description":"The maximum number of file instruments." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"32768", + "name":"performance_schema_max_file_handles", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_file_handles", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"905", + "unit":"NULL", + "description":"The maximum number of opened file objects.The value ofperformance_schema_max_file_handlesshould be greater than the value ofopen_files_limit:open_files_limit affects themaximum number of open file handles the server can support andperformance_schema_max_file_handlesaffects how many of these file handles can be instrumented." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"-1", + "name":"performance_schema_max_file_instances", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_file_instances", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"906", + "unit":"NULL", + "description":"The maximum number of instrumented file objects." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"-1", + "name":"performance_schema_max_index_stat", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_index_stat", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"907", + "unit":"NULL", + "description":"The maximum number of indexes for which the Performance Schemamaintains statistics. If this maximum is exceeded such thatindex statistics are lost the Performance Schema incrementsthePerformance_schema_index_stat_loststatus variable. The default value is autosized using thevalue ofperformance_schema_max_table_instances.This variable was added in MySQL 5.7.6." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"250", + "name":"performance_schema_max_memory_classes", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_memory_classes", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"908", + "unit":"NULL", + "description":"The maximum number of memory instruments. This variable wasadded in MySQL 5.7.2." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"-1", + "name":"performance_schema_max_metadata_locks", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_metadata_locks", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"909", + "unit":"NULL", + "description":"The maximum number of metadata lock instruments. This valuecontrols the size of themetadata_locks table. If thismaximum is exceeded such that a metadata lock cannot beinstrumented the Performance Schema increments thePerformance_schema_metadata_lock_loststatus variable.This variable was added in MySQL 5.7.3." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"200", + "name":"performance_schema_max_mutex_classes", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_mutex_classes", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"910", + "unit":"NULL", + "description":"The maximum number of mutex instruments." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"-1", + "name":"performance_schema_max_mutex_instances", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_mutex_instances", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"911", + "unit":"NULL", + "description":"The maximum number of instrumented mutex objects." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"-1", + "name":"performance_schema_max_prepared_statements_instances", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_prepared_statements_instances", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"912", + "unit":"NULL", + "description":"The maximum number of rows in theprepared_statements_instancestable. If this maximum is exceeded such that a preparedstatement cannot be instrumented the Performance Schemaincrements thePerformance_schema_prepared_statements_loststatus variable. The default value of this variable isautosized based on the value of themax_prepared_stmt_countsystem variable.This variable was added in MySQL 5.7.4." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"30", + "name":"performance_schema_max_rwlock_classes", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_rwlock_classes", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"913", + "unit":"NULL", + "description":"The maximum number of rwlock instruments." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"5000", + "name":"performance_schema_max_program_instances", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_program_instances", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"914", + "unit":"NULL", + "description":"The maximum number of stored programs for which thePerformance Schema maintains statistics. If this maximum isexceeded the Performance Schema increments thePerformance_schema_program_loststatus variable.This variable was added in MySQL 5.7.2." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"-1", + "name":"performance_schema_max_rwlock_instances", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_rwlock_instances", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"915", + "unit":"NULL", + "description":"The maximum number of instrumented rwlock objects." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"10", + "name":"performance_schema_max_socket_classes", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_socket_classes", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"916", + "unit":"NULL", + "description":"The maximum number of socket instruments." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"-1", + "name":"performance_schema_max_socket_instances", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_socket_instances", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"917", + "unit":"NULL", + "description":"The maximum number of instrumented socket objects." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"4", + "name":"div_precision_increment", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for div_precision_increment", + "vartype":"integer", + "max_value":"30", + "scope":"{GlobalSession}", + "id":"973", + "unit":"NULL", + "description":"This variable indicates the number of digits by which toincrease the scale of the result of division operationsperformed with the/ operator.The default value is 4. The minimum and maximum values are 0and 30 respectively. The following example illustrates theeffect of increasing the default value." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1024", + "name":"performance_schema_max_sql_text_length", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_sql_text_length", + "vartype":"integer", + "max_value":"1048576", + "scope":"{Global}", + "id":"918", + "unit":"NULL", + "description":"The maximum number of bytes used to store SQL statements inthe SQL_TEXT column of theevents_statements_currentevents_statements_history andevents_statements_history_longstatement event tables. Any bytes in excess ofperformance_schema_max_sql_text_lengthare discarded and do not appear in theSQL_TEXT column. Statements differing onlyafter that many initial bytes are indistinguishable in thiscolumn.Decreasing theperformance_schema_max_sql_text_lengthvalue reduces memory use but causes more statements to becomeindistinguishable if they differ only at the end. Increasingthe value increases memory use but permits longer statementsto be distinguished.This variable was added in MySQL 5.7.6." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"150", + "name":"performance_schema_max_stage_classes", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_stage_classes", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"919", + "unit":"NULL", + "description":"The maximum number of stage instruments." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"-1", + "name":"performance_schema_max_statement_classes", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_statement_classes", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"920", + "unit":"NULL", + "description":"The maximum number of statement instruments. The default valueis calculated at server build time based on the number ofcommands in the client/server protocol and the number of SQLstatement types supported by the server.This variable should not be changed unless to set it to 0 todisable all statement instrumentation and save all memoryassociated with it. Setting the variable to nonzero valuesother than the default has no benefit; in particular valueslarger than the default cause more memory to be allocated thenis needed." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"10", + "name":"performance_schema_max_statement_stack", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_statement_stack", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"921", + "unit":"NULL", + "description":"The maximum depth of nested stored program calls for which thePerformance Schema maintains statistics. When this maximum isexceeded the Performance Schema increments thePerformance_schema_nested_statement_loststatus variable for each stored program statement executed.This variable was added in MySQL 5.7.2." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"-1", + "name":"performance_schema_max_table_handles", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_table_handles", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"922", + "unit":"NULL", + "description":"The maximum number of opened table objects. This valuecontrols the size of thetable_handles table. If thismaximum is exceeded such that a table handle cannot beinstrumented the Performance Schema increments thePerformance_schema_table_handles_loststatus variable." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"-1", + "name":"performance_schema_max_table_instances", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_table_instances", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"923", + "unit":"NULL", + "description":"The maximum number of instrumented table objects." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"-1", + "name":"performance_schema_max_table_lock_stat", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_table_lock_stat", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"924", + "unit":"NULL", + "description":"The maximum number of tables for which the Performance Schemamaintains lock statistics. If this maximum is exceeded suchthat table lock statistics are lost the Performance Schemaincrements thePerformance_schema_table_lock_stat_loststatus variable.This variable was added in MySQL 5.7.6." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"50", + "name":"performance_schema_max_thread_classes", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_thread_classes", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"925", + "unit":"NULL", + "description":"The maximum number of thread instruments." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"-1", + "name":"performance_schema_max_thread_instances", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_max_thread_instances", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"926", + "unit":"NULL", + "description":"The maximum number of instrumented thread objects. The valuecontrols the size of the threadstable. If this maximum is exceeded such that a thread cannotbe instrumented the Performance Schema increments thePerformance_schema_thread_instances_loststatus variable.The max_connections systemvariable affects how many threads can run in the server.performance_schema_max_thread_instancesaffects how many of these running threads can be instrumented.The variables_by_thread andstatus_by_thread tables containsystem and status variable information information only aboutforeground threads. If not all threads are instrumented by thePerformance Schema this table will miss some rows. In thiscase thePerformance_schema_thread_instances_loststatus variable will be greater than zero." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"-1", + "name":"performance_schema_session_connect_attrs_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"-1", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_session_connect_attrs_size", + "vartype":"integer", + "max_value":"1048576", + "scope":"{Global}", + "id":"927", + "unit":"NULL", + "description":"The amount of preallocated memory per thread used to holdconnection attribute strings. If the connection attributestrings are larger than the reserved storage thePerformance_schema_session_connect_attrs_loststatus variable is incremented." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"100", + "name":"performance_schema_setup_actors_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_setup_actors_size", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"928", + "unit":"NULL", + "description":"The number of rows in thesetup_actors table." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"100", + "name":"performance_schema_setup_objects_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_setup_objects_size", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"929", + "unit":"NULL", + "description":"The number of rows in thesetup_objects table." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"-1", + "name":"performance_schema_users_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"-1", + "dynamic":"f", + "rank":"-1", + "summary":"Options for performance_schema_users_size", + "vartype":"integer", + "max_value":"1048576", + "scope":"{Global}", + "id":"930", + "unit":"NULL", + "description":"The number of rows in the userstable. If this variable is 0 the Performance Schema does notmaintain connection statistics in theusers table or status variableinformation in the status_by_usertable." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"autocommit", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for autocommit", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"931", + "unit":"NULL", + "description":"The autocommit mode. If set to 1 all changes to a table takeeffect immediately. If set to 0 you must useCOMMIT to accept a transactionor ROLLBACKto cancel it. If autocommitis 0 and you change it to 1 MySQL performs an automaticCOMMIT of any open transaction.Another way to begin a transaction is to use aSTARTTRANSACTION orBEGINstatement. See Section 13.3.1 START TRANSACTION COMMIT and ROLLBACK Syntax.By default client connections begin withautocommit set to 1. To causeclients to begin with a default of 0 set the globalautocommit value by startingthe server with the--autocommit=0 option. To setthe variable using an option file include these lines:" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"TRUE", + "name":"automatic_sp_privileges", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for automatic_sp_privileges", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"932", + "unit":"NULL", + "description":"When this variable has a value of 1 (the default) the serverautomatically grants theEXECUTE andALTER ROUTINE privileges to thecreator of a stored routine if the user cannot alreadyexecute and alter or drop the routine. (TheALTER ROUTINE privilege isrequired to drop the routine.) The server also automaticallydrops those privileges from the creator when the routine isdropped. Ifautomatic_sp_privileges is 0the server does not automatically add or drop theseprivileges.The creator of a routine is the account used to execute theCREATE statement for it. This might not bethe same as the account named as theDEFINER in the routine definition.See also Section 20.2.2 Stored Routines and MySQL Privileges." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"auto_generate_certs", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for auto_generate_certs", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"933", + "unit":"NULL", + "description":"This variable is available if the server was compiled usingOpenSSL (see Section 6.3.11.1 OpenSSL Versus yaSSL). Itcontrols whether the server autogenerates SSL key andcertificate files in the data directory if they do notalready exist.At startup the server automatically generates server-side andclient-side SSL certificate and key files in the datadirectory if theauto_generate_certs systemvariable is enabled no SSL options other than--ssl are specified and theserver-side SSL files are missing from the data directory.These files enable secure client connections using SSL; seeSection 6.3.11.4 Configuring MySQL to Use Secure Connections.For more information about SSL file autogeneration includingfile names and characteristics seeSection 6.3.12.1 Creating SSL and RSA Certificates and Keys using MySQLThesha256_password_auto_generate_rsa_keyssystem variable is related but controls autogeneration of RSAkey-pair files needed for secure password exchange using RSAover unencypted connections." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"avoid_temporal_upgrade", + "deprecated":"t", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for avoid_temporal_upgrade", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"934", + "unit":"NULL", + "description":"This variable controls whether ALTERTABLE implicitly upgrades temporal columns found tobe in pre-5.6.4 format (TIMEDATETIME andTIMESTAMP columns withoutsupport for fractional seconds precision). Upgrading suchcolumns requires a table rebuild which prevents any use offast alterations that might otherwise apply to the operationto be performed.This variable is disabled by default. Enabling it causesALTER TABLE not to rebuildtemporal columns and thereby be able to take advantage ofpossible fast alterations.This variable is deprecated and will be removed in a futureMySQL release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"-1", + "name":"back_log", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"f", + "rank":"-1", + "summary":"Options for back_log", + "vartype":"integer", + "max_value":"65535", + "scope":"{Global}", + "id":"935", + "unit":"NULL", + "description":"The number of outstanding connection requests MySQL can have.This comes into play when the main MySQL thread gets very manyconnection requests in a very short time. It then takes sometime (although very little) for the main thread to check theconnection and start a new thread. Theback_log value indicates howmany requests can be stacked during this short time beforeMySQL momentarily stops answering new requests. You need toincrease this only if you expect a large number of connectionsin a short period of time.In other words this value is the size of the listen queue forincoming TCP/IP connections. Your operating system has its ownlimit on the size of this queue. The manual page for the Unixlisten() system call should have moredetails. Check your OS documentation for the maximum value forthis variable. back_logcannot be set higher than your operating system limit.The default value is based on the following formula capped toa limit of 900:" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"basedir", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for basedir", + "vartype":"directory name", + "max_value":"NULL", + "scope":"{Global}", + "id":"936", + "unit":"NULL", + "description":"The MySQL installation base directory. This variable can beset with the --basedir option.Relative path names for other variables usually are resolvedrelative to the base directory." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"big_tables", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for big-tables", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"937", + "unit":"NULL", + "description":"If set to 1 all temporary tables are stored on disk ratherthan in memory. This is a little slower but the errorThe table tbl_name isfull does not occur forSELECT operations that requirea large temporary table. The default value for a newconnection is 0 (use in-memory temporary tables). Normallyyou should never need to set this variable because in-memorytables are automatically converted to disk-based tables asrequired." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"*", + "name":"bind_address", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for bind-address", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"938", + "unit":"NULL", + "description":"The value of the --bind-addressoption.This variable has no effect for the embedded server(libmysqld) and as of MySQL 5.7.2 is nolonger visible within the embedded server." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"3", + "name":"checkpoint_segments", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the maximum distance in log segments between automatic WAL checkpoints.", + "vartype":"integer", + "max_value":"2147483647", + "scope":"{Global}", + "id":"1483", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"aes-128-ecb", + "name":"block_encryption_mode", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for block_encryption_mode", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"939", + "unit":"NULL", + "description":"This variable controls the block encryption mode forblock-based algorithms such as AES. It affects encryption forAES_ENCRYPT() andAES_DECRYPT().block_encryption_mode takes avalue inaes-keylen-modeformat where keylen is the keylength in bits and mode is theencryption mode. The value is not case sensitive. Permittedkeylen values are 128192 and256. Permitted encryption modes depend on whether MySQL wascompiled using OpenSSL or yaSSL:For example this statement causes the AES encryptionfunctions to use a key length of 256 bits and the CBC mode:An error occurs for attempts to setblock_encryption_mode to avalue containing an unsupported key length or a mode that theSSL library does not support." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"8388608", + "name":"bulk_insert_buffer_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for bulk_insert_buffer_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{GlobalSession}", + "id":"940", + "unit":"NULL", + "description":"MyISAM uses a special tree-like cache tomake bulk inserts faster forINSERT ...SELECT INSERT ... VALUES (...) (...)... andLOAD DATAINFILE when adding data to nonempty tables. Thisvariable limits the size of the cache tree in bytes perthread. Setting it to 0 disables this optimization. Thedefault value is 8MB." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"CHARSET", + "name":"character_set_client", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for character_set_client", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"941", + "unit":"NULL", + "description":"The character set for statements that arrive from the client.The session value of this variable is set using the characterset requested by the client when the client connects to theserver. (Many clients support a--default-character-set option to enable thischaracter set to be specified explicitly. See alsoSection 10.1.5 Connection Character Sets and Collations.) The global value of thevariable is used to set the session value in cases when theclient-requested value is unknown or not available or theserver is configured to ignore client requests:ucs2 utf16utf16le and utf32cannot be used as a client character set which means thatthey also do not work for SET NAMES orSET CHARACTER SET." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"CHARSET", + "name":"character_set_connection", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for character_set_connection", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"942", + "unit":"NULL", + "description":"The character set used for literals that do not have acharacter set introducer and for number-to-string conversion." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"CHARSET", + "name":"character_set_database", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for character_set_database", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"943", + "unit":"NULL", + "description":"The character set used by the default database. The serversets this variable whenever the default database changes. Ifthere is no default database the variable has the same valueas character_set_server.The globalcharacter_set_database andcollation_database systemvariables are deprecated as of MySQL 5.7.6 and will be removedin a future version of MySQL.Assigning a value to the sessioncharacter_set_database andcollation_database systemvariables is deprecated as of MySQL 5.7.6 and assignmentsproduce a warning. The session variables will become read onlyin a future version of MySQL and assignments will produce anerror. It will remain possible to access the session variablesto determine the database character set and collation for thedefault database." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"binary", + "name":"character_set_filesystem", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for character-set-filesystem", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"944", + "unit":"NULL", + "description":"The file system character set. This variable is used tointerpret string literals that refer to file names such as inthe LOAD DATAINFILE andSELECT ... INTOOUTFILE statements and theLOAD_FILE() function. Such filenames are converted fromcharacter_set_client tocharacter_set_filesystembefore the file opening attempt occurs. The default value isbinary which means that no conversionoccurs. For systems on which multibyte file names arepermitted a different value may be more appropriate. Forexample if the system represents file names using UTF-8 setcharacter_set_filesystem to'utf8'." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"CHARSET", + "name":"character_set_results", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for character_set_results", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"945", + "unit":"NULL", + "description":"The character set used for returning query results such asresult sets or error messages to the client." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"latin1", + "name":"character_set_server", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for character-set-server", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"946", + "unit":"NULL", + "description":"The server's default character set." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"utf8", + "name":"character_set_system", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for character_set_system", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"947", + "unit":"NULL", + "description":"The character set used by the server for storing identifiers.The value is always utf8." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"character_sets_dir", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for character-sets-dir", + "vartype":"directory name", + "max_value":"NULL", + "scope":"{Global}", + "id":"948", + "unit":"NULL", + "description":"The directory where character sets are installed." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"check_proxy_users", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for check_proxy_users", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"949", + "unit":"NULL", + "description":"This variable controls whether the server performs proxy usermapping for authentication plugins that request it. Withcheck_proxy_users enabled itmay also be necessary to enable plugin-specific systemvariables to take advantage of server proxy user mappingsupport:For information about user proxying seeSection 6.3.9 Proxy Users.This variable was added in MySQL 5.7.7. Before 5.7.7 proxyuser mapping is available only for plugins that implement itfor themselves." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"300", + "name":"checkpoint_timeout", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"30", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the maximum time between automatic WAL checkpoints.", + "vartype":"integer", + "max_value":"3600", + "scope":"{Global}", + "id":"1484", + "unit":"s", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"COLLATION", + "name":"collation_database", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for collation_database", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"951", + "unit":"NULL", + "description":"The collation used by the default database. The server setsthis variable whenever the default database changes. If thereis no default database the variable has the same value ascollation_server.The globalcharacter_set_database andcollation_database systemvariables are deprecated as of MySQL 5.7.6 and will be removedin a future version of MySQL.Assigning a value to the sessioncharacter_set_database andcollation_database systemvariables is deprecated as of MySQL 5.7.6 and assignmentsproduce a warning. The session variables will become read onlyin a future version of MySQL and assignments will produce anerror. It will remain possible to access the session variablesto determine the database character set and collation for thedefault database." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"latin1_swedish_ci", + "name":"collation_server", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for collation-server", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"952", + "unit":"NULL", + "description":"The server's default collation." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"NO_CHAIN", + "name":"completion_type", + "deprecated":"f", + "valid_vals":"NO_CHAIN,CHAIN,RELEASE,0,1,2", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for completion_type", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"953", + "unit":"NULL", + "description":"The transaction completion type. This variable can take thevalues shown in the following table. The variable can beassigned using either the name values or corresponding integervalues.completion_type affectstransactions that begin withSTARTTRANSACTION orBEGIN andend with COMMIT orROLLBACK. Itdoes not apply to implicit commits resulting from execution ofthe statements listed in Section 13.3.3 Statements That Cause an Implicit Commit. Italso does not apply forXACOMMITXAROLLBACK or whenautocommit=1." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"AUTO", + "name":"concurrent_insert", + "deprecated":"f", + "valid_vals":"NEVER,AUTO,ALWAYS,0,1,2", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for concurrent_insert", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"954", + "unit":"NULL", + "description":"If AUTO (the default) MySQL permitsINSERT andSELECT statements to runconcurrently for MyISAM tables that have nofree blocks in the middle of the data file. If you startmysqld with--skip-newthis variable is set to NEVER.This variable can take the values shown in the followingtable. The variable can be assigned using either the namevalues or corresponding integer values.See also Section 8.11.3 Concurrent Inserts." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"10", + "name":"connect_timeout", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"2", + "dynamic":"t", + "rank":"-1", + "summary":"Options for connect_timeout", + "vartype":"integer", + "max_value":"31536000", + "scope":"{Global}", + "id":"955", + "unit":"NULL", + "description":"The number of seconds that the mysqldserver waits for a connect packet before responding withBad handshake. The default value is 10seconds.Increasing theconnect_timeout value mighthelp if clients frequently encounter errors of the formLost connection to MySQL server at'XXX' system error:errno." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"core_file", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for core_file", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"956", + "unit":"NULL", + "description":"Whether to write a core file if the server crashes. Thisvariable is set by the--core-file option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"datadir", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for datadir", + "vartype":"directory name", + "max_value":"NULL", + "scope":"{Global}", + "id":"957", + "unit":"NULL", + "description":"The MySQL data directory. This variable can be set with the--datadir option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"%Y-%m-%d", + "name":"date_format", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"958", + "unit":"NULL", + "description":"This variable is unused. It is deprecated and will be removedin a future MySQL release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"%Y-%m-%d %H:%i:%s", + "name":"datetime_format", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"959", + "unit":"NULL", + "description":"This variable is unused. It is deprecated and will be removedin a future MySQL release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"d:t:i:o/tmp/mysqld.trace", + "name":"debug", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for debug", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"960", + "unit":"NULL", + "description":"This variable indicates the current debugging settings. It isavailable only for servers built with debugging support. Theinitial value comes from the value of instances of the--debug option given at serverstartup. The global and session values may be set at runtime;the SUPER privilege isrequired even for the session value.Assigning a value that begins with + or- cause the value to added to or subtractedfrom the current value:For more information see Section 25.5.3 The DBUG Package." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"debug_sync", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for debug_sync", + "vartype":"string", + "max_value":"NULL", + "scope":"{Session}", + "id":"961", + "unit":"NULL", + "description":"This variable is the user interface to the Debug Syncfacility. Use of Debug Sync requires that MySQL be configuredwith the -DENABLE_DEBUG_SYNC=1CMake option (seeSection 2.9.4 MySQL Source-Configuration Options). If Debug Syncis not compiled in this system variable is not available.The global variable value is read only and indicates whetherthe facility is enabled. By default Debug Sync is disabledand the value of debug_syncis OFF. If the server is started with--debug-sync-timeout=Nwhere N is a timeout value greaterthan 0 Debug Sync is enabled and the value ofdebug_sync is ON -current signal followed by the signal name. AlsoN becomes the default timeout forindividual synchronization points.The session value can be read by any user and will have thesame value as the global variable. The session value can beset by users that have theSUPER privilege to controlsynchronization points.For a description of the Debug Sync facility and how to usesynchronization points seeMySQLInternals: Test Synchronization." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"end_markers_in_json", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for end_markers_in_json", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"974", + "unit":"NULL", + "description":"Whether optimizer JSON output should add end markers." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"mysql_native_password", + "name":"default_authentication_plugin", + "deprecated":"f", + "valid_vals":"mysql_native_password,sha256_password", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for default_authentication_plugin", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"962", + "unit":"NULL", + "description":"The default authentication plugin. Permitted values aremysql_native_password (use MySQL nativepasswords; this is the default) andsha256_password (use SHA-256 passwords).For more information about these plugins seeSection 6.4.1.1 The Native Authentication Plugin andSection 6.4.1.4 The SHA-256 Authentication Plugin.The value ofdefault_authentication_pluginaffects these aspects of server operation:This variable was added in MySQL 5.7.2. Earlier in MySQL5.7 use the--default-authentication-plugincommand-line option instead which is used the same way atserver startup but cannot be accessed at runtime." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"360", + "name":"default_password_lifetime", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for default_password_lifetime", + "vartype":"integer", + "max_value":"65535", + "scope":"{Global}", + "id":"963", + "unit":"NULL", + "description":"This variable defines the global automatic password expirationpolicy. It applies to accounts that use MySQL built-inauthentication methods (accounts that use an authenticationplugin of mysql_native_passwordmysql_old_password orsha256_password).The defaultdefault_password_lifetimevalue is 0 which disables automatic password expiration. Ifthe value ofdefault_password_lifetime isa positive integer N it indicatesthe permitted password lifetime; passwords must be changedevery N days.The global password expiration policy can be overridden asdesired for individual accounts using the ALTERUSER statement. SeeSection 6.3.6 Password Expiration Policy." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"InnoDB", + "name":"default_storage_engine", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for default-storage-engine", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"964", + "unit":"NULL", + "description":"The default storage engine. This variable sets the storageengine for permanent tables only. To set the storage enginefor TEMPORARY tables set thedefault_tmp_storage_enginesystem variable.To see which storage engines are available and enabled usethe SHOW ENGINES statement orquery the INFORMATION_SCHEMAENGINES table.default_storage_engine shouldbe used in preference tostorage_engine which isdeprecated and was removed in MySQL 5.7.5.If you disable the default storage engine at server startupyou must set the default engine for both permanent andTEMPORARY tables to a different engine orthe server will not start." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"InnoDB", + "name":"default_tmp_storage_engine", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for default_tmp_storage_engine", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"965", + "unit":"NULL", + "description":"The default storage engine for TEMPORARYtables (created withCREATE TEMPORARYTABLE). To set the storage engine for permanenttables set thedefault_storage_engine systemvariable. Also see the discussion of that variable regardingpossible values.If you disable the default storage engine at server startupyou must set the default engine for both permanent andTEMPORARY tables to a different engine orthe server will not start." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"default_week_format", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for default_week_format", + "vartype":"integer", + "max_value":"7", + "scope":"{GlobalSession}", + "id":"966", + "unit":"NULL", + "description":"The default mode value to use for theWEEK() function. SeeSection 12.7 Date and Time Functions." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"ON", + "name":"delay_key_write", + "deprecated":"f", + "valid_vals":"ON,OFF,ALL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for delay-key-write", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"967", + "unit":"NULL", + "description":"This option applies only to MyISAM tables.It can have one of the following values to affect handling ofthe DELAY_KEY_WRITE table option that canbe used in CREATE TABLEstatements.If DELAY_KEY_WRITE is enabled for a tablethe key buffer is not flushed for the table on every indexupdate but only when the table is closed. This speeds upwrites on keys a lot but if you use this feature you shouldadd automatic checking of all MyISAM tablesby starting the server with the--myisam-recover-options option(for example--myisam-recover-options=BACKUPFORCE).See Section 5.1.3 Server Command Options andSection 15.2.1 MyISAM Startup Options." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"100", + "name":"delayed_insert_limit", + "deprecated":"t", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for delayed_insert_limit", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"968", + "unit":"NULL", + "description":"This system variable is deprecated (becauseDELAYED inserts are not supported) andwill be removed in a future release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"300", + "name":"delayed_insert_timeout", + "deprecated":"t", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for delayed_insert_timeout", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"969", + "unit":"NULL", + "description":"This system variable is deprecated (becauseDELAYED inserts are not supported) andwill be removed in a future release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1000", + "name":"delayed_queue_size", + "deprecated":"t", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for delayed_queue_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"970", + "unit":"NULL", + "description":"This system variable is deprecated (becauseDELAYED inserts are not supported) andwill be removed in a future release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"empty string", + "name":"disabled_storage_engines", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for disabled_storage_engines", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"971", + "unit":"NULL", + "description":"This variable indicates which storage engines cannot be usedto create tables or tablespaces. For example to prevent newMyISAM or FEDERATEDtables from being created start the server with these linesin the server option file:By defaultdisabled_storage_engines isempty (no engines disabled) but it can be set to acomma-separated list of one or more engines (not casesensitive). Any engine named in the value cannot be used tocreate tables or tablespaces with CREATETABLE or CREATETABLESPACE and cannot be used withALTER TABLE ...ENGINE orALTERTABLESPACE ... ENGINE to change the storage engineof existing tables or tablespaces. Attempts to do so result inan ER_DISABLED_STORAGE_ENGINEerror.disabled_storage_engines doesnot restrict other DDL statements for existing tables such asCREATE INDEXTRUNCATE TABLEANALYZE TABLEDROP TABLE orDROP TABLESPACE. This permits asmooth transition so that existing tables or tablespaces thatuse a disabled engine can be migrated to a permitted engine bymeans such asALTER TABLE ...ENGINE permitted_engine.It is permitted to set thedefault_storage_engine ordefault_tmp_storage_enginesystem variable to a storage engine that is disabled. Thiscould cause applications to behave erratically or failalthough that might be a useful technique in a developmentenvironment for identifying applications that use disabledengines so that they can be modified.disabled_storage_engines isdisabled and has no effect if the server is started with anyof these options: --bootstrap--initialize--initialize-insecure--skip-grant-tables." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"10", + "name":"eq_range_index_dive_limit", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for eq_range_index_dive_limit", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{GlobalSession}", + "id":"975", + "unit":"NULL", + "description":"This variable indicates the number of equality ranges in anequality comparison condition when the optimizer should switchfrom using index dives to index statistics in estimating thenumber of qualifying rows. It applies to evaluation ofexpressions that have either of these equivalent forms wherethe optimizer uses a nonunique index to look upcol_name values:In both cases the expression containsN equality ranges. The optimizercan make row estimates using index dives or index statistics.If eq_range_index_dive_limitis greater than 0 the optimizer uses existing indexstatistics instead of index dives if there areeq_range_index_dive_limit ormore equality ranges. Thus to permit use of index dives forup to N equality ranges seteq_range_index_dive_limit toN + 1. To disable use of indexstatistics and always use index dives regardless ofN seteq_range_index_dive_limit to0For more information seeSection 8.2.1.3.3 Equality Range Optimization of Many-Valued Comparisons.To update table index statistics for best estimates useANALYZE TABLE." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"INTERNAL", + "name":"error_count", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"integer", + "max_value":"NULL", + "scope":"{NA}", + "id":"976", + "unit":"NULL", + "description":"The number of errors that resulted from the last statementthat generated messages. This variable is read only. SeeSection 13.7.5.17 SHOW ERRORS Syntax." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"event_scheduler", + "deprecated":"f", + "valid_vals":"ON,OFF,DISABLED", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for event-scheduler", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"977", + "unit":"NULL", + "description":"This variable indicates the status of the Event Scheduler;possible values are ONOFF and DISABLED withthe default being OFF. This variable andits effects on the Event Scheduler's operation are discussedin greater detail in theOverview sectionof the Events chapter." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"expire_logs_days", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for expire_logs_days", + "vartype":"integer", + "max_value":"99", + "scope":"{Global}", + "id":"978", + "unit":"NULL", + "description":"The number of days for automatic binary log file removal. Thedefault is 0 which means no automatic removal.Possible removals happen at startup and when the binary log isflushed. Log flushing occurs as indicated inSection 5.4 MySQL Server Logs.To remove binary log files manually use thePURGE BINARY LOGS statement.See Section 13.4.1.1 PURGE BINARY LOGS Syntax." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"FALSE", + "name":"explicit_defaults_for_timestamp", + "deprecated":"t", + "valid_vals":"TRUE,FALSE", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for explicit_defaults_for_timestamp", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global,Session}", + "id":"979", + "unit":"NULL", + "description":"In MySQL the TIMESTAMP datatype differs in nonstandard ways from other data types:Those nonstandard behaviors remain the default forTIMESTAMP but as of MySQL 5.6.6are deprecated and this warning appears at startup:As indicated by the warning to turn off the nonstandardbehaviors enable theexplicit_defaults_for_timestampsystem variable at server startup. With this variable enabledthe server handles TIMESTAMP asfollows instead:" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"external_user", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for external_user", + "vartype":"string", + "max_value":"NULL", + "scope":"{Session}", + "id":"980", + "unit":"NULL", + "description":"The external user name used during the authentication processas set by the plugin used to authenticate the client. Withnative (built-in) MySQL authentication or if the plugin doesnot set the value this variable is NULL.See Section 6.3.9 Proxy Users." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"flush", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for flush", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"981", + "unit":"NULL", + "description":"If ON the server flushes (synchronizes)all changes to disk after each SQL statement. Normally MySQLdoes a write of all changes to disk only after each SQLstatement and lets the operating system handle thesynchronizing to disk. See Section B.5.3.3 What to Do If MySQL Keeps Crashing. Thisvariable is set to ON if you startmysqld with the--flush option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"flush_time", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for flush_time", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"982", + "unit":"NULL", + "description":"If this is set to a nonzero value all tables are closed everyflush_time seconds to free upresources and synchronize unflushed data to disk. This optionis best used only on systems with minimal resources." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"foreign_key_checks", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{NA}", + "id":"983", + "unit":"NULL", + "description":"If set to 1 (the default) foreign key constraints forInnoDB tables are checked. If set to 0foreign key constraints are ignored with a couple ofexceptions. When re-creating a table that was dropped anerror is returned if the table definition does not conform tothe foreign key constraints referencing the table. Likewisean ALTER TABLE operationreturns an error if a foreign key definition is incorrectlyformed. For more information seeSection 13.1.18.3 Using FOREIGN KEY Constraints.Setting this variable has the same effect onNDB tables as it does forInnoDB tables. Typically you leave thissetting enabled during normal operation to enforcereferentialintegrity. Disabling foreign key checking can be usefulfor reloading InnoDB tables in an orderdifferent from that required by their parent/childrelationships. SeeSection 14.6.6 InnoDB and FOREIGN KEY Constraints.Setting foreign_key_checks to 0 alsoaffects data definition statements:DROPSCHEMA drops a schema even if it contains tablesthat have foreign keys that are referred to by tables outsidethe schema and DROP TABLEdrops tables that have foreign keys that are referred to byother tables." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"+ -><()~*:&|", + "name":"ft_boolean_syntax", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for ft_boolean_syntax", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"984", + "unit":"NULL", + "description":"The list of operators supported by boolean full-text searchesperformed using IN BOOLEAN MODE. SeeSection 12.9.2 Boolean Full-Text Searches.The default variable value is'+ -><()~*:&|'. The rulesfor changing the value are as follows:" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"ft_stopword_file", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for ft_stopword_file", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"988", + "unit":"NULL", + "description":"The file from which to read the list of stopwords forfull-text searches on MyISAM tables. Theserver looks for the file in the data directory unless anabsolute path name is given to specify a different directory.All the words from the file are used; comments arenot honored. By default a built-in listof stopwords is used (as defined in thestorage/myisam/ft_static.c file). Settingthis variable to the empty string ('')disables stopword filtering. See alsoSection 12.9.4 Full-Text Stopwords." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"general_log", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for general-log", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"989", + "unit":"NULL", + "description":"Whether the general query log is enabled. The value can be 0(or OFF) to disable the log or 1 (orON) to enable the log. The default valuedepends on whether the--general_log option is given.The destination for log output is controlled by thelog_output system variable;if that value is NONE no log entries arewritten even if the log is enabled." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"host_name.log", + "name":"general_log_file", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for general_log_file", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"990", + "unit":"NULL", + "description":"The name of the general query log file. The default value ishost_name.logbut the initial value can be changed with the--general_log_file option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1024", + "name":"group_concat_max_len", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"4", + "dynamic":"t", + "rank":"-1", + "summary":"Options for group_concat_max_len", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{GlobalSession}", + "id":"991", + "unit":"NULL", + "description":"The maximum permitted result length in bytes for theGROUP_CONCAT() function. Thedefault is 1024." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"have_compress", + "deprecated":"f", + "valid_vals":"YES,NO,DISABLED", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"992", + "unit":"NULL", + "description":"YES if the zlibcompression library is available to the serverNO if not. If not theCOMPRESS() andUNCOMPRESS() functions cannotbe used." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"have_crypt", + "deprecated":"f", + "valid_vals":"YES,NO,DISABLED", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"993", + "unit":"NULL", + "description":"YES if the crypt()system call is available to the server NOif not. If not the ENCRYPT()function cannot be used." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"have_dynamic_loading", + "deprecated":"f", + "valid_vals":"YES,NO,DISABLED", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"994", + "unit":"NULL", + "description":"YES if mysqld supportsdynamic loading of plugins NO if not." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"have_geometry", + "deprecated":"f", + "valid_vals":"YES,NO,DISABLED", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"995", + "unit":"NULL", + "description":"YES if the server supports spatial datatypes NO if not." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"have_openssl", + "deprecated":"f", + "valid_vals":"YES,NO,DISABLED", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"996", + "unit":"NULL", + "description":"This variable is an alias forhave_ssl." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"have_profiling", + "deprecated":"f", + "valid_vals":"YES,NO,DISABLED", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"997", + "unit":"NULL", + "description":"YES if statement profiling capability ispresent NO if not. If present theprofiling system variable controls whetherthis capability is enabled or disabled. SeeSection 13.7.5.31 SHOW PROFILES Syntax.This variable is deprecated and will be removed in a futureMySQL release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"have_query_cache", + "deprecated":"f", + "valid_vals":"YES,NO,DISABLED", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"998", + "unit":"NULL", + "description":"YES if mysqld supportsthe query cache NO if not." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"have_rtree_keys", + "deprecated":"f", + "valid_vals":"YES,NO,DISABLED", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"999", + "unit":"NULL", + "description":"YES if RTREE indexes areavailable NO if not. (These are used forspatial indexes in MyISAM tables.)" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"have_ssl", + "deprecated":"f", + "valid_vals":"YES,NO,DISABLED", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"1000", + "unit":"NULL", + "description":"YES if mysqld supportsSSL connections NO if not.DISABLED indicates that the server wascompiled with SSL support but was not started with theappropriate--ssl-xxx options.For more information seeSection 6.3.11.2 Building MySQL with Support for Secure Connections." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"have_statement_timeout", + "deprecated":"f", + "valid_vals":"YES,NO,DISABLED", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for have_statement_timeout", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"1001", + "unit":"NULL", + "description":"Whether the statement execution timeout feature is available(see Statement Execution Time Optimizer Hints). Thevalue can be NO if the background threadused by this feature could not be initialized." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"have_symlink", + "deprecated":"f", + "valid_vals":"YES,NO,DISABLED", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"1002", + "unit":"NULL", + "description":"YES if symbolic link support is enabledNO if not. This is required on Unix forsupport of the DATA DIRECTORY andINDEX DIRECTORY table options. If theserver is started with the--skip-symbolic-linksoption the value is DISABLED.This variable has no meaning on Windows." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"lc_messages_dir", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for lc-messages-dir", + "vartype":"directory name", + "max_value":"NULL", + "scope":"{Global}", + "id":"1024", + "unit":"NULL", + "description":"The directory where error messages are located. The serveruses the value together with the value oflc_messages to produce thelocation for the error message file. SeeSection 10.2 Setting the Error Message Language." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"20", + "name":"max_delayed_threads", + "deprecated":"t", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_delayed_threads", + "vartype":"integer", + "max_value":"16384", + "scope":"{GlobalSession}", + "id":"1052", + "unit":"NULL", + "description":"This system variable is deprecated (becauseDELAYED inserts are not supported) andwill be removed in a future release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"-1", + "name":"host_cache_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for host_cache_size", + "vartype":"integer", + "max_value":"65536", + "scope":"{Global}", + "id":"1003", + "unit":"NULL", + "description":"The size of the internal host cache (seeSection 8.12.6.2 DNS Lookup Optimization and the Host Cache). Setting the size to 0 disablesthe host cache. Changing the cache size at runtime implicitlycauses a FLUSHHOSTS operation to clear the host cache and truncatethe host_cache table.The default value is 128 plus 1 for a value ofmax_connections up to 500plus 1 for every increment of 20 over 500 in themax_connections value cappedto a limit of 2000.Use of --skip-host-cache issimilar to setting thehost_cache_size systemvariable to 0 buthost_cache_size is moreflexible because it can also be used to resize enable ordisable the host cache at runtime not just at server startup.If you start the server with--skip-host-cache that doesnot prevent changes to the value ofhost_cache_size but suchchanges have no effect and the cache is not re-enabled even ifhost_cache_size is set largerthan 0." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"hostname", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for hostname", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"1004", + "unit":"NULL", + "description":"The server sets this variable to the server host name atstartup." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"INTERNAL", + "name":"identity", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"integer", + "max_value":"NULL", + "scope":"{NA}", + "id":"1005", + "unit":"NULL", + "description":"This variable is a synonym for thelast_insert_id variable. Itexists for compatibility with other database systems. You canread its value with SELECT @@identity andset it using SET identity." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"ignore_db_dirs", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for ignore_db_dirs", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"1006", + "unit":"NULL", + "description":"A comma-separated list of names that are not considered asdatabase directories in the data directory. The value is setfrom any instances of--ignore-db-dir given at serverstartup.As of MySQL 5.7.11--ignore-db-dir can be used atdata directory initialization time with mysqld--initialize to specify directories that the servershould ignore for purposes of assessing whether an existingdata directory is considered empty. SeeSection 2.10.1.1 Initializing the Data Directory Manually Using mysqld." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"init_connect", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for init_connect", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"1007", + "unit":"NULL", + "description":"A string to be executed by the server for each client thatconnects. The string consists of one or more SQL statementsseparated by semicolon characters. For example each clientsession begins by default with autocommit mode enabled. Forolder servers (before MySQL 5.5.8) there is no globalautocommit system variable tospecify that autocommit should be disabled by default but asa workaround init_connect canbe used to achieve the same effect:The init_connect variable canalso be set on the command line or in an option file. To setthe variable as just shown using an option file include theselines:The content of init_connectis not executed for users that have theSUPER privilege. This is doneso that an erroneous value forinit_connect does not preventall clients from connecting. For example the value mightcontain a statement that has a syntax error thus causingclient connections to fail. Not executinginit_connect for users thathave the SUPER privilegeenables them to open a connection and fix theinit_connect value.The server discards any result sets produced by statements inthe value of of init_connect." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"init_file", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for init-file", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"1008", + "unit":"NULL", + "description":"The name of the file specified with the--init-file option when youstart the server. This should be a file containing SQLstatements that you want the server to execute when it starts.Each statement must be on a single line and should not includecomments. For more information see the description of--init-file." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"INTERNAL", + "name":"insert_id", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"integer", + "max_value":"NULL", + "scope":"{NA}", + "id":"1009", + "unit":"NULL", + "description":"The value to be used by the followingINSERT orALTER TABLE statement wheninserting an AUTO_INCREMENT value. This ismainly used with the binary log." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"28800", + "name":"interactive_timeout", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for interactive_timeout", + "vartype":"integer", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1010", + "unit":"NULL", + "description":"The number of seconds the server waits for activity on aninteractive connection before closing it. An interactiveclient is defined as a client that uses theCLIENT_INTERACTIVE option tomysql_real_connect(). See alsowait_timeout." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"MYISAM", + "name":"internal_tmp_disk_storage_engine", + "deprecated":"f", + "valid_vals":"MYISAM,INNODB", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for internal_tmp_disk_storage_engine", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"1011", + "unit":"NULL", + "description":"The storage engine for on-disk internal temporary tables (seeSection 8.4.4 Internal Temporary Table Use in MySQL). Permitted valuesare MYISAM and INNODB.This variable was added in MySQL 5.7.5 with a default ofMYISAM. In MySQL 5.7.6 the default valuewas changed to INNODB. With this changethe optimizer uses theInnoDB storage engine by default foron-disk internal temporary tables.Underinternal_tmp_disk_storage_engine=INNODBqueries that generate temporary tables that exceedInnoDBrow or column limits will return Row sizetoo large or Too manycolumns errors. The workaround is to setinternal_tmp_disk_storage_engineto MYISAM." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"256", + "name":"multi_range_count", + "deprecated":"t", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for multi_range_count", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{GlobalSession}", + "id":"1073", + "unit":"NULL", + "description":"This variable has no effect. It is deprecated and will beremoved in a future MySQL release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"off", + "name":"debug_assertions", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Turns on various assertion checks.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1501", + "unit":"", + "description":"This is a debugging aid." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"262144", + "name":"join_buffer_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"128", + "dynamic":"t", + "rank":"-1", + "summary":"Options for join_buffer_size", + "vartype":"integer", + "max_value":"18446744073709547520", + "scope":"{GlobalSession}", + "id":"1012", + "unit":"NULL", + "description":"The minimum size of the buffer that is used for plain indexscans range index scans and joins that do not use indexesand thus perform full table scans. Normally the best way toget fast joins is to add indexes. Increase the value ofjoin_buffer_size to get afaster full join when adding indexes is not possible. One joinbuffer is allocated for each full join between two tables. Fora complex join between several tables for which indexes arenot used multiple join buffers might be necessary.Unless Batched Key Access (BKA) is used there is no gain fromsetting the buffer larger than required to hold each matchingrow and all joins allocate at least the minimum size so usecaution in setting this variable to a large value globally. Itis better to keep the global setting small and change to alarger setting only in sessions that are doing large joins.Memory allocation time can cause substantial performance dropsif the global size is larger than needed by most queries thatuse it.When BKA is used the value ofjoin_buffer_size defines howlarge the batch of keys is in each request to the storageengine. The larger the buffer the more sequential access willbe to the right hand table of a join operation which cansignificantly improve performance.The default is 256KB. The maximum permissible setting forjoin_buffer_size is4GB1. Larger values are permitted for 64-bit platforms(except 64-bit Windows for which large values are truncatedto 4GB1 with a warning).For additional information about join buffering seeSection 8.2.1.10 Nested-Loop Join Algorithms. For information aboutBatched Key Access seeSection 8.2.1.14 Block Nested-Loop and Batched Key Access Joins." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"keep_files_on_create", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for keep_files_on_create", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1013", + "unit":"NULL", + "description":"If a MyISAM table is created with noDATA DIRECTORY option the.MYD file is created in the databasedirectory. By default if MyISAM finds anexisting .MYD file in this case itoverwrites it. The same applies to .MYIfiles for tables created with no INDEXDIRECTORY option. To suppress this behavior set thekeep_files_on_create variableto ON (1) in which caseMyISAM will not overwrite existing filesand returns an error instead. The default value isOFF (0).If a MyISAM table is created with aDATA DIRECTORY or INDEXDIRECTORY option and an existing.MYD or .MYI file isfound MyISAM always returns an error. It will not overwrite afile in the specified directory." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"8388608", + "name":"key_buffer_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"8", + "dynamic":"t", + "rank":"-1", + "summary":"Options for key_buffer_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"1014", + "unit":"NULL", + "description":"Index blocks for MyISAM tables are bufferedand are shared by all threads.key_buffer_size is the sizeof the buffer used for index blocks. The key buffer is alsoknown as the key cache.The maximum permissible setting forkey_buffer_size is4GB1 on 32-bit platforms. Larger values are permittedfor 64-bit platforms. The effective maximum size might beless depending on your available physical RAM and per-processRAM limits imposed by your operating system or hardwareplatform. The value of this variable indicates the amount ofmemory requested. Internally the server allocates as muchmemory as possible up to this amount but the actualallocation might be less.You can increase the value to get better index handling forall reads and multiple writes; on a system whose primaryfunction is to run MySQL using theMyISAM storage engine 25% of themachine's total memory is an acceptable value for thisvariable. However you should be aware that if you make thevalue too large (for example more than 50% of themachine's total memory) your system might start to pageand become extremely slow. This is because MySQL relies on theoperating system to perform file system caching for datareads so you must leave some room for the file system cache.You should also consider the memory requirements of any otherstorage engines that you may be using in addition toMyISAM.For even more speed when writing many rows at the same timeuse LOCK TABLES. SeeSection 8.2.2.1 Speed of INSERT Statements.You can check the performance of the key buffer by issuing aSHOW STATUS statement andexamining theKey_read_requestsKey_readsKey_write_requests andKey_writes status variables.(See Section 13.7.5 SHOW Syntax.) TheKey_reads/Key_read_requests ratio shouldnormally be less than 0.01. TheKey_writes/Key_write_requests ratio isusually near 1 if you are using mostly updates and deletesbut might be much smaller if you tend to do updates thataffect many rows at the same time or if you are using theDELAY_KEY_WRITE table option.The fraction of the key buffer in use can be determined usingkey_buffer_size inconjunction with theKey_blocks_unused statusvariable and the buffer block size which is available fromthe key_cache_block_sizesystem variable:This value is an approximation because some space in the keybuffer is allocated internally for administrative structures.Factors that influence the amount of overhead for thesestructures include block size and pointer size. As block sizeincreases the percentage of the key buffer lost to overheadtends to decrease. Larger blocks results in a smaller numberof read operations (because more keys are obtained per read)but conversely an increase in reads of keys that are notexamined (if not all keys in a block are relevant to a query).It is possible to create multiple MyISAMkey caches. The size limit of 4GB applies to each cacheindividually not as a group. SeeSection 8.10.2 The MyISAM Key Cache." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"300", + "name":"key_cache_age_threshold", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"100", + "dynamic":"t", + "rank":"-1", + "summary":"Options for key_cache_age_threshold", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"1015", + "unit":"NULL", + "description":"This value controls the demotion of buffers from the hotsublist of a key cache to the warm sublist. Lower values causedemotion to happen more quickly. The minimum value is 100. Thedefault value is 300. See Section 8.10.2 The MyISAM Key Cache." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1024", + "name":"key_cache_block_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"512", + "dynamic":"t", + "rank":"-1", + "summary":"Options for key_cache_block_size", + "vartype":"integer", + "max_value":"16384", + "scope":"{Global}", + "id":"1016", + "unit":"NULL", + "description":"The size in bytes of blocks in the key cache. The defaultvalue is 1024. See Section 8.10.2 The MyISAM Key Cache." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"100", + "name":"key_cache_division_limit", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for key_cache_division_limit", + "vartype":"integer", + "max_value":"100", + "scope":"{Global}", + "id":"1017", + "unit":"NULL", + "description":"The division point between the hot and warm sublists of thekey cache buffer list. The value is the percentage of thebuffer list to use for the warm sublist. Permissible valuesrange from 1 to 100. The default value is 100. SeeSection 8.10.2 The MyISAM Key Cache." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"platform specific", + "name":"keyring_file_data", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for keyring_file_data", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"1018", + "unit":"NULL", + "description":"The path name of the data file used for secure data storage bythe keyring_file plugin. The file locationshould be in a directory considered for use only by thekeyring_file plugin. For example do notlocate the file under the data directory.Do not use the same keyring_file data filefor multiple MySQL instances. Each instance should have itsown unique data file.The default file name is keyring locatedin a directory that is platform specific and depends on thevalue of the INSTALL_LAYOUTCMake option as shown in the followingtable. To specify the default directory for the fileexplicitly if you are building from source use theINSTALL_MYSQLKEYRINGDIRCMake option.If the value assigned tokeyring_file_data specifies afile that does not exist the keyring_fileplugin attempts to create it during plugin initialization. Ifnecessary the plugin also creates the directory in which thefile is located.If you create the directory manually it should have arestrictive mode and be accessible only to the account used torun the server. For example on Unix and Unix-like systems ifyou set keyring_file_data to/usr/local/mysql/mysql-keyring/keyringthe following commands (executed as root)create the directory and set its mode and ownership:If the keyring_file plugin cannot create oraccess the file it writes an error message to the error log.If an attempted runtime assignment tokeyring_file_data results inan error the variable value remains unchanged." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"large_files_support", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for large_files_support", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1019", + "unit":"NULL", + "description":"Whether mysqld was compiled with optionsfor large file support." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"FALSE", + "name":"large_pages", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for large-pages", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1020", + "unit":"NULL", + "description":"Whether large page support is enabled (via the--large-pages option). SeeSection 8.12.5.2 Enabling Large Page Support." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"large_page_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for large_page_size", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"1021", + "unit":"NULL", + "description":"If large page support is enabled this shows the size ofmemory pages. Large memory pages are supported only on Linux;on other platforms the value of this variable is always 0.See Section 8.12.5.2 Enabling Large Page Support." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"INTERNAL", + "name":"last_insert_id", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"integer", + "max_value":"NULL", + "scope":"{NA}", + "id":"1022", + "unit":"NULL", + "description":"The value to be returned fromLAST_INSERT_ID(). This isstored in the binary log when you useLAST_INSERT_ID() in a statementthat updates a table. Setting this variable does not updatethe value returned by themysql_insert_id() C APIfunction." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"en_US", + "name":"lc_messages", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for lc-messages", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1023", + "unit":"NULL", + "description":"The locale to use for error messages. The default isen_US. The server converts the argument toa language name and combines it with the value oflc_messages_dir to producethe location for the error message file. SeeSection 10.2 Setting the Error Message Language." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"on", + "name":"debug_pretty_print", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Indents parse and plan tree displays.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1502", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"LOCALE", + "name":"lc_time_names", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for lc_time_names", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1025", + "unit":"NULL", + "description":"This variable specifies the locale that controls the languageused to display day and month names and abbreviations. Thisvariable affects the output from theDATE_FORMAT()DAYNAME() andMONTHNAME() functions. Localenames are POSIX-style values such as'ja_JP' or 'pt_BR'. Thedefault value is 'en_US' regardless of yoursystem's locale setting. For further information seeSection 10.7 MySQL Server Locale Support." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"GPL", + "name":"license", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for license", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"1026", + "unit":"NULL", + "description":"The type of license the server has." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"local_infile", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for local_infile", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1027", + "unit":"NULL", + "description":"Whether LOCAL is supported forLOAD DATAINFILE statements. If this variable is disabledclients cannot use LOCAL inLOAD DATA statements. SeeSection 6.1.6 Security Issues with LOAD DATA LOCAL." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"31536000", + "name":"lock_wait_timeout", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for lock_wait_timeout", + "vartype":"integer", + "max_value":"31536000", + "scope":"{GlobalSession}", + "id":"1028", + "unit":"NULL", + "description":"This variable specifies the timeout in seconds for attempts toacquire metadata locks. The permissible values range from 1 to31536000 (1 year). The default is 31536000.This timeout applies to all statements that use metadatalocks. These include DML and DDL operations on tables viewsstored procedures and stored functions as well asLOCK TABLESFLUSH TABLES WITH READLOCK and HANDLERstatements.This timeout does not apply to implicit accesses to systemtables in the mysql database such as granttables modified by GRANT orREVOKE statements or tablelogging statements. The timeout does apply to system tablesaccessed directly such as withSELECT orUPDATE.The timeout value applies separately for each metadata lockattempt. A given statement can require more than one lock soit is possible for the statement to block for longer than thelock_wait_timeout valuebefore reporting a timeout error. When lock timeout occursER_LOCK_WAIT_TIMEOUT isreported.lock_wait_timeout does notapply to delayed inserts which always execute with a timeoutof 1 year. This is done to avoid unnecessary timeouts becausea session that issues a delayed insert receives nonotification of delayed insert timeouts." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"locked_in_memory", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for locked_in_memory", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1029", + "unit":"NULL", + "description":"Whether mysqld was locked in memory with--memlock." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"log_backward_compatible_user_definitions", + "deprecated":"t", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for log_backward_compatible_user_definitions", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1030", + "unit":"NULL", + "description":"Whether to log theuser_specification part ofCREATE USERALTER USER andGRANT statements inbackward-compatible (pre-5.7.6) fashion:This variable was removed in MySQL 5.7.9 and replaced bylog_builtin_as_identified_by_password." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"FALSE", + "name":"log_bin_trust_function_creators", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for log-bin-trust-function-creators", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1031", + "unit":"NULL", + "description":"This variable applies when binary logging is enabled. Itcontrols whether stored function creators can be trusted notto create stored functions that will cause unsafe events to bewritten to the binary log. If set to 0 (the default) usersare not permitted to create or alter stored functions unlessthey have the SUPER privilegein addition to the CREATEROUTINE or ALTERROUTINE privilege. A setting of 0 also enforces therestriction that a function must be declared with theDETERMINISTIC characteristic or with theREADS SQL DATA or NO SQLcharacteristic. If the variable is set to 1 MySQL does notenforce these restrictions on stored function creation. Thisvariable also applies to trigger creation. SeeSection 20.7 Binary Logging of Stored Programs." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"log_builtin_as_identified_by_password", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for log_builtin_as_identified_by_password", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1032", + "unit":"NULL", + "description":"This variable affects binary logging of user-managementstatements. If enabled binary logging forCREATE USER statementsinvolving built-in authentication plugins rewrites thestatements to include an IDENTIFIED BYPASSWORD clause and SETPASSWORD statements are logged asSET PASSWORD statements ratherthan being rewritten to ALTERUSER statements.This variable was added in MySQL 5.7.9. It replaces thelog_backward_compatible_user_definitionsvariable." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"log_error", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for log-error", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"1033", + "unit":"NULL", + "description":"The location of the error log or stderr ifthe server is writing error message to the standard erroroutput. See Section 5.4.2 The Error Log." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"3", + "name":"log_error_verbosity", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for log_error_verbosity", + "vartype":"integer", + "max_value":"3", + "scope":"{Global}", + "id":"1034", + "unit":"NULL", + "description":"This variable controls verbosity of the server in writingerror warning and note messages to the error log. Thefollowing table shows the permitted values. The default is 3.log_error_verbosity was addedin MySQL 5.7.2. It is preferred over and should be usedinstead of the olderlog_warnings system variable.See the description oflog_warnings for informationabout how that variable relates tolog_error_verbosity. Inparticular assigning a value tolog_warnings assigns a valueto log_error_verbosity andvice versa." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"60", + "name":"net_write_timeout", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for net_write_timeout", + "vartype":"integer", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1087", + "unit":"NULL", + "description":"The number of seconds to wait for a block to be written to aconnection before aborting the write. See alsonet_read_timeout." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"FILE", + "name":"log_output", + "deprecated":"f", + "valid_vals":"TABLE,FILE,NONE", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for log-output", + "vartype":"set", + "max_value":"NULL", + "scope":"{Global}", + "id":"1035", + "unit":"NULL", + "description":"The destination for general query log and slow query logoutput. The value can be a comma-separated list of one or moreof the words TABLE (log to tables)FILE (log to files) orNONE (do not log to tables or files). Thedefault value is FILE.NONE if present takes precedence over anyother specifiers. If the value is NONE logentries are not written even if the logs are enabled. If thelogs are not enabled no logging occurs even if the value oflog_output is notNONE. For more information seeSection 5.4.1 Selecting General Query and Slow Query Log Output Destinations." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"log_queries_not_using_indexes", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for log-queries-not-using-indexes", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1036", + "unit":"NULL", + "description":"Whether queries that do not use indexes are logged to the slowquery log. See Section 5.4.5 The Slow Query Log." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"log_syslog", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for log_syslog", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1037", + "unit":"NULL", + "description":"Whether to write error log output to syslog(on Unix and Unix-like systems) or Event Log (on Windows). Thedefault value is platform specific:Regardless of the defaultlog_syslog can be setexplicitly to control output on any supported platform.syslog output control is orthogonal tosending error output to a file or (on Windows) to the console.Error output can be directed to the latter destination inaddition to or instead of syslog asdesired." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"daemon", + "name":"log_syslog_facility", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for log_syslog_facility", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"1038", + "unit":"NULL", + "description":"The facility for error log output written tosyslog (what type of program is sending themessage). This variable has no effect unless thelog_syslog system variable isenabled.The permitted values can vary per operating system; consultyour system syslog documentation.This variable does not exist on Windows." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"log_syslog_include_pid", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for log_syslog_include_pid", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1039", + "unit":"NULL", + "description":"Whether to include the server process ID in each line of errorlog output written to syslog. This variablehas no effect unless thelog_syslog system variable isenabled.This variable does not exist on Windows." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"empty string", + "name":"log_syslog_tag", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for log_syslog_tag", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"1040", + "unit":"NULL", + "description":"The tag to be added to the server identifier in error logoutput written to syslog. This variable hasno effect unless thelog_syslog system variable isenabled.By default the server identifier is mysqldwith no tag. If a tag of tag_val isspecified it is appended to the server identifier with aleading hyphen resulting in an identifier ofmysqld-tag_val.On Windows to use a tag that does not already exist theserver must be run from an account with Administratorprivileges to permit creation of a registry entry for thetag. Elevated privileges are not required if the tag alreadyexists." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"UTC", + "name":"log_timestamps", + "deprecated":"f", + "valid_vals":"UTC,SYSTEM", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for log_timestamps", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"1041", + "unit":"NULL", + "description":"This variable controls the timestamp time zone of error logmessages and of general query log and slow query log messageswritten to files. It does not affect the time zone of generalquery log and slow query log messages written to tables(mysql.general_logmysql.slow_log). Rows retrieved from thosetables can be converted from the local system time zone to anydesired time zone withCONVERT_TZ() or by setting thesession time_zone systemvariable.Permitted log_timestampsvalues are UTC (the default) andSYSTEM (local system time zone).Timestamps are written using ISO 8601 / RFC 3339 format:YYYY-MM-DDThh:mm:ss.uuuuuu plus a tailvalue of Z signifying Zulu time (UTC) orhh:mm (an offset from UTC).This variable was added in MySQL 5.7.2. Before 5.7.2timestamps in log messages were written using the local systemtime zone by default not UTC. If you wantthe previous log message time zone default setlog_timestamps=SYSTEM." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"log_throttle_queries_not_using_indexes", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for log_throttle_queries_not_using_indexes", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"1042", + "unit":"NULL", + "description":"Iflog_queries_not_using_indexesis enabled thelog_throttle_queries_not_using_indexesvariable limits the number of such queries per minute that canbe written to the slow query log. A value of 0 (the default)means no limit. For more information seeSection 5.4.5 The Slow Query Log." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"log_slow_admin_statements", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for log_slow_admin_statements", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1043", + "unit":"NULL", + "description":"Include slow administrative statements in the statementswritten to the slow query log. Administrative statementsinclude ALTER TABLEANALYZE TABLECHECK TABLECREATE INDEXDROP INDEXOPTIMIZE TABLE andREPAIR TABLE." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"151", + "name":"max_connections", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_connections", + "vartype":"integer", + "max_value":"100000", + "scope":"{Global}", + "id":"1051", + "unit":"NULL", + "description":"The maximum permitted number of simultaneous clientconnections. By default this is 151. SeeSection B.5.2.7 Too many connections for more information.Increasing this value increases the number of file descriptorsthat mysqld requires. If the requirednumber of descriptors are not available the server reducesthe value of max_connections.See Section 8.4.3.1 How MySQL Opens and Closes Tables for comments on filedescriptor limits.Connections refused because themax_connections limit isreached increment theConnection_errors_max_connectionsstatus variable." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"log_warnings", + "deprecated":"t", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for log-warnings", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"1044", + "unit":"NULL", + "description":"Whether to produce additional warning messages to the errorlog. This variable is enabled by default (the default is 1before MySQL 5.7.2 2 as of 5.7.2). To disable it set it to0. The server logs messages about statements that are unsafefor statement-based logging if the value is greater than 0.Aborted connections and access-denied errors for newconnection attempts are logged if the value is greater than 1.See Section B.5.2.11 Communication Errors and Aborted Connections.Enabling this option by setting it greater than 0 isrecommended if you use replication to get more informationabout what is happening such as messages about networkfailures and reconnections. If the value is greater than 1aborted connections are written to the error log andaccess-denied errors for new connection attempts are written.If a slave server is started withlog_warnings enabled theslave prints messages to the error log to provide informationabout its status such as the binary log and relay logcoordinates where it starts its job when it is switching toanother relay log when it reconnects after a disconnect andso forth.As of MySQL 5.7.2 information items previously governed bylog_warnings are governed bylog_error_verbosity which ispreferred over and should be used instead of the olderlog_warnings system variable.(The log_warnings systemvariable and --log-warningscommand-line option are deprecated and will be removed in afuture MySQL release.)Assigning a value tolog_warnings assigns a valueto log_error_verbosity andvice versa. The variables are related as follows:As of MySQL 5.7.2 the default log level is controlled bylog_error_verbosity whichhas a default of 3. In addition the default forlog_warnings changes from 1to 2 which corresponds tolog_error_verbosity=3. Toachieve a logging level similar to the previous default setlog_error_verbosity=2.In MySQL 5.7.2 and higher use oflog_warnings is stillpermitted but maps onto use oflog_error_verbosity asfollows:" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"10", + "name":"long_query_time", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for long_query_time", + "vartype":"numeric", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1045", + "unit":"NULL", + "description":"If a query takes longer than this many seconds the serverincrements the Slow_queriesstatus variable. If the slow query log is enabled the queryis logged to the slow query log file. This value is measuredin real time not CPU time so a query that is under thethreshold on a lightly loaded system might be above thethreshold on a heavily loaded one. The minimum and defaultvalues of long_query_time are0 and 10 respectively. The value can be specified to aresolution of microseconds. For logging to a file times arewritten including the microseconds part. For logging totables only integer times are written; the microseconds partis ignored. See Section 5.4.5 The Slow Query Log." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"FALSE", + "name":"low_priority_updates", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for low-priority-updates", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1046", + "unit":"NULL", + "description":"If set to 1 allINSERTUPDATEDELETE and LOCK TABLEWRITE statements wait until there is no pendingSELECT or LOCK TABLEREAD on the affected table. This affects onlystorage engines that use only table-level locking (such asMyISAM MEMORY andMERGE)." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"lower_case_file_system", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for lower_case_file_system", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1047", + "unit":"NULL", + "description":"This variable describes the case sensitivity of file names onthe file system where the data directory is located.OFF means file names are case sensitiveON means they are not case sensitive. Thisvariable is read only because it reflects a file systemattribute and setting it would have no effect on the filesystem." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"lower_case_table_names", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"Options for lower_case_table_names", + "vartype":"integer", + "max_value":"2", + "scope":"{Global}", + "id":"1048", + "unit":"NULL", + "description":"If set to 0 table names are stored as specified andcomparisons are case sensitive. If set to 1 table names arestored in lowercase on disk and comparisons are not casesensitive. If set to 2 table names are stored as given butcompared in lowercase. This option also applies to databasenames and table aliases. For additional information seeSection 9.2.2 Identifier Case Sensitivity.On Windows the default value is 1. On OS X the default valueis 2.You should not setlower_case_table_names to 0if you are running MySQL on a system where the data directoryresides on a case-insensitive file system (such as on Windowsor OS X). It is an unsupported combination that could resultin a hang condition when running an INSERT INTO ...SELECT ... FROM tbl_nameoperation with the wrong tbl_nameletter case. With MyISAM accessing tablenames using different letter cases could cause indexcorruption.As of MySQL 5.7.9 an error message is printed and the serverexits if you attempt to start the server with--lower_case_table_names=0 ona case-insensitive file system.If you are using InnoDB tables you shouldset this variable to 1 on all platforms to force names to beconverted to lowercase.The setting of this variable in MySQL 5.7 affectsthe behavior of replication filtering options with regard tocase sensitivity. (Bug #51639) SeeSection 17.2.5 How Servers Evaluate Replication Filtering Rules for more information." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"4194304", + "name":"max_allowed_packet", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1024", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_allowed_packet", + "vartype":"integer", + "max_value":"1073741824", + "scope":"{GlobalSession}", + "id":"1049", + "unit":"NULL", + "description":"The maximum size of one packet or any generated/intermediatestring or any parameter sent by themysql_stmt_send_long_data() CAPI function. The default is 4MB.The packet message buffer is initialized tonet_buffer_length bytes butcan grow up tomax_allowed_packet bytes whenneeded. This value by default is small to catch large(possibly incorrect) packets.You must increase this value if you are using largeBLOB columns or long strings.It should be as big as the largestBLOB you want to use. Theprotocol limit formax_allowed_packet is 1GB.The value should be a multiple of 1024; nonmultiples arerounded down to the nearest multiple.When you change the message buffer size by changing the valueof the max_allowed_packetvariable you should also change the buffer size on the clientside if your client program permits it. The defaultmax_allowed_packet valuebuilt in to the client library is 1GB but individual clientprograms might override this. For examplemysql and mysqldump havedefaults of 16MB and 24MB respectively. They also enable youto change the client-side value by settingmax_allowed_packet on thecommand line or in an option file.The session value of this variable is read only. The clientcan receive up to as many bytes as the session value. Howeverthe server will not send to the client more bytes than thecurrent globalmax_allowed_packet value.(The global value could be less than the session value if theglobal value is changed after the client connects.)" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"100", + "name":"max_connect_errors", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_connect_errors", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"1050", + "unit":"NULL", + "description":"If more than this many successive connection requests from ahost are interrupted without a successful connection theserver blocks that host from further connections. You canunblock blocked hosts by flushing the host cache. To do soissue a FLUSHHOSTS statement or execute a mysqladminflush-hosts command. If a connection is establishedsuccessfully within fewer thanmax_connect_errors attemptsafter a previous connection was interrupted the error countfor the host is cleared to zero. However once a host isblocked flushing the host cache is the only way to unblockit. The default is 100." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1024", + "name":"max_digest_length", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"Options for max_digest_length", + "vartype":"integer", + "max_value":"1048576", + "scope":"{Global}", + "id":"1053", + "unit":"NULL", + "description":"The maximum number of bytes available for computing statementdigests (seeSection 22.7 Performance Schema Statement Digests). Whenthis amount of space is used for computing the digest for astatement no further tokens from the parsed statement arecollected or figure into the digest value. Statementsdiffering only after that many bytes of parsed statementtokens produce the same digest and are aggregated for digeststatistics.Decreasing themax_digest_length valuereduces memory use but causes the digest value of morestatements to become indistinguishable if they differ only atthe end. Increasing the value permits longer statements to bedistinguished but increases memory use particularly forworkloads that involve large numbers of simultaneous sessions(max_digest_length bytes areallocated per session).This variable was added in MySQL 5.7.6. Until 5.7.8 thisvariable applies to Performance Schema and to other serverfunctions that use digests such as query rewrite plugins. Asof 5.7.8 it no longer applies to Performance Schema; insteaduseperformance_schema_max_digest_length." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"64", + "name":"max_error_count", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_error_count", + "vartype":"integer", + "max_value":"65535", + "scope":"{GlobalSession}", + "id":"1054", + "unit":"NULL", + "description":"The maximum number of error warning and note messages to bestored for display by the SHOWERRORS and SHOWWARNINGS statements. This is the same as the numberof condition areas in the diagnostics area and thus thenumber of conditions that can be inspected byGET DIAGNOSTICS." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"max_execution_time", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_execution_time", + "vartype":"integer", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1055", + "unit":"NULL", + "description":"The execution timeout forSELECT statements inmilliseconds. If the value is 0 timeouts are not enabled.max_execution_time applies asfollows:This variable was added in MySQL 5.7.8. Previously it wasnamed max_statement_time." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"16777216", + "name":"max_heap_table_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"16384", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_heap_table_size", + "vartype":"integer", + "max_value":"1844674407370954752", + "scope":"{GlobalSession}", + "id":"1056", + "unit":"NULL", + "description":"This variable sets the maximum size to which user-createdMEMORY tables are permitted to grow. Thevalue of the variable is used to calculateMEMORY table MAX_ROWSvalues. Setting this variable has no effect on any existingMEMORY table unless the table isre-created with a statement such asCREATE TABLE or altered withALTER TABLE orTRUNCATE TABLE. A serverrestart also sets the maximum size of existingMEMORY tables to the globalmax_heap_table_size value.This variable is also used in conjunction withtmp_table_size to limit thesize of internal in-memory tables. SeeSection 8.4.4 Internal Temporary Table Use in MySQL.max_heap_table_size is not replicated. SeeSection 17.4.1.23 Replication and MEMORY Tables andSection 17.4.1.38 Replication and Variables for moreinformation." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"20", + "name":"max_insert_delayed_threads", + "deprecated":"t", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_insert_delayed_threads", + "vartype":"integer", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1057", + "unit":"NULL", + "description":"This variable is a synonym formax_delayed_threads.This system variable is deprecated (becauseDELAYED inserts are not supported) andwill be removed in a future release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"18446744073709551615", + "name":"max_join_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_join_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{GlobalSession}", + "id":"1058", + "unit":"NULL", + "description":"Do not permit statements that probably need to examine morethan max_join_size rows (forsingle-table statements) or row combinations (formultiple-table statements) or that are likely to do more thanmax_join_size disk seeks. Bysetting this value you can catch statements where keys arenot used properly and that would probably take a long time.Set it if your users tend to perform joins that lack aWHERE clause that take a long time orthat return millions of rows.Setting this variable to a value other thanDEFAULT resets the value ofsql_big_selects to0. If you set thesql_big_selects value againthe max_join_size variable isignored.If a query result is in the query cache no result size checkis performed because the result has previously been computedand it does not burden the server to send it to the client." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1024", + "name":"max_length_for_sort_data", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"4", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_length_for_sort_data", + "vartype":"integer", + "max_value":"8388608", + "scope":"{GlobalSession}", + "id":"1059", + "unit":"NULL", + "description":"The cutoff on the size of index values that determines whichfilesort algorithm to use. SeeSection 8.2.1.15 ORDER BY Optimization." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"65536", + "name":"max_points_in_geometry", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"3", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_points_in_geometry", + "vartype":"integer", + "max_value":"1048576", + "scope":"{Global}", + "id":"1060", + "unit":"NULL", + "description":"The maximum value of thepoints_per_circle argument to theST_Buffer_Strategy() function." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"16382", + "name":"max_prepared_stmt_count", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_prepared_stmt_count", + "vartype":"integer", + "max_value":"1048576", + "scope":"{Global}", + "id":"1061", + "unit":"NULL", + "description":"This variable limits the total number of prepared statementsin the server. It can be used in environments where there isthe potential for denial-of-service attacks based on runningthe server out of memory by preparing huge numbers ofstatements. If the value is set lower than the current numberof prepared statements existing statements are not affectedand can be used but no new statements can be prepared untilthe current number drops below the limit. The default value is16382. The permissible range of values is from 0 to 1million. Setting the value to 0 disables prepared statements." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"10", + "name":"net_retry_count", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for net_retry_count", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{GlobalSession}", + "id":"1086", + "unit":"NULL", + "description":"If a read or write on a communication port is interruptedretry this many times before giving up. This value should beset quite high on FreeBSD because internal interrupts are sentto all threads." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"max_relay_log_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_relay_log_size", + "vartype":"integer", + "max_value":"1073741824", + "scope":"{Global}", + "id":"1062", + "unit":"NULL", + "description":"If a write by a replication slave to its relay log causes thecurrent log file size to exceed the value of this variablethe slave rotates the relay logs (closes the current file andopens the next one). Ifmax_relay_log_size is 0 theserver uses max_binlog_sizefor both the binary log and the relay log. Ifmax_relay_log_size is greaterthan 0 it constrains the size of the relay log which enablesyou to have different sizes for the two logs. You must setmax_relay_log_size to between4096 bytes and 1GB (inclusive) or to 0. The default value is0. See Section 17.2.2 Replication Implementation Details." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"18446744073709551615", + "name":"max_seeks_for_key", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_seeks_for_key", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{GlobalSession}", + "id":"1063", + "unit":"NULL", + "description":"Limit the assumed maximum number of seeks when looking up rowsbased on a key. The MySQL optimizer assumes that no more thanthis number of key seeks are required when searching formatching rows in a table by scanning an index regardless ofthe actual cardinality of the index (seeSection 13.7.5.22 SHOW INDEX Syntax). By setting this to a low value(say 100) you can force MySQL to prefer indexes instead oftable scans." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1024", + "name":"max_sort_length", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"4", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_sort_length", + "vartype":"integer", + "max_value":"8388608", + "scope":"{GlobalSession}", + "id":"1064", + "unit":"NULL", + "description":"The number of bytes to use when sorting data values. Theserver uses only the firstmax_sort_length bytes of eachvalue and ignores the rest. Consequently values that differonly after the firstmax_sort_length bytes compareas equal for GROUP BY ORDERBY and DISTINCT operations.Increasing the value ofmax_sort_length may requireincreasing the value ofsort_buffer_size as well. Fordetails see Section 8.2.1.15 ORDER BY Optimization" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"max_sp_recursion_depth", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_sp_recursion_depth", + "vartype":"integer", + "max_value":"255", + "scope":"{GlobalSession}", + "id":"1065", + "unit":"NULL", + "description":"The number of times that any given stored procedure may becalled recursively. The default value for this option is 0which completely disables recursion in stored procedures. Themaximum value is 255.Stored procedure recursion increases the demand on threadstack space. If you increase the value ofmax_sp_recursion_depth itmay be necessary to increase thread stack size by increasingthe value of thread_stack atserver startup." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"max_statement_time", + "deprecated":"t", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_statement_time", + "vartype":"integer", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1066", + "unit":"NULL", + "description":"The execution timeout forSELECT statements inmilliseconds. If the value is 0 timeouts are not enabled.max_statement_time applies asfollows:This variable was added in MySQL 5.7.4 and renamed tomax_execution_time in MySQL5.7.8." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"max_tmp_tables", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"integer", + "max_value":"NULL", + "scope":"{NA}", + "id":"1067", + "unit":"NULL", + "description":"This variable is unused. It is deprecated and will be removedin a future MySQL release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"max_user_connections", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_user_connections", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{GlobalSession}", + "id":"1068", + "unit":"NULL", + "description":"The maximum number of simultaneous connections permitted toany given MySQL user account. A value of 0 (the default) meansno limit.This variable has a global value that can be set at serverstartup or runtime. It also has a read-only session value thatindicates the effective simultaneous-connection limit thatapplies to the account associated with the current session.The session value is initialized as follows:Account resource limits are specified using theCREATE USER orALTER USER statement. SeeSection 6.3.4 Setting Account Resource Limits." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"18446744073709551615", + "name":"max_write_lock_count", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_write_lock_count", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"1069", + "unit":"NULL", + "description":"After this many write locks permit some pending read lockrequests to be processed in between." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"mecab_rc_file", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for mecab_rc_file", + "vartype":"directory name", + "max_value":"NULL", + "scope":"{Global}", + "id":"1070", + "unit":"NULL", + "description":"The mecab_rc_file option is used whensetting up the MeCab full-text parser.The mecab_rc_file option defines the pathto the mecabrc configuration file whichis the configuration file for MeCab. The option is read-onlyand can only be set at startup. Themecabrc configuration file is required toinitialize MeCab.For information about the MeCab full-text parser seeSection 12.9.9 MeCab Full-Text Parser Plugin.For information about options that can be specified in theMeCab mecabrc configuration file referto theMeCabDocumentation on theGoogleDevelopers site." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1024", + "name":"metadata_locks_cache_size", + "deprecated":"t", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"f", + "rank":"-1", + "summary":"Options for metadata_locks_cache_size", + "vartype":"integer", + "max_value":"1048576", + "scope":"{Global}", + "id":"1071", + "unit":"NULL", + "description":"The size of the metadata locks cache. The server uses thiscache to avoid creation and destruction of synchronizationobjects. This is particularly helpful on systems where suchoperations are expensive such as Windows XP.In MySQL 5.7.4 metadata locking implementation changes makethis variable unnecessary so it is deprecated and will beremoved in a future MySQL release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"8", + "name":"metadata_locks_hash_instances", + "deprecated":"t", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"f", + "rank":"-1", + "summary":"Options for metadata_locks_hash_instances", + "vartype":"integer", + "max_value":"1024", + "scope":"{Global}", + "id":"1072", + "unit":"NULL", + "description":"The set of metadata locks can be partitioned into separatehashes to permit connections accessing different objects touse different locking hashes and reduce contention. Themetadata_locks_hash_instancessystem variable specifies the number of hashes (default 8).In MySQL 5.7.4 metadata locking implementation changes makethis variable unnecessary so it is deprecated and will beremoved in a future MySQL release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"6", + "name":"myisam_data_pointer_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"2", + "dynamic":"t", + "rank":"-1", + "summary":"Options for myisam_data_pointer_size", + "vartype":"integer", + "max_value":"7", + "scope":"{Global}", + "id":"1074", + "unit":"NULL", + "description":"The default pointer size in bytes to be used byCREATE TABLE forMyISAM tables when noMAX_ROWS option is specified. This variablecannot be less than 2 or larger than 7. The default value is6. See Section B.5.2.12 The table is full." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"9223372036854775807", + "name":"myisam_max_sort_file_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for myisam_max_sort_file_size", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"1075", + "unit":"NULL", + "description":"The maximum size of the temporary file that MySQL is permittedto use while re-creating a MyISAM index(during REPAIR TABLEALTER TABLE orLOAD DATAINFILE). If the file size would be larger than thisvalue the index is created using the key cache instead whichis slower. The value is given in bytes.If MyISAM index files exceed this size anddisk space is available increasing the value may helpperformance. The space must be available in the file systemcontaining the directory where the original index file islocated." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"18446744073709551615", + "name":"myisam_mmap_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"7", + "dynamic":"f", + "rank":"-1", + "summary":"Options for myisam_mmap_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"1076", + "unit":"NULL", + "description":"The maximum amount of memory to use for memory mappingcompressed MyISAM files. If manycompressed MyISAM tables are used thevalue can be decreased to reduce the likelihood ofmemory-swapping problems." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"BACKUP", + "name":"myisam_recover_options", + "deprecated":"f", + "valid_vals":"OFF,DEFAULT,BACKUP,FORCE,QUICK,", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for myisam_recover_options", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"1077", + "unit":"NULL", + "description":"The value of the--myisam-recover-optionsoption. See Section 5.1.3 Server Command Options." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"myisam_repair_threads", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for myisam_repair_threads", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global,Session}", + "id":"1078", + "unit":"NULL", + "description":"If this value is greater than 1 MyISAMtable indexes are created in parallel (each index in its ownthread) during the Repair by sortingprocess. The default value is 1." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"8388608", + "name":"myisam_sort_buffer_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"4096", + "dynamic":"t", + "rank":"-1", + "summary":"Options for myisam_sort_buffer_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{GlobalSession}", + "id":"1079", + "unit":"NULL", + "description":"The size of the buffer that is allocated when sortingMyISAM indexes during aREPAIR TABLE or when creatingindexes with CREATE INDEX orALTER TABLE.The maximum permissible setting formyisam_sort_buffer_size is4GB1. Larger values are permitted for 64-bit platforms." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"nulls_unequal", + "name":"myisam_stats_method", + "deprecated":"f", + "valid_vals":"nulls_equal,nulls_unequal,nulls_ignored", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for myisam_stats_method", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1080", + "unit":"NULL", + "description":"How the server treats NULL values whencollecting statistics about the distribution of index valuesfor MyISAM tables. This variable has threepossible values nulls_equalnulls_unequal andnulls_ignored. Fornulls_equal all NULLindex values are considered equal and form a single valuegroup that has a size equal to the number ofNULL values. Fornulls_unequal NULLvalues are considered unequal and eachNULL forms a distinct value group of size1. For nulls_ignoredNULL values are ignored.The method that is used for generating table statisticsinfluences how the optimizer chooses indexes for queryexecution as described in Section 8.3.7 InnoDB and MyISAM Index Statistics Collection." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"myisam_use_mmap", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for myisam_use_mmap", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1081", + "unit":"NULL", + "description":"Use memory mapping for reading and writingMyISAM tables." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"mysql_native_password_proxy_users", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for mysql_native_password_proxy_users", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1082", + "unit":"NULL", + "description":"This variable controls whether themysql_native_password built-inauthentication plugin supports proxy users. It has no effectunless the check_proxy_userssystem variable is enabled. For information about userproxying see Section 6.3.9 Proxy Users.This variable was added in MySQL 5.7.7. Before 5.7.7mysql_native_password does not supportproxy users." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"named_pipe", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for named_pipe", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1083", + "unit":"NULL", + "description":"(Windows only.) Indicates whether the server supportsconnections over named pipes." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"16384", + "name":"net_buffer_length", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1024", + "dynamic":"t", + "rank":"-1", + "summary":"Options for net_buffer_length", + "vartype":"integer", + "max_value":"1048576", + "scope":"{GlobalSession}", + "id":"1084", + "unit":"NULL", + "description":"Each client thread is associated with a connection buffer andresult buffer. Both begin with a size given bynet_buffer_length but aredynamically enlarged up tomax_allowed_packet bytes asneeded. The result buffer shrinks tonet_buffer_length after eachSQL statement.This variable should not normally be changed but if you havevery little memory you can set it to the expected length ofstatements sent by clients. If statements exceed this lengththe connection buffer is automatically enlarged. The maximumvalue to whichnet_buffer_length can be setis 1MB.The session value of this variable is read only." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"30", + "name":"net_read_timeout", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for net_read_timeout", + "vartype":"integer", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1085", + "unit":"NULL", + "description":"The number of seconds to wait for more data from a connectionbefore aborting the read. When the server is reading from theclient net_read_timeout isthe timeout value controlling when to abort. When the serveris writing to the clientnet_write_timeout is thetimeout value controlling when to abort. See alsoslave_net_timeout." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"INTERNAL", + "name":"pseudo_slave_mode", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for pseudo_slave_mode", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Session}", + "id":"1112", + "unit":"NULL", + "description":"This variable is for internal server use." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"FALSE", + "name":"new", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for new", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1088", + "unit":"NULL", + "description":"This variable was used in MySQL 4.0 to turn on some 4.1behaviors and is retained for backward compatibility. Itsvalue is always OFF.In MySQL Cluster setting this variable toON makes it possible to employ partitioningtypes other than KEY or LINEARKEY with NDB tables.This feature is experimental only and not supportedin production. For additional information seeUser-defined partitioning and the NDB storage engine (MySQL Cluster)." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"2", + "name":"ngram_token_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"f", + "rank":"-1", + "summary":"Options for ngram_token_size", + "vartype":"integer", + "max_value":"10", + "scope":"{Global}", + "id":"1089", + "unit":"NULL", + "description":"Defines the n-gram token size for the n-gram full-text parser.The ngram_token_size option is read-onlyand can only be modified at startup. The default value is 2(bigram). The maximum value is 10.For more information about how to configure this variable seeSection 12.9.8 ngram Full-Text Parser." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"offline_mode", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for offline_mode", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1090", + "unit":"NULL", + "description":"Whether the server is in offline mode whichhas these characteristics:Only users who have the SUPERprivilege can control offline mode. To put a server in offlinemode change the value of theoffline_mode system variablefrom OFF to ON. Toresume normal operations changeoffline_mode fromON to OFF. In offlinemode clients that are refused access receive anER_SERVER_OFFLINE_MODE error." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"old", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for old", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1091", + "unit":"NULL", + "description":"old is a compatibilityvariable. It is disabled by default but can be enabled atstartup to revert the server to behaviors present in olderversions.When old is enabled itchanges the default scope of index hints to that used prior toMySQL 5.1.17. That is index hints with noFOR clause apply only to how indexes areused for row retrieval and not to resolution of ORDERBY or GROUP BY clauses. (SeeSection 8.9.4 Index Hints.) Take care about enabling thisin a replication setup. With statement-based binary logginghaving different modes for the master and slaves might lead toreplication errors." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"old_alter_table", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for old-alter-table", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1092", + "unit":"NULL", + "description":"When this variable is enabled the server does not use theoptimized method of processing an ALTERTABLE operation. It reverts to using a temporarytable copying over the data and then renaming the temporarytable to the original as used by MySQL 5.0 and earlier. Formore information on the operation ofALTER TABLE seeSection 13.1.8 ALTER TABLE Syntax." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"old_passwords", + "deprecated":"t", + "valid_vals":"0,1,2", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for old_passwords", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1093", + "unit":"NULL", + "description":"This variable controls the password hashing method used by thePASSWORD() function. It alsoinfluences password hashing performed byCREATE USER andGRANT statements that specify apassword using an IDENTIFIED BY clause.The following table shows the permitted values ofold_passwords the passwordhashing method for each value and which authenticationplugins use passwords hashed with each method.If old_passwords=1PASSWORD(str)returns the same value asOLD_PASSWORD(str).The latter function is not affected by the value ofold_passwords.If you set old_passwords=2follow the instructions for using thesha256_password plugin atSection 6.4.1.4 The SHA-256 Authentication Plugin.The server sets the globalold_passwords value duringstartup to be consistent with the password hashing methodrequired by the default authentication plugin. The defaultplugin is mysql_native_password unless thedefault_authentication_pluginsystem variable is set otherwise.As of MySQL 5.7.1 when a client successfully connects to theserver the server sets the sessionold_passwords valueappropriately for the account authentication method. Forexample if the account uses thesha256_password authentication plugin theserver sets old_passwords=2.For additional information about authentication plugins andhashing formats seeSection 6.3.8 Pluggable Authentication andSection 6.1.2.4 Password Hashing in MySQL." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"5000", + "name":"open_files_limit", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"Options for open-files-limit", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"1094", + "unit":"NULL", + "description":"The number of files that the operating system permitsmysqld to open. The value of this variableat runtime is the real value permitted by the system and mightbe different from the value you specify at server startup. Thevalue is 0 on systems where MySQL cannot change the number ofopen files.The effectiveopen_files_limit value isbased on the value specified at system startup (if any) andthe values of max_connectionsand table_open_cache usingthese formulas:The server attempts to obtain the number of file descriptorsusing the maximum of those three values. If that manydescriptors cannot be obtained the server attempts to obtainas many as the system will permit." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"optimizer_prune_level", + "deprecated":"f", + "valid_vals":"1,0", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for optimizer_prune_level", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1095", + "unit":"NULL", + "description":"Controls the heuristics applied during query optimization toprune less-promising partial plans from the optimizer searchspace. A value of 0 disables heuristics so that the optimizerperforms an exhaustive search. A value of 1 causes theoptimizer to prune plans based on the number of rows retrievedby intermediate plans." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"62", + "name":"optimizer_search_depth", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for optimizer_search_depth", + "vartype":"integer", + "max_value":"62", + "scope":"{GlobalSession}", + "id":"1096", + "unit":"NULL", + "description":"The maximum depth of search performed by the query optimizer.Values larger than the number of relations in a query resultin better query plans but take longer to generate anexecution plan for a query. Values smaller than the number ofrelations in a query return an execution plan quicker but theresulting plan may be far from being optimal. If set to 0 thesystem automatically picks a reasonable value." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"INTERNAL", + "name":"pseudo_thread_id", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for pseudo_thread_id", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Session}", + "id":"1113", + "unit":"NULL", + "description":"This variable is for internal server use." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"InnoDB", + "name":"storage_engine", + "deprecated":"t", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for storage_engine", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1186", + "unit":"NULL", + "description":"This variable is deprecated and was removed in MySQL 5.7.5.Use default_storage_engineinstead." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"index_merge=onindex_merge_union=on index_merge_sort_union=onindex_merge_intersection=on engine_condition_pushdown=on", + "name":"optimizer_switch", + "deprecated":"f", + "valid_vals":"batched_key_access=on|off,block_nested_loop=on|off,engine_condition_pushdown=on|off,firstmatch=on|off,index_condition_pushdown=on|off,index_merge=on|off,index_merge_intersection=on|off,index_merge_sort_union=on|off,index_merge_union=on|off,loosescan=on|off,materialization=on|off,mrr=on|off,mrr_cost_based=on|off,semijoin=on|off,subquery_materialization_cost_based=on|off,use_index_extensions=on|off", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for optimizer_switch", + "vartype":"set", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1097", + "unit":"NULL", + "description":"The optimizer_switch systemvariable enables control over optimizer behavior. The value ofthis variable is a set of flags each of which has a value ofon or off to indicatewhether the corresponding optimizer behavior is enabled ordisabled. This variable has global and session values and canbe changed at runtime. The global default can be set at serverstartup.To see the current set of optimizer flags select the variablevalue:For more information about the syntax of this variable and theoptimizer behaviors that it controls seeSection 8.9.2 Controlling Switchable Optimizations." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"enabled=off", + "name":"optimizer_trace", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for optimizer_trace", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1098", + "unit":"NULL", + "description":"This variable controls optimizer tracing. For details seeMySQLInternals: Tracing the Optimizer." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"enabled=off", + "name":"optimizer_trace_features", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for optimizer_trace_features", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1099", + "unit":"NULL", + "description":"This variable enables or disables selected optimizer tracingfeatures. For details seeMySQLInternals: Tracing the Optimizer." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"optimizer_trace_limit", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for optimizer_trace_limit", + "vartype":"integer", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1100", + "unit":"NULL", + "description":"The maximum number of optimizer traces to display. Fordetails seeMySQLInternals: Tracing the Optimizer." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"16384", + "name":"optimizer_trace_max_mem_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for optimizer_trace_max_mem_size", + "vartype":"integer", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1101", + "unit":"NULL", + "description":"The maximum cumulative size of stored optimizer traces. Fordetails seeMySQLInternals: Tracing the Optimizer." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"-1", + "name":"optimizer_trace_offset", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for optimizer_trace_offset", + "vartype":"integer", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1102", + "unit":"NULL", + "description":"The offset of optimizer traces to display. For details seeMySQLInternals: Tracing the Optimizer." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"18446744073709551615", + "name":"parser_max_mem_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"400000", + "dynamic":"t", + "rank":"-1", + "summary":"Options for parser_max_mem_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{GlobalSession}", + "id":"1103", + "unit":"NULL", + "description":"The maximum amount of memory available to the parser. Thedefault value places no limit on memory available. The valuecan be reduced to protect against out-of-memory situationscaused by parsing long or complex SQL statements." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"pid_file", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for pid-file", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"1104", + "unit":"NULL", + "description":"The path name of the process ID (PID) file. This variable canbe set with the --pid-fileoption." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"BASEDIR/lib/plugin", + "name":"plugin_dir", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for plugin_dir", + "vartype":"directory name", + "max_value":"NULL", + "scope":"{Global}", + "id":"1105", + "unit":"NULL", + "description":"The path name of the plugin directory.If the plugin directory is writable by the server it may bepossible for a user to write executable code to a file in thedirectory using SELECT... INTO DUMPFILE. This can be prevented by makingplugin_dir read only to theserver or by setting--secure-file-priv to adirectory where SELECT writescan be made safely." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"3306", + "name":"port", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"Options for port", + "vartype":"integer", + "max_value":"65535", + "scope":"{Global}", + "id":"1106", + "unit":"NULL", + "description":"The number of the port on which the server listens for TCP/IPconnections. This variable can be set with the--port option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"32768", + "name":"preload_buffer_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1024", + "dynamic":"t", + "rank":"-1", + "summary":"Options for preload_buffer_size", + "vartype":"integer", + "max_value":"1073741824", + "scope":"{GlobalSession}", + "id":"1107", + "unit":"NULL", + "description":"The size of the buffer that is allocated when preloadingindexes." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"profiling", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{NA}", + "id":"1108", + "unit":"NULL", + "description":"If set to 0 or OFF (the default) statementprofiling is disabled. If set to 1 or ONstatement profiling is enabled and theSHOW PROFILE andSHOW PROFILES statementsprovide access to profiling information. SeeSection 13.7.5.31 SHOW PROFILES Syntax.This variable is deprecated and will be removed in a futureMySQL release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"15", + "name":"profiling_history_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"integer", + "max_value":"100", + "scope":"{NA}", + "id":"1109", + "unit":"NULL", + "description":"The number of statements for which to maintain profilinginformation if profiling isenabled. The default value is 15. The maximum value is 100.Setting the value to 0 effectively disables profiling. SeeSection 13.7.5.31 SHOW PROFILES Syntax.This variable is deprecated and will be removed in a futureMySQL release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"protocol_version", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for protocol_version", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"1110", + "unit":"NULL", + "description":"The version of the client/server protocol used by the MySQLserver." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"proxy_user", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for proxy_user", + "vartype":"string", + "max_value":"NULL", + "scope":"{Session}", + "id":"1111", + "unit":"NULL", + "description":"If the current client is a proxy for another user thisvariable is the proxy user account name. Otherwise thisvariable is NULL. SeeSection 6.3.9 Proxy Users." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"8192", + "name":"query_alloc_block_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1024", + "dynamic":"t", + "rank":"-1", + "summary":"Options for query_alloc_block_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{GlobalSession}", + "id":"1114", + "unit":"1024", + "description":"The allocation size of memory blocks that are allocated forobjects created during statement parsing and execution. If youhave problems with memory fragmentation it might help toincrease this parameter." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1048576", + "name":"query_cache_limit", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for query_cache_limit", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"1115", + "unit":"NULL", + "description":"Do not cache results that are larger than this number ofbytes. The default value is 1MB." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"4096", + "name":"query_cache_min_res_unit", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"512", + "dynamic":"t", + "rank":"-1", + "summary":"Options for query_cache_min_res_unit", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"1116", + "unit":"NULL", + "description":"The minimum size (in bytes) for blocks allocated by the querycache. The default value is 4096 (4KB). Tuning information forthis variable is given inSection 8.10.3.3 Query Cache Configuration." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1048576", + "name":"query_cache_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for query_cache_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"1117", + "unit":"NULL", + "description":"The amount of memory allocated for caching query results. Bydefault the query cache is disabled. This is achieved using adefault value of 1M with a default forquery_cache_type of 0. (To reduce overheadsignificantly if you set the size to 0 you should also startthe server withquery_cache_type=0.The permissible values are multiples of 1024; other values arerounded down to the nearest multiple.query_cache_size bytes ofmemory are allocated even ifquery_cache_type is set to 0.See Section 8.10.3.3 Query Cache Configuration for moreinformation.The query cache needs a minimum size of about 40KB to allocateits structures. (The exact size depends on systemarchitecture.) If you set the value ofquery_cache_size too small awarning will occur as described inSection 8.10.3.3 Query Cache Configuration." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"query_cache_type", + "deprecated":"f", + "valid_vals":"0,1,2", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for query_cache_type", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1118", + "unit":"NULL", + "description":"Set the query cache type. Setting theGLOBAL value sets the type for all clientsthat connect thereafter. Individual clients can set theSESSION value to affect their own use ofthe query cache. Possible values are shown in the followingtable.This variable defaults to OFF.If the server is started withquery_cache_type set to 0 it does notacquire the query cache mutex at all which means that thequery cache cannot be enabled at runtime and there is reducedoverhead in query execution." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"FALSE", + "name":"query_cache_wlock_invalidate", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for query_cache_wlock_invalidate", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1119", + "unit":"NULL", + "description":"Normally when one client acquires a WRITElock on a MyISAM table other clients arenot blocked from issuing statements that read from the tableif the query results are present in the query cache. Settingthis variable to 1 causes acquisition of aWRITE lock for a table to invalidate anyqueries in the query cache that refer to the table. Thisforces other clients that attempt to access the table to waitwhile the lock is in effect." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"8192", + "name":"query_prealloc_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"8192", + "dynamic":"t", + "rank":"-1", + "summary":"Options for query_prealloc_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{GlobalSession}", + "id":"1120", + "unit":"1024", + "description":"The size of the persistent buffer used for statement parsingand execution. This buffer is not freed between statements. Ifyou are running complex queries a largerquery_prealloc_size valuemight be helpful in improving performance because it canreduce the need for the server to perform memory allocationduring query execution operations." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"rand_seed1", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"integer", + "max_value":"NULL", + "scope":"{NA}", + "id":"1121", + "unit":"NULL", + "description":"The rand_seed1 andrand_seed2 variables exist assession variables only and can be set but not read. Thevariablesbut not their valuesare shown in theoutput of SHOW VARIABLES.The purpose of these variables is to support replication ofthe RAND() function. Forstatements that invoke RAND()the master passes two values to the slave where they are usedto seed the random number generator. The slave uses thesevalues to set the session variablesrand_seed1 andrand_seed2 so thatRAND() on the slave generatesthe same value as on the master." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"rand_seed2", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"integer", + "max_value":"NULL", + "scope":"{NA}", + "id":"1122", + "unit":"NULL", + "description":"See the description forrand_seed1." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"4096", + "name":"range_alloc_block_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"4096", + "dynamic":"t", + "rank":"-1", + "summary":"Options for range_alloc_block_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{GlobalSession}", + "id":"1123", + "unit":"1024", + "description":"The size of blocks that are allocated when doing rangeoptimization." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1536000", + "name":"range_optimizer_max_mem_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for range_optimizer_max_mem_size", + "vartype":"integer", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1124", + "unit":"NULL", + "description":"The limit on memory consumption for the range optimizer. Avalue of 0 means no limit. If an execution planconsidered by the optimizer uses the range access method butthe optimizer estimates that the amount of memory needed forthis method would exceed the limit it abandons the plan andconsiders other plans. For more information seeSection 8.2.1.3.4 Limiting Memory Use for Range Optimization." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"STRICT", + "name":"rbr_exec_mode", + "deprecated":"f", + "valid_vals":"IDEMPOTENT,STRICT", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for rbr_exec_mode", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Session}", + "id":"1125", + "unit":"NULL", + "description":"This variable switches the server betweenIDEMPOTENT mode andSTRICT mode. IDEMPOTENTmode causes suppression of duplicate-key and no-key-founderrors. This mode is useful when replaying a row-based binarylog on a server that causes conflicts with existing data.mysqlbinlog uses this mode when you set the--idempotent option bywriting the following to the output:" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"131072", + "name":"read_buffer_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"8200", + "dynamic":"t", + "rank":"-1", + "summary":"Options for read_buffer_size", + "vartype":"integer", + "max_value":"2147479552", + "scope":"{GlobalSession}", + "id":"1126", + "unit":"NULL", + "description":"Each thread that does a sequential scan for aMyISAM table allocates a buffer of thissize (in bytes) for each table it scans. If you do manysequential scans you might want to increase this value whichdefaults to 131072. The value of this variable should be amultiple of 4KB. If it is set to a value that is not amultiple of 4KB its value will be rounded down to the nearestmultiple of 4KB.This option is also used in the following context for allstorage engines:and in one other storage engine-specific way: to determine thememory block size for MEMORYtables.The maximum permissible setting forread_buffer_size is 2GB.For more information about memory use during differentoperations see Section 8.12.5.1 How MySQL Uses Memory." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"read_only", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for read_only", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1127", + "unit":"NULL", + "description":"When the read_only systemvariable is enabled the server permits no client updatesexcept from users who have theSUPER privilege. This variableis disabled by default.As of MySQL 5.7.8 the server also supports asuper_read_only systemvariable (disabled by default) which has these effects:Even with read_only enabledthe server permits these operations:Changes to read_only on amaster server are not replicated to slave servers. The valuecan be set on a slave server independent of the setting on themaster.The following conditions apply to attempts to enableread_only (including implicitattempts resulting from enablingsuper_read_only):" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"262144", + "name":"read_rnd_buffer_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for read_rnd_buffer_size", + "vartype":"integer", + "max_value":"2147483647", + "scope":"{GlobalSession}", + "id":"1128", + "unit":"NULL", + "description":"This variable is used for reads from MyISAMtables and for any storage engine for Multi-Range Readoptimization.When reading rows from a MyISAM table insorted order following a key-sorting operation the rows areread through this buffer to avoid disk seeks. SeeSection 8.2.1.15 ORDER BY Optimization. Setting the variableto a large value can improve ORDER BYperformance by a lot. However this is a buffer allocated foreach client so you should not set the global variable to alarge value. Instead change the session variable only fromwithin those clients that need to run large queries.The maximum permissible setting forread_rnd_buffer_size is 2GB.For more information about memory use during differentoperations see Section 8.12.5.1 How MySQL Uses Memory. For informationabout Multi-Range Read optimization seeSection 8.2.1.13 Multi-Range Read Optimization." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"TRUE", + "name":"relay_log_purge", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for relay_log_purge", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1129", + "unit":"NULL", + "description":"Disables or enables automatic purging of relay log files assoon as they are not needed any more. The default value is 1(ON)." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"relay_log_space_limit", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"Options for relay_log_space_limit", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"1130", + "unit":"NULL", + "description":"The maximum amount of space to use for all relay logs." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"report_host", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for report-host", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"1131", + "unit":"NULL", + "description":"The value of the --report-hostoption." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"report_password", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for report-password", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"1132", + "unit":"NULL", + "description":"The value of the--report-password option. Notthe same as the password used for the MySQL replication useraccount." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"report_port", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"Options for report-port", + "vartype":"integer", + "max_value":"65535", + "scope":"{Global}", + "id":"1133", + "unit":"NULL", + "description":"The value of the --report-portoption." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"report_user", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for report-user", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"1134", + "unit":"NULL", + "description":"The value of the --report-useroption. Not the same as the name for the MySQL replicationuser account." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"require_secure_transport", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for require_secure_transport", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1135", + "unit":"NULL", + "description":"Whether client connections to the server are required to usesome form of secure transport. When this variable is enabledthe server permits only TCP/IP connections that use SSL orconnections that use a socket file (on Unix) or shared memory(on Windows). The server rejects nonsecure connectionattempts which fail with anER_SECURE_TRANSPORT_REQUIREDerror.This capability supplements per-account SSL requirementswhich take precedence. For exmaple if an account is definedwith REQUIRE SSL enablingrequire_secure_transport doesnot make it possible to use the account to connect using aUnix socket file.It is possible for a server to have no secure transportsavailable. For example a server on Windows supports no securetransports if started without specifying any SSL certificateor key files and with theshared_memory system variabledisabled. Under these conditions attempts to enablerequire_secure_transport atstartup cause the server to write a message to the error logand exit. Attempts to enable the variable at runtime fail withanER_NO_SECURE_TRANSPORTS_CONFIGUREDerror." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"rpl_semi_sync_master_enabled", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for rpl_semi_sync_master_enabled", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1136", + "unit":"NULL", + "description":"Controls whether semisynchronous replication is enabled on themaster. To enable or disable the plugin set this variable toON or OFF (or 1 or 0)respectively. The default is OFF.This variable is available only if the master-sidesemisynchronous replication plugin is installed." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"off", + "name":"debug_print_parse", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Logs each query's parse tree.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1503", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"10000", + "name":"rpl_semi_sync_master_timeout", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for rpl_semi_sync_master_timeout", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"1137", + "unit":"NULL", + "description":"A value in milliseconds that controls how long the masterwaits on a commit for acknowledgment from a slave beforetiming out and reverting to asynchronous replication. Thedefault value is 10000 (10 seconds).This variable is available only if the master-sidesemisynchronous replication plugin is installed." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"32", + "name":"rpl_semi_sync_master_trace_level", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for rpl_semi_sync_master_trace_level", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"1138", + "unit":"NULL", + "description":"The semisynchronous replication debug trace level on themaster. Four levels are defined:This variable is available only if the master-sidesemisynchronous replication plugin is installed." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"rpl_semi_sync_master_wait_for_slave_count", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for rpl_semi_sync_master_wait_for_slave_count", + "vartype":"integer", + "max_value":"65535", + "scope":"{Global}", + "id":"1139", + "unit":"NULL", + "description":"The number of slave acknowledgments the master must receiveper transaction before proceeding. By defaultrpl_semi_sync_master_wait_for_slave_countis 1 meaning that semisynchronousreplication proceeds after receiving a single slaveacknowledgment. Performance is best for small values of thisvariable.For example ifrpl_semi_sync_master_wait_for_slave_countis 2 then 2 slaves must acknowledgereceipt of the transaction before the timeout periodconfigured byrpl_semi_sync_master_timeoutfor semisynchronous replication to proceed. If less slavesacknowledge receipt of the transaction during the timeoutperiod the master reverts to normal replication.This variable is available only if the master-sidesemisynchronous replication plugin is installed." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"rpl_semi_sync_master_wait_no_slave", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for rpl_semi_sync_master_wait_no_slave", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1140", + "unit":"NULL", + "description":"Controls whether the master waits for the timeout periodconfigured byrpl_semi_sync_master_timeoutto expire even if the slave count drops to less than thenumber of slaves configured byrpl_semi_sync_master_wait_for_slave_countduring the timeout period.When the value ofrpl_semi_sync_master_wait_no_slave isON (the default) it is permissible for theslave count to drop to less thanrpl_semi_sync_master_wait_for_slave_countduring the timeout period. As long as enough slavesacknowledge the transaction before the timeout period expiressemisynchronous replication continues.When the value ofrpl_semi_sync_master_wait_no_slave isOFF if the slave count drops to less thanthe number configured inrpl_semi_sync_master_wait_for_slave_countat any time during the timeout period configured byrpl_semi_sync_master_timeoutthe master reverts to normal replication.This variable is available only if the master-sidesemisynchronous replication plugin is installed." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"AFTER_SYNC", + "name":"rpl_semi_sync_master_wait_point", + "deprecated":"f", + "valid_vals":"AFTER_SYNC,AFTER_COMMIT", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for rpl_semi_sync_master_wait_point", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"1141", + "unit":"NULL", + "description":"This variable controls the point at which a semisynchronousreplication master waits for slave acknowledgment oftransaction receipt before returning a status to the clientthat committed the transaction. These values are permitted:The replication characteristics of these settings differ asfollows:This variable is available only if the master-sidesemisynchronous replication plugin is installed.rpl_semi_sync_master_wait_pointwas added in MySQL 5.7.2. For older versions semisynchronousmaster behavior is equivalent to a setting ofAFTER_COMMIT.This change introduces a version compatibility constraintbecause it increments the semisynchronous interface version:Servers for MySQL 5.7.2 and up do not work withsemisynchronous replication plugins from older versions nordo servers from older versions work with semisynchronousreplication plugins for MySQL 5.7.2 and up." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"rpl_semi_sync_slave_enabled", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for rpl_semi_sync_slave_enabled", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1142", + "unit":"NULL", + "description":"Controls whether semisynchronous replication is enabled on theslave. To enable or disable the plugin set this variable toON or OFF (or 1 or 0)respectively. The default is OFF.This variable is available only if the slave-sidesemisynchronous replication plugin is installed." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"32", + "name":"rpl_semi_sync_slave_trace_level", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for rpl_semi_sync_slave_trace_level", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"1143", + "unit":"NULL", + "description":"The semisynchronous replication debug trace level on theslave. Seerpl_semi_sync_master_trace_levelfor the permissible values.This variable is available only if the slave-sidesemisynchronous replication plugin is installed." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"secure_auth", + "deprecated":"t", + "valid_vals":"OFF,ON", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for secure-auth", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1144", + "unit":"NULL", + "description":"If this variable is enabled the server blocks connections byclients that attempt to use accounts that have passwordsstored in the old (pre-4.1) format.Enable this variable to prevent all use of passwords employingthe old format (and hence insecure communication over thenetwork).As of MySQL 5.7.5 this variable is deprecated and will beremoved in a future MySQL release. It is always enabled andattempting to disable it produces an error. Before MySQL5.7.5 this variable is enabled by default but can bedisabled.Server startup fails with an error if this variable is enabledand the privilege tables are in pre-4.1 format. SeeSection B.5.2.4 Client does not support authentication protocol." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"ssl_crlpath", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for ssl-crlpath", + "vartype":"directory name", + "max_value":"NULL", + "scope":"{Global}", + "id":"1184", + "unit":"NULL", + "description":"The path to a directory that contains files containingcertificate revocation lists in PEM format. Revocation listswork for MySQL distributions compiled using OpenSSL (but notyaSSL). See Section 6.3.11.1 OpenSSL Versus yaSSL." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"empty", + "name":"secure_file_priv", + "deprecated":"f", + "valid_vals":"empty,dirname", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for secure-file-priv", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"1145", + "unit":"NULL", + "description":"This variable is used to limit the effect of data import andexport operations such as those performed by theLOAD DATA andSELECT ... INTOOUTFILE statements and theLOAD_FILE() function. Theseoperations are permitted only to users who have theFILE privilege.secure_file_priv may be setas follows:Before MySQL 5.7.6 this variable is empty by default. As of5.7.6 the default value is platform specific and depends onthe value of the INSTALL_LAYOUTCMake option as shown in the followingtable. To specify the defaultsecure_file_priv valueexplicitly if you are building from source use theINSTALL_SECURE_FILE_PRIVDIRCMake option.As of MySQL 5.7.8 to set the defaultsecure_file_priv value forthe libmysqld embedded server use theINSTALL_SECURE_FILE_PRIV_EMBEDDEDDIRCMake option. The default value for thisoption is NULL.As of MySQL 5.7.6 the server checks the value ofsecure_file_priv at startupand writes a warning to the error log if the value isinsecure. The setting is considered insecure ifsecure_file_priv has an emptyvalue or the value is the data directory or a subdirectory ofit or a directory that is accessible by all users. Ifsecure_file_priv is set to anonexistent path the server writes an error message to theerror log and exits." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"server_id", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for server-id", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{Global}", + "id":"1146", + "unit":"NULL", + "description":"The server ID used in replication to give each master andslave a unique identity. This variable is set by the--server-id option. For eachserver participating in replication you should pick apositive integer in the range from 1 to2321 to act as thatserver's ID." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"session_track_gtids", + "deprecated":"f", + "valid_vals":"OFF,OWN_GTID,ALL_GTIDS ", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for session_track_gtids", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1147", + "unit":"NULL", + "description":"Controls a tracker for capturing GTIDs and returning them inthe OK packet. Depending on the value of this option at theend of executing a transaction the GTIDs specified arecaptured by the tracker and appended to the OK packet. Thepossible sets of GTIDs to track are:For information about obtaining session state-changeinformation within client programs seeSection 24.8.7.65 mysql_session_track_get_first()." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"session_track_schema", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for session_track_schema", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1148", + "unit":"NULL", + "description":"Controls whether the server tracks changes to the defaultschema (database) name within the current session and makesthis information available to the client when changes occur.If notification is enabled any setting of the default schemais reported even if the new schema name is the same as theold.For information about obtaining session state-changeinformation within client programs seeSection 24.8.7.65 mysql_session_track_get_first()." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"session_track_state_change", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for session_track_state_change", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1149", + "unit":"NULL", + "description":"Controls whether the server tracks changes to the state of thecurrent session and notifies the client when state changesoccur. Session state consists of these values:If the session-state tracker is enabled any assignments tosession state values are reported even if the new values arethe same as the old.Thesession_track_state_changevariable controls only notification of when changes occur notwhat the changes are. To receive notification for changes tothe default schema name and session system variable valuesuse the session_track_schemaandsession_track_system_variablessystem variables.For information about obtaining session state-changeinformation within client programs seeSection 24.8.7.65 mysql_session_track_get_first()." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"time_zone autocommit character_set_client character_set_results character_set_connection", + "name":"session_track_system_variables", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for session_track_system_variables", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1150", + "unit":"NULL", + "description":"Controls whether the server tracks changes to the sessionsystem variables and makes this information available to theclient when changes occur. The variable value is acomma-separated list of variables for which to track changes.By default notification is enabled fortime_zoneautocommitcharacter_set_clientcharacter_set_results andcharacter_set_connection.(The latter three variables are those affected bySETNAMES.)The special value * causes the server totrack changes to all session variables. If given this valuemust be specified by itself without specific system variablenames.Notification occurs for all assignments to tracked sessionsystem variables even if the new values are the same as theold.For information about obtaining session state-changeinformation within client programs seeSection 24.8.7.65 mysql_session_track_get_first()." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"skip_external_locking", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for skip_external_locking", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1159", + "unit":"NULL", + "description":"This is OFF if mysqlduses external locking (system locking) ONif external locking is disabled. This affects onlyMyISAM table access.This variable is set by the--external-locking or--skip-external-lockingoption. External locking is disabled by default.External locking affects onlyMyISAM table access. For moreinformation including conditions under which it can andcannot be used see Section 8.11.5 External Locking." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"ssl_key", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for ssl-key", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"1185", + "unit":"NULL", + "description":"The name of the SSL key file to use for establishing a secureconnection." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"off", + "name":"debug_print_plan", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Logs each query's execution plan.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1504", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"sha256_password_auto_generate_rsa_keys", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for sha256_password_auto_generate_rsa_keys", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1151", + "unit":"NULL", + "description":"This variable is available if the server was compiled usingOpenSSL (see Section 6.3.11.1 OpenSSL Versus yaSSL). Itcontrols whether the server autogenerates RSA private/publickey-pair files in the data directory if they do not alreadyexist.At startup the server automatically generates RSAprivate/public key-pair files in the data directory if thesha256_password_auto_generate_rsa_keyssystem variable is enabled no RSA options are specified andthe RSA files are missing from the data directory. These filesenable secure password exchange using RSA over unencryptedconnections for accounts authenticated by thesha256_password plugin; seeSection 6.4.1.4 The SHA-256 Authentication Plugin.For more information about RSA file autogeneration includingfile names and characteristics seeSection 6.3.12.1 Creating SSL and RSA Certificates and Keys using MySQLThe auto_generate_certssystem variable is related but controls autogeneration of SSLcertificate and key files needed for secure connections usingSSL." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"private_key.pem", + "name":"sha256_password_private_key_path", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for sha256_password_private_key_path", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"1152", + "unit":"NULL", + "description":"This variable is available if MySQL was compiled using OpenSSL(see Section 6.3.11.1 OpenSSL Versus yaSSL). Its value is thepath name of the RSA private key file for thesha256_password authentication plugin. Ifthe file is named as a relative path it is interpretedrelative to the server data directory. The file must be in PEMformat. Because this file stores a private key its accessmode should be restricted so that only the MySQL server canread it.For information about sha256_passwordincluding instructions for creating the RSA key files seeSection 6.4.1.4 The SHA-256 Authentication Plugin." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"sha256_password_proxy_users", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sha256_password_proxy_users", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1153", + "unit":"NULL", + "description":"This variable controls whether thesha256_password built-in authenticationplugin supports proxy users. It has no effect unless thecheck_proxy_users systemvariable is enabled. For information about user proxying seeSection 6.3.9 Proxy Users.This variable was added in MySQL 5.7.7. Before 5.7.7sha256_password does not support proxyusers." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"public_key.pem", + "name":"sha256_password_public_key_path", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for sha256_password_public_key_path", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"1154", + "unit":"NULL", + "description":"This variable is available if MySQL was compiled using OpenSSL(see Section 6.3.11.1 OpenSSL Versus yaSSL). Its value is thepath name of the RSA public key file for thesha256_password authentication plugin. Ifthe file is named as a relative path it is interpretedrelative to the server data directory. The file must be in PEMformat. Because this file stores a public key copies can befreely distributed to client users. (Clients that explicitlyspecify a public key when connecting to the server using RSApassword encryption must use the same public key as that usedby the server.)For information about sha256_passwordincluding instructions for creating the RSA key files and howclients specify the RSA public key seeSection 6.4.1.4 The SHA-256 Authentication Plugin." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"FALSE", + "name":"shared_memory", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for shared_memory", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1155", + "unit":"NULL", + "description":"(Windows only.) Whether the server permits shared-memoryconnections." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"MYSQL", + "name":"shared_memory_base_name", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for shared_memory_base_name", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"1156", + "unit":"NULL", + "description":"(Windows only.) The name of shared memory to use forshared-memory connections. This is useful when runningmultiple MySQL instances on a single physical machine. Thedefault name is MYSQL. The name is casesensitive." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"show_compatibility_56", + "deprecated":"t", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for show_compatibility_56", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1157", + "unit":"NULL", + "description":"The INFORMATION_SCHEMA has tables thatcontain system and status variable information (seeSection 21.10 The INFORMATION_SCHEMA GLOBAL_VARIABLES and SESSION_VARIABLES Tables andSection 21.9 The INFORMATION_SCHEMA GLOBAL_STATUS and SESSION_STATUS Tables). As of MySQL 5.7.6 thePerformance Schema also contains system and status variabletables (seeSection 22.9.12 Performance Schema System Variable TablesandSection 22.9.13 Performance Schema Status Variable Tables).The Performance Schema tables are intended to replace theINFORMATION_SCHEMA tables which aredeprecated as of MySQL 5.7.6 and will be removed in a futureMySQL release.For advice on migrating away from theINFORMATION_SCHEMA tables to thePerformance Schema tables seeSection 22.17 Migrating to Performance Schema System and Status Variable Tables.To assist in the migration you can use theshow_compatibility_56 systemvariable which affects whether MySQL 5.6 compatibility isenabled with respect to how system and status variableinformation is provided by theINFORMATION_SCHEMA and Performance Schematables and also by the SHOWVARIABLES and SHOWSTATUS statements.The following discussion describes the effects ofshow_compatibility_56:For better understanding it is strongly recommended that youalso read these sections:The show_compatibility_56system variable affects these aspects of server operationregarding system and status variables:This list summarizes the effects ofshow_compatibility_56 withadditional details given later:The following descriptions detail the effect of settingshow_compatibility_56 toON or OFF in thecontexts in which this variable applies.SHOW GLOBALVARIABLES statement:SHOW [SESSION| LOCAL] VARIABLES statement:SHOW GLOBALSTATUS statement:SHOW [SESSION |LOCAL] STATUS statement:In MySQL 5.7.6 and 5.7.7 for each of theSHOW statements just described use of aWHERE clause produces a warning whenshow_compatibility_56=ON and an error whenshow_compatibility_56=OFF. (This applies toWHERE clauses that are not optimized away.For example WHERE 1 is trivially true isoptimized away and thus produces no warning or error.) Thisbehavior does not occur as of MySQL 5.7.8;WHERE is supported as before 5.7.6.INFORMATION_SCHEMA tables(GLOBAL_VARIABLESSESSION_VARIABLESGLOBAL_STATUSandSESSION_STATUS):Performance Schema system variable tables:Performance Schema status variable tables:Slave status variables:FLUSH STATUSstatement:" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"show_old_temporals", + "deprecated":"t", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for show_old_temporals", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1158", + "unit":"NULL", + "description":"Whether SHOW CREATE TABLEoutput includes comments to flag temporal columns found to bein pre-5.6.4 format (TIMEDATETIME andTIMESTAMP columns withoutsupport for fractional seconds precision). This variable isdisabled by default. If enabled SHOWCREATE TABLE output looks like this:Output for the COLUMN_TYPE column of theINFORMATION_SCHEMA.COLUMNS tableis affected similarly.This variable is deprecated and will be removed in a futureMySQL release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"ssl_cert", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for ssl-cert", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"1181", + "unit":"NULL", + "description":"The name of the SSL certificate file to use for establishing asecure connection." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"skip_name_resolve", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for skip-name-resolve", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1160", + "unit":"NULL", + "description":"This variable is set from the value of the--skip-name-resolve option. Ifit is OFF mysqldresolves host names when checking client connections. If it isON mysqld uses only IPnumbers; in this case all Host columnvalues in the grant tables must be IP addresses orlocalhost. SeeSection 8.12.6.2 DNS Lookup Optimization and the Host Cache." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"skip_networking", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for skip-networking", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1161", + "unit":"NULL", + "description":"This is ON if the server permits only local(non-TCP/IP) connections. On Unix local connections use aUnix socket file. On Windows local connections use a namedpipe or shared memory. This variable can be set toON with the--skip-networking option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"skip_show_database", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for skip-show-database", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1162", + "unit":"NULL", + "description":"This prevents people from using the SHOWDATABASES statement if they do not have theSHOW DATABASES privilege. Thiscan improve security if you have concerns about users beingable to see databases belonging to other users. Its effectdepends on the SHOW DATABASESprivilege: If the variable value is ON theSHOW DATABASES statement ispermitted only to users who have the SHOWDATABASES privilege and the statement displays alldatabase names. If the value is OFFSHOW DATABASES is permitted toall users but displays the names of only those databases forwhich the user has the SHOWDATABASES or other privilege. (Note thatany global privilege is considered aprivilege for the database.)" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"2", + "name":"slow_launch_time", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for slow_launch_time", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"1163", + "unit":"NULL", + "description":"If creating a thread takes longer than this many seconds theserver increments theSlow_launch_threads statusvariable." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"slow_query_log", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for slow-query-log", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1164", + "unit":"NULL", + "description":"Whether the slow query log is enabled. The value can be 0 (orOFF) to disable the log or 1 (orON) to enable the log. The default valuedepends on whether the--slow_query_log option isgiven. The destination for log output is controlled by thelog_output system variable;if that value is NONE no log entries arewritten even if the log is enabled.Slow is determined by the value of thelong_query_time variable. SeeSection 5.4.5 The Slow Query Log." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"host_name-slow.log", + "name":"slow_query_log_file", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for slow_query_log_file", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"1165", + "unit":"NULL", + "description":"The name of the slow query log file. The default value ishost_name-slow.logbut the initial value can be changed with the--slow_query_log_file option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"/tmp/mysql.sock", + "name":"socket", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for socket", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"1166", + "unit":"NULL", + "description":"On Unix platforms this variable is the name of the socketfile that is used for local client connections. The default is/tmp/mysql.sock. (For some distributionformats the directory might be different such as/var/lib/mysql for RPMs.)On Windows this variable is the name of the named pipe thatis used for local client connections. The default value isMySQL (not case sensitive)." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"262144", + "name":"sort_buffer_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"32768", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sort_buffer_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{GlobalSession}", + "id":"1167", + "unit":"NULL", + "description":"Each session that must perform a sort allocates a buffer ofthis size. sort_buffer_sizeis not specific to any storage engine and applies in a generalmanner for optimization. At minimum thesort_buffer_size value mustbe large enough to accommodate fifteen tuples in the sortbuffer. Also increasing the value ofmax_sort_length may requireincreasing the value ofsort_buffer_size. For moreinformation see Section 8.2.1.15 ORDER BY OptimizationIf you see manySort_merge_passes per secondin SHOW GLOBALSTATUS output you can consider increasing thesort_buffer_size value tospeed up ORDER BY or GROUPBY operations that cannot be improved with queryoptimization or improved indexing.The optimizer tries to work out how much space is needed butcan allocate more up to the limit. Setting it larger thanrequired globally will slow down most queries that sort. It isbest to increase it as a session setting and only for thesessions that need a larger size. On Linux there arethresholds of 256KB and 2MB where larger values maysignificantly slow down memory allocation so you shouldconsider staying below one of those values. Experiment to findthe best value for your workload. SeeSection B.5.3.5 Where MySQL Stores Temporary Files.The maximum permissible setting forsort_buffer_size is4GB1. Larger values are permitted for 64-bit platforms(except 64-bit Windows for which large values are truncatedto 4GB1 with a warning)." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"sql_auto_is_null", + "deprecated":"f", + "valid_vals":"1,0", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sql_auto_is_null", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1168", + "unit":"NULL", + "description":"If this variable is set to 1 then after a statement thatsuccessfully inserts an automatically generatedAUTO_INCREMENT value you can find thatvalue by issuing a statement of the following form:If the statement returns a row the value returned is the sameas if you invoked theLAST_INSERT_ID() function. Fordetails including the return value after a multiple-rowinsert see Section 12.14 Information Functions. If noAUTO_INCREMENT value was successfullyinserted the SELECT statementreturns no row.The behavior of retrieving anAUTO_INCREMENT value by using anIS NULL comparison is used bysome ODBC programs such as Access. SeeObtaining Auto-Increment Values.This behavior can be disabled by settingsql_auto_is_null to 0.The default value ofsql_auto_is_null is 0." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"ssl_cipher", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for ssl-cipher", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"1182", + "unit":"NULL", + "description":"A list of permissible ciphers to use for SSL encryption." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"ssl_crl", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for ssl-crl", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"1183", + "unit":"NULL", + "description":"The path to a file containing certificate revocation lists inPEM format. Revocation lists work for MySQL distributionscompiled using OpenSSL (but not yaSSL). SeeSection 6.3.11.1 OpenSSL Versus yaSSL." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"sql_big_selects", + "deprecated":"f", + "valid_vals":"1,0", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sql_big_selects", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1169", + "unit":"NULL", + "description":"If set to 0 MySQL abortsSELECT statements that arelikely to take a very long time to execute (that isstatements for which the optimizer estimates that the numberof examined rows exceeds the value ofmax_join_size). This isuseful when an inadvisable WHERE statementhas been issued. The default value for a new connection is 1which permits all SELECTstatements.If you set the max_join_sizesystem variable to a value other thanDEFAULTsql_big_selects is set to 0." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"sql_buffer_result", + "deprecated":"f", + "valid_vals":"1,0", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sql_buffer_result", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1170", + "unit":"NULL", + "description":"If set to 1sql_buffer_result forcesresults from SELECT statementsto be put into temporary tables. This helps MySQL free thetable locks early and can be beneficial in cases where ittakes a long time to send results to the client. The defaultvalue is 0." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"sql_log_bin", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sql_log_bin", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Session}", + "id":"1171", + "unit":"NULL", + "description":"This variable controls whether logging to the binary log isdone. The default value is 1 (do logging). To change loggingfor the current session change the session value of thisvariable. The session user must have theSUPER privilege to set thisvariable.Setting this variable to 0 prevents GTIDs from beingassigned to transactions in the binary log. If youare using GTIDs for replication this means that even whenbinary logging is later enabled once again the GTIDs writteninto the log from this point do not account for anytransactions that occurred in the meantimein effectthose transactions are lost.In MySQL 5.7 it is not possible to set@@session.sql_log_bin within a transactionor subquery. (Bug #53437)" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"sql_log_off", + "deprecated":"f", + "valid_vals":"1,0", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sql_log_off", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1172", + "unit":"NULL", + "description":"This variable controls whether logging to the general querylog is done. The default value is 0 (do logging). To changelogging for the current session change the session value ofthis variable. The session user must have theSUPER privilege to set thisoption. The default value is 0." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"NO_ENGINE_SUBSTITUTION", + "name":"sql_mode", + "deprecated":"f", + "valid_vals":"ALLOW_INVALID_DATES,ANSI_QUOTES,ERROR_FOR_DIVISION_BY_ZERO,HIGH_NOT_PRECEDENCE,IGNORE_SPACE,NO_AUTO_CREATE_USER,NO_AUTO_VALUE_ON_ZERO,NO_BACKSLASH_ESCAPES,NO_DIR_IN_CREATE,NO_ENGINE_SUBSTITUTION,NO_FIELD_OPTIONS,NO_KEY_OPTIONS,NO_TABLE_OPTIONS,NO_UNSIGNED_SUBTRACTION,NO_ZERO_DATE,NO_ZERO_IN_DATE,ONLY_FULL_GROUP_BY,PAD_CHAR_TO_FULL_LENGTH,PIPES_AS_CONCAT,REAL_AS_FLOAT,STRICT_ALL_TABLES,STRICT_TRANS_TABLES", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sql-mode", + "vartype":"set", + "max_value":"NULL", + "scope":"{Global,Session}", + "id":"1173", + "unit":"NULL", + "description":"The current server SQL mode which can be set dynamically. Fordetails see Section 5.1.7 Server SQL Modes." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"sql_notes", + "deprecated":"f", + "valid_vals":"1,0", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{NA}", + "id":"1174", + "unit":"NULL", + "description":"If set to 1 (the default) warnings of Notelevel increment warning_count and theserver records them. If set to 0 Notewarnings do not incrementwarning_count and the serverdoes not record them. mysqldump includesoutput to set this variable to 0 so that reloading the dumpfile does not produce warnings for events that do not affectthe integrity of the reload operation." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"sql_quote_show_create", + "deprecated":"f", + "valid_vals":"1,0", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{NA}", + "id":"1175", + "unit":"NULL", + "description":"If set to 1 (the default) the server quotes identifiers forSHOW CREATE TABLE andSHOW CREATE DATABASEstatements. If set to 0 quoting is disabled. This option isenabled by default so that replication works for identifiersthat require quoting. See Section 13.7.5.10 SHOW CREATE TABLE Syntaxand Section 13.7.5.6 SHOW CREATE DATABASE Syntax." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"sql_safe_updates", + "deprecated":"f", + "valid_vals":"1,0", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{NA}", + "id":"1176", + "unit":"NULL", + "description":"If set to 1 MySQL abortsUPDATE orDELETE statements that do notuse a key in the WHERE clause or aLIMIT clause. (SpecificallyUPDATE statements must have aWHERE clause that uses a key or aLIMIT clause or both.DELETE statements must haveboth.) This makes it possible to catchUPDATE orDELETE statements where keysare not used properly and that would probably change or deletea large number of rows. The default value is 0." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"18446744073709551615", + "name":"sql_select_limit", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sql_select_limit", + "vartype":"integer", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1177", + "unit":"NULL", + "description":"The maximum number of rows to return fromSELECT statements. The defaultvalue for a new connection is the maximum number of rows thatthe server permits per table. Typical default values are(232)1 or(264)1. If you have changedthe limit the default value can be restored by assigning avalue of DEFAULT.If a SELECT has aLIMIT clause the LIMITtakes precedence over the value ofsql_select_limit." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"sql_warnings", + "deprecated":"f", + "valid_vals":"1,0", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{NA}", + "id":"1178", + "unit":"NULL", + "description":"This variable controls whether single-rowINSERT statements produce aninformation string if warnings occur. The default is 0. Setthe value to 1 to produce an information string." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"ssl_ca", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for ssl-ca", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"1179", + "unit":"NULL", + "description":"The path to a file with a list of trusted SSL CAs." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"ssl_capath", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for ssl-capath", + "vartype":"directory name", + "max_value":"NULL", + "scope":"{Global}", + "id":"1180", + "unit":"NULL", + "description":"The path to a directory that contains trusted SSL CAcertificates in PEM format." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"256", + "name":"stored_program_cache", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"256", + "dynamic":"t", + "rank":"-1", + "summary":"Options for stored_program_cache", + "vartype":"integer", + "max_value":"524288", + "scope":"{Global}", + "id":"1187", + "unit":"NULL", + "description":"Sets a soft upper limit for the number of cached storedroutines per connection. The value of this variable isspecified in terms of the number of stored routines held ineach of the two caches maintained by the MySQL Server forrespectively stored procedures and stored functions.Whenever a stored routine is executed this cache size ischecked before the first or top-level statement in the routineis parsed; if the number of routines of the same type (storedprocedures or stored functions according to which is beingexecuted) exceeds the limit specified by this variable thecorresponding cache is flushed and memory previously allocatedfor cached objects is freed. This allows the cache to beflushed safely even when there are dependencies betweenstored routines." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"super_read_only", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for super_read_only", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1188", + "unit":"NULL", + "description":"If the read_only systemvariable is enabled the server permits client updates onlyfrom users who have the SUPERprivilege. If thesuper_read_only systemvariable is also enabled the server prohibits client updateseven from users who have SUPER.See the description of theread_only system variable fora description of read-only mode and information about howread_only andsuper_read_only interact.Changes to super_read_only ona master server are not replicated to slave servers. The valuecan be set on a slave server independent of the setting on themaster." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"TRUE", + "name":"sync_frm", + "deprecated":"t", + "valid_vals":"TRUE,FALSE", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sync_frm", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1189", + "unit":"NULL", + "description":"If this variable is set to 1 when any nontemporary table iscreated its .frm file is synchronized todisk (using fdatasync()). This is slowerbut safer in case of a crash. The default is 1.This variable is deprecated in MySQL 5.7.6 and will be removedin a future version of MySQL (when .frmfiles become obsolete)." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"system_time_zone", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for system_time_zone", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"1190", + "unit":"NULL", + "description":"The server system time zone. When the server begins executingit inherits a time zone setting from the machine defaultspossibly modified by the environment of the account used forrunning the server or the startup script. The value is used toset system_time_zone.Typically the time zone is specified by theTZ environment variable. It also can bespecified using the--timezone option of themysqld_safe script.The system_time_zone variablediffers from time_zone.Although they might have the same value the latter variableis used to initialize the time zone for each client thatconnects. See Section 10.6 MySQL Server Time Zone Support." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"-1", + "name":"table_definition_cache", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"400", + "dynamic":"t", + "rank":"-1", + "summary":"Options for table_definition_cache", + "vartype":"integer", + "max_value":"524288", + "scope":"{Global}", + "id":"1191", + "unit":"NULL", + "description":"The number of table definitions (from.frm files) that can be stored in thedefinition cache. If you use a large number of tables you cancreate a large table definition cache to speed up opening oftables. The table definition cache takes less space and doesnot use file descriptors unlike the normal table cache. Theminimum value is 400. The default value is based on thefollowing formula capped to a limit of 2000:For InnoDBtable_definition_cache actsas a soft limit for the number of open table instances in theInnoDB data dictionary cache. If the numberof open table instances exceeds thetable_definition_cachesetting the LRU mechanism begins to mark table instances foreviction and eventually removes them from the data dictionarycache. The limit helps address situations in which significantamounts of memory would be used to cache rarely used tableinstances until the next server restart. The number of tableinstances with cached metadata could be higher than the limitdefined bytable_definition_cachebecause InnoDB system table instances andparent and child table instances with foreign keyrelationships are not placed on the LRU list and are notsubject to eviction from memory.Additionallytable_definition_cachedefines a soft limit for the number ofInnoDB file-per-table tablespacesthat can be open at one time which is also controlled byinnodb_open_files. If bothtable_definition_cache andinnodb_open_files are setthe highest setting is used. If neither variable is settable_definition_cache whichhas a higher default value is used. If the number of opentablespace file handles exceeds the limit defined bytable_definition_cache orinnodb_open_files the LRUmechanism searches the tablespace file LRU list for files thatare fully flushed and are not currently being extended. Thisprocess is performed each time a new tablespace is opened. Ifthere are no inactive tablespaces notablespace files are closed." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"2000", + "name":"table_open_cache", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for table_open_cache", + "vartype":"integer", + "max_value":"524288", + "scope":"{Global}", + "id":"1192", + "unit":"NULL", + "description":"The number of open tables for all threads. Increasing thisvalue increases the number of file descriptors thatmysqld requires. You can check whether youneed to increase the table cache by checking theOpened_tables statusvariable. See Section 5.1.6 Server Status Variables. Ifthe value of Opened_tablesis large and you do not useFLUSH TABLESoften (which just forces all tables to be closed andreopened) then you should increase the value of thetable_open_cache variable.For more information about the table cache seeSection 8.4.3.1 How MySQL Opens and Closes Tables." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1", + "name":"table_open_cache_instances", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"f", + "rank":"-1", + "summary":"Options for table_open_cache_instances", + "vartype":"integer", + "max_value":"64", + "scope":"{Global}", + "id":"1193", + "unit":"NULL", + "description":"The number of open tables cache instances. To improvescalability by reducing contention among sessions the opentables cache can be partitioned into several smaller cacheinstances of sizetable_open_cache /table_open_cache_instances .A session needs to lock only one instance to access it for DMLstatements. This segments cache access among instancespermitting higher performance for operations that use thecache when there are many sessions accessing tables. (DDLstatements still require a lock on the entire cache but suchstatements are much less frequent than DML statements.)A value of 8 or 16 is recommended on systems that routinelyuse 16 or more cores." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"updatable_views_with_limit", + "deprecated":"f", + "valid_vals":"1,0", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for updatable_views_with_limit", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global,Session}", + "id":"1211", + "unit":"NULL", + "description":"This variable controls whether updates to a view can be madewhen the view does not contain all columns of the primary keydefined in the underlying table if the update statementcontains a LIMIT clause. (Such updatesoften are generated by GUI tools.) An update is anUPDATE orDELETE statement. Primary keyhere means a PRIMARY KEY or aUNIQUE index in which no column can containNULL.The variable can have two values:" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"-1", + "name":"thread_cache_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for thread_cache_size", + "vartype":"integer", + "max_value":"16384", + "scope":"{Global}", + "id":"1194", + "unit":"NULL", + "description":"How many threads the server should cache for reuse. When aclient disconnects the client's threads are put in the cacheif there are fewer thanthread_cache_size threadsthere. Requests for threads are satisfied by reusing threadstaken from the cache if possible and only when the cache isempty is a new thread created. This variable can be increasedto improve performance if you have a lot of new connections.Normally this does not provide a notable performanceimprovement if you have a good thread implementation. Howeverif your server sees hundreds of connections per second youshould normally setthread_cache_size high enoughso that most new connections use cached threads. By examiningthe difference between theConnections andThreads_created statusvariables you can see how efficient the thread cache is. Fordetails see Section 5.1.6 Server Status Variables.The default value is based on the following formula capped toa limit of 100:This variable has no effect for the embedded server(libmysqld) and as of MySQL 5.7.2 is nolonger visible within the embedded server." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"10", + "name":"thread_concurrency", + "deprecated":"t", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"f", + "rank":"-1", + "summary":"Options for thread_concurrency", + "vartype":"integer", + "max_value":"512", + "scope":"{Global}", + "id":"1195", + "unit":"NULL", + "description":"This variable is specific to Solaris 8 and earlier systemsfor which mysqld invokes thethr_setconcurrency() function with thevariable value. This function enables applications to give thethreads system a hint about the desired number of threads thatshould be run at the same time. Current Solaris versionsdocument this as having no effect.This variable was removed in MySQL 5.7.2." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"one-thread-per-connection", + "name":"thread_handling", + "deprecated":"f", + "valid_vals":"no-threads,one-thread-per-connection", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for thread_handling", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"1196", + "unit":"NULL", + "description":"The thread-handling model used by the server for connectionthreads. The permissible values areno-threads (the server uses a single threadto handle one connection) andone-thread-per-connection (the server usesone thread to handle each client connection).no-threads is useful for debugging underLinux; see Section 25.5 Debugging and Porting MySQL.This variable has no effect for the embedded server(libmysqld) and as of MySQL 5.7.2 is nolonger visible within the embedded server." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"262144", + "name":"thread_stack", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"131072", + "dynamic":"f", + "rank":"-1", + "summary":"Options for thread_stack", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"1197", + "unit":"1024", + "description":"The stack size for each thread. The default of 192KB (256KBfor 64-bit systems) is large enough for normal operation. Ifthe thread stack size is too small it limits the complexityof the SQL statements that the server can handle therecursion depth of stored procedures and othermemory-consuming actions." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"%H:%i:%s", + "name":"time_format", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"1198", + "unit":"NULL", + "description":"This variable is unused. It is deprecated and will be removedin a future MySQL release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"time_zone", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for time_zone", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1199", + "unit":"NULL", + "description":"The current time zone. This variable is used to initialize thetime zone for each client that connects. By default theinitial value of this is 'SYSTEM' (whichmeans use the value ofsystem_time_zone).The value can be specified explicitly at server startup withthe --default-time-zone option.See Section 10.6 MySQL Server Time Zone Support." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"timed_mutexes", + "deprecated":"t", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for timed_mutexes", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1200", + "unit":"NULL", + "description":"This deprecated variable has no use and was removed in MySQL5.7.5." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"DEFAULT", + "name":"timestamp", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for timestamp", + "vartype":"numeric", + "max_value":"NULL", + "scope":"{Session}", + "id":"1201", + "unit":"NULL", + "description":"Set the time for this client. This is used to get the originaltimestamp if you use the binary log to restore rows.timestamp_value should be a Unixepoch timestamp (a value like that returned byUNIX_TIMESTAMP() not a valuein 'YYYY-MM-DD hh:mm:ss' format) orDEFAULT.Setting timestamp to aconstant value causes it to retain that value until it ischanged again. Settingtimestamp toDEFAULT causes its value to be the currentdate and time as of the time it is accessed.In MySQL 5.7timestamp is aDOUBLE rather thanBIGINT because its value includes amicroseconds part.SET timestamp affects the value returned byNOW() but not bySYSDATE(). This means thattimestamp settings in the binary log have no effect oninvocations of SYSDATE(). Theserver can be started with the--sysdate-is-now option tocause SYSDATE() to be an aliasfor NOW() in which caseSET timestamp affects both functions." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"TLSv1TLSv1.1TLSv1.2", + "name":"tls_version", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for tls_version", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"1202", + "unit":"NULL", + "description":"The protocols permitted by the server for encryptedconnections. The value is a comma-separated list containingone or more protocol names. The protocols that can be namedfor this variable depend on the SSL library used to compileMySQL. For details seeSection 6.3.11.3 Secure Connection Protocols and Ciphers." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"validate_user_plugins", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for validate_user_plugins", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1212", + "unit":"NULL", + "description":"If this variable is enabled (the default) the server checkseach user account and produces a warning if conditions arefound that would make the account unusable:Enabling validate_user_plugins slows downserver initialization and FLUSH PRIVILEGES.If you do not require the additional checking you can disablethis variable at startup to avoid the performance decrement." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"off", + "name":"debug_print_rewritten", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Logs each query's rewritten parse tree.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1505", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"16777216", + "name":"tmp_table_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1024", + "dynamic":"t", + "rank":"-1", + "summary":"Options for tmp_table_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{GlobalSession}", + "id":"1203", + "unit":"NULL", + "description":"The maximum size of internal in-memory temporary tables. Thisvariable does not apply to user-createdMEMORY tables.The actual limit is determined as the minimum oftmp_table_size andmax_heap_table_size. If anin-memory temporary table exceeds the limit MySQLautomatically converts it to an on-disk temporary table. As ofMySQL 5.7.5 theinternal_tmp_disk_storage_engineoption defines the storage engine used for on-disk temporarytables. Prior to MySQL 5.7.5 the MyISAMstorage engine is used.Increase the value oftmp_table_size (andmax_heap_table_size ifnecessary) if you do many advanced GROUP BYqueries and you have lots of memory.You can compare the number of internal on-disk temporarytables created to the total number of internal temporarytables created by comparing the values of theCreated_tmp_disk_tables andCreated_tmp_tablesvariables.See also Section 8.4.4 Internal Temporary Table Use in MySQL." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"tmpdir", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for tmpdir", + "vartype":"directory name", + "max_value":"NULL", + "scope":"{Global}", + "id":"1204", + "unit":"NULL", + "description":"The directory used for temporary files and temporary tables.This variable can be set to a list of several paths that areused in round-robin fashion. Paths should be separated bycolon characters (:) on Unixand semicolon characters (;)on Windows.The multiple-directory feature can be used to spread the loadbetween several physical disks. If the MySQL server is actingas a replication slave you should not settmpdir to point to adirectory on a memory-based file system or to a directory thatis cleared when the server host restarts. A replication slaveneeds some of its temporary files to survive a machine restartso that it can replicate temporary tables orLOAD DATAINFILE operations. If files in the temporary filedirectory are lost when the server restarts replicationfails. You can set the slave's temporary directory using theslave_load_tmpdir variable.In that case the slave will not use the generaltmpdir value and you can settmpdir to a nonpermanentlocation." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"8192", + "name":"transaction_alloc_block_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1024", + "dynamic":"t", + "rank":"-1", + "summary":"Options for transaction_alloc_block_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{GlobalSession}", + "id":"1205", + "unit":"1024", + "description":"The amount in bytes by which to increase a per-transactionmemory pool which needs memory. See the description oftransaction_prealloc_size." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"4096", + "name":"transaction_prealloc_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1024", + "dynamic":"t", + "rank":"-1", + "summary":"Options for transaction_prealloc_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{GlobalSession}", + "id":"1206", + "unit":"1024", + "description":"There is a per-transaction memory pool from which varioustransaction-related allocations take memory. The initial sizeof the pool in bytes istransaction_prealloc_size.For every allocation that cannot be satisfied from the poolbecause it has insufficient memory available the pool isincreased bytransaction_alloc_block_sizebytes. When the transaction ends the pool is truncated totransaction_prealloc_sizebytes.By makingtransaction_prealloc_sizesufficiently large to contain all statements within a singletransaction you can avoid many malloc()calls." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"transaction_write_set_extraction", + "deprecated":"f", + "valid_vals":"OFF,MURMUR32", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for transaction_write_set_extraction", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1207", + "unit":"NULL", + "description":"Reserved for future use." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"REPEATABLE-READ", + "name":"tx_isolation", + "deprecated":"f", + "valid_vals":"READ-UNCOMMITTED,READ-COMMITTED,REPEATABLE-READ, SERIALIZABLE ", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for tx_isolation", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1208", + "unit":"NULL", + "description":"The default transaction isolation level. Defaults toREPEATABLE-READ.This variable can be set directly or indirectly using theSET TRANSACTION statement. SeeSection 13.3.6 SET TRANSACTION Syntax. If you settx_isolation directly to anisolation level name that contains a space the name should beenclosed within quotation marks with the space replaced by adash. For example:Any unique prefix of a valid value may be used to set thevalue of this variable.The default transaction isolation level can also be set atstartup using the--transaction-isolation serveroption." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"tx_read_only", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for tx_read_only", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1209", + "unit":"NULL", + "description":"The default transaction access mode. The value can beOFF (read/write the default) orON (read only).This variable can be set directly or indirectly using theSET TRANSACTION statement. SeeSection 13.3.6 SET TRANSACTION Syntax.To set the default transaction access mode at startup use the--transaction-read-only serveroption." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"YES", + "default_val":"1", + "name":"unique_checks", + "deprecated":"f", + "valid_vals":"1,0", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for unique_checks", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1210", + "unit":"NULL", + "description":"If set to 1 (the default) uniqueness checks for secondaryindexes in InnoDB tables are performed. Ifset to 0 storage engines are permitted to assume thatduplicate keys are not present in input data. If you know forcertain that your data does not contain uniqueness violationsyou can set this to 0 to speed up large table imports toInnoDB.Setting this variable to 0 does notrequire storage engines to ignoreduplicate keys. An engine is still permitted to check for themand issue duplicate-key errors if it detects them." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"version", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"1213", + "unit":"NULL", + "description":"The version number for the server. The value might alsoinclude a suffix indicating server build or configurationinformation. -log indicates that one ormore of the general log slow query log or binary log areenabled. -debug indicates that the server wasbuilt with debugging support enabled." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"INTERNAL", + "name":"version_comment", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for version_comment", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"1214", + "unit":"NULL", + "description":"The CMake configuration program has aCOMPILATION_COMMENT option thatpermits a comment to be specified when building MySQL. Thisvariable contains the value of that comment. SeeSection 2.9.4 MySQL Source-Configuration Options." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"INTERNAL", + "name":"version_compile_machine", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for version_compile_machine", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"1215", + "unit":"NULL", + "description":"The type of the server binary." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"INTERNAL", + "name":"version_compile_os", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for version_compile_os", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"1216", + "unit":"NULL", + "description":"The type of operating system on which MySQL was built." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"28800", + "name":"wait_timeout", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for wait_timeout", + "vartype":"integer", + "max_value":"31536000", + "scope":"{GlobalSession}", + "id":"1217", + "unit":"NULL", + "description":"The number of seconds the server waits for activity on anoninteractive connection before closing it.On thread startup the sessionwait_timeout value isinitialized from the globalwait_timeout value or fromthe globalinteractive_timeout valuedepending on the type of client (as defined by theCLIENT_INTERACTIVE connect option tomysql_real_connect()). Seealso interactive_timeout." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"INTERNAL", + "name":"warning_count", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"integer", + "max_value":"NULL", + "scope":"{NA}", + "id":"1218", + "unit":"NULL", + "description":"The number of errors warnings and notes that resulted fromthe last statement that generated messages. This variable isread only. See Section 13.7.5.40 SHOW WARNINGS Syntax." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"/usr/local/mysql/share/mysql/english/", + "name":"language", + "deprecated":"t", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for language", + "vartype":"directory name", + "max_value":"NULL", + "scope":"{Global}", + "id":"1219", + "unit":"NULL", + "description":"The language to use for error messages.lang_name can be given as thelanguage name or as the full path name to the directory wherethe language files are installed. SeeSection 10.2 Setting the Error Message Language.--lc-messages-dir and--lc-messages should be usedrather than --language whichis deprecated (and handled as an alias for--lc-messages-dir). The--language option will beremoved in a future MySQL release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"min-examined-row-limit", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for min-examined-row-limit", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{GlobalSession}", + "id":"1220", + "unit":"NULL", + "description":"When this option is set queries which examine fewer thannumber rows are not written to theslow query log. The default is 0." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"false", + "name":"enforce-gtid-consistency", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for enforce-gtid-consistency", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1221", + "unit":"NULL", + "description":"When enabled the server enforces GTID consistency byallowing execution of only statements that can be safelylogged using a GTID. You must set thisoption to ON before enabling GTID basedreplication.The values that--enforce-gtid-consistencycan be configured to are:Setting--enforce-gtid-consistencywithout a value is an alias for--enforce-gtid-consistency=ON.This impacts on the behavior of the variable seeenforce_gtid_consistency.Only statements that can be logged using GTID safestatements can be logged whenenforce-gtid-consistency isset to ON so the operations listed herecannot be used with this option:For more information seeSection 17.1.3.4 Restrictions on Replication with GTIDs." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"TRUE", + "name":"binlog_gtid_simple_recovery", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for binlog_gtid_simple_recovery", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1222", + "unit":"NULL", + "description":"This variable controls how binary log files are iteratedduring the search for GTIDs when MySQL starts or restarts.In MySQL version 5.7.5 this variable was added assimplified_binlog_gtid_recovery and inMySQL version 5.7.6 it was renamed tobinlog_gtid_simple_recovery.Whenbinlog_gtid_simple_recovery=FALSEthe method of iterating the binary log files is:Whenbinlog_gtid_simple_recovery=TRUEwhich is the default in MySQL 5.7.7 and later the serveriterates only the oldest and the newest binary log files andthe values of gtid_purgedand gtid_executed arecomputed based only onPrevious_gtids_log_event orGtid_log_event found in these files. Thisensures only two binary log files are iterated during serverrestart or when binary logs are being purged." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"false", + "name":"enforce_gtid_consistency", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for enforce_gtid_consistency", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1223", + "unit":"NULL", + "description":"Depending on the value of this variable the server enforcesGTID consistency by allowing execution of only statementsthat can be safely logged using a GTID. Youmust set this variable toON before enabling GTID basedreplication.The values thatenforce_gtid_consistencycan be configured to are:For more information on statements that can be logged usingGTID based replication see--enforce-gtid-consistency.Prior to MySQL 5.7.6 the booleanenforce-gtid-consistencydefaulted to OFF. To maintaincompatibility with previous versions in MySQL 5.7.6 theenumeration defaults to OFF and setting--enforce-gtid-consistencywithout a value is interpreted as setting the value toON. The variable also has multipletextual aliases for the values:0=OFF=FALSE1=ON=TRUE2=WARN. Thisdiffers from other enumeration types but maintainscompatibility with the boolean type used in previousversions. These changes impact on what is returned by thevariable. Using SELECT@@ENFORCE_GTID_CONSISTENCY SHOWVARIABLES LIKE 'ENFORCE_GTID_CONSISTENCY' andSELECT * FROM INFORMATION_SCHEMA.VARIABLES WHERE'VARIABLE_NAME' = 'ENFORCE_GTID_CONSISTENCY' allreturn the textual form not the numeric form. This is anincompatible change since@@ENFORCE_GTID_CONSISTENCY returns thenumeric form for booleans but returns the textual form forSHOW and the Information Schema." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1000", + "name":"executed_gtids_compression_period", + "deprecated":"t", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for executed_gtids_compression_period", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{Global}", + "id":"1224", + "unit":"NULL", + "description":"This option is deprecated and will be removed in a futureMySQL release. Use the renamedgtid_executed_compression_periodto control how the gtid_executed table iscompressed." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"8", + "name":"innodb_stats_sample_pages", + "deprecated":"t", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_stats_sample_pages", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"1400", + "unit":"NULL", + "description":"Deprecated useinnodb_stats_transient_sample_pagesinstead." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"gtid_executed", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for gtid_executed", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"1225", + "unit":"NULL", + "description":"When used with global scope this variable contains arepresentation of the set of all transactions executed onthe server and GTIDs that have been set by aSETgtid_purged statement. Thisis the same as the value of theExecuted_Gtid_Set column in the output ofSHOW MASTER STATUS andSHOW SLAVE STATUS. The valueof this variable is a GTID set seeGTID Sets formore information.When the server starts@@global.gtid_executed is initialized.Seebinlog_gtid_simple_recoveryfor more information on how binary logs are iterated topopulate gtid_executed.GTIDs are then added to the set as transactions areexecuted or if anySETgtid_purged statement isexecuted.The set of transactions that can be found in the binary logsat any given time is equal toGTID_SUBTRACT(@@global.gtid_executed@@global.gtid_purged); that is to alltransactions in the binary log that have not yet beenpurged.Issuing RESET MASTER causesthe global value (but not the session value) of thisvariable to be reset to an empty string. GTIDs are nototherwise removed from this set other than when the set iscleared due to RESET MASTER.Prior to MySQL 5.7.7 this variable could also be used withsession scope where it contained a representation of theset of transactions that are written to the cache in thecurrent session. The session scope was deprecated in MySQL5.7.7." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1000", + "name":"gtid_executed_compression_period", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for gtid_executed_compression_period", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{Global}", + "id":"1226", + "unit":"NULL", + "description":"Compress the mysql.gtid_executed tableeach time this many transactions have been processed. Asetting of 0 means that this table is not compressed. Sinceno compression of the table occurs when using the binarylog setting the value of the variable has no effect unlessbinary logging is disabled.Seemysql.gtid_executed Table Compressionfor more information.In MySQL version 5.7.5 this variable was added asexecuted_gtids_compression_period and inMySQL version 5.7.6 it was renamed togtid_executed_compression_period." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"gtid_mode", + "deprecated":"f", + "valid_vals":"OFF,UPGRADE_STEP_1,UPGRADE_STEP_2,ON", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for gtid_mode", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"1227", + "unit":"NULL", + "description":"Controls whether GTID based logging is enabled and what typeof transactions the logs can contain. Prior to MySQL 5.7.6this variable was read-only and was set using the--gtid-mode option only.MySQL 5.7.6 enables this variable to be set dynamically. Youmust have the SUPER privilegeto set this variable.enforce_gtid_consistencymust be true before you can setgtid_mode=ON. Beforemodifying this variable seeSection 17.1.5 Changing Replication Modes on Online Servers.Transactions logged in MySQL 5.7.6 and later can be eitheranonymous or use GTIDs. Anonymous transactions rely onbinary log file and position to identify specifictransactions. GTID transactions have a unique identifierthat is used to refer to transactions. TheOFF_PERMISSIVE andON_PERMISSIVE modes added in MySQL 5.7.6permit a mix of these transaction types in the topology. Thedifferent modes are now:Changes from one value to another can only be one step at atime. For example ifgtid_mode is currently setto OFF_PERMISSIVE it is possible tochange to OFF orON_PERMISSIVE but not toON.In MySQL 5.7.6 and later the values ofgtid_purged andgtid_executed arepersistent regardless of the value ofgtid_mode. Therefore evenafter changing the value ofgtid_mode these variablescontain the correct values. In MySQL 5.7.5 and earlier thevalues of gtid_purged andgtid_executed are notpersistent whilegtid_mode=OFF. Thereforeafter changing gtid_mode toOFF once all binary logs containingGTIDs are purged the values of these variables are lost." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"AUTOMATIC", + "name":"gtid_next", + "deprecated":"f", + "valid_vals":"AUTOMATIC,ANONYMOUS,UUID:NUMBER", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for gtid_next", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Session}", + "id":"1228", + "unit":"NULL", + "description":"This variable is used to specify whether and how the nextGTID is obtained. gtid_next can take anyof the following values:Exactly which of the above options are valid depends on thesetting of gtid_mode seeSection 17.1.5.1 Replication Mode Conceptsfor more information. Setting this variable has no effect ifgtid_mode isOFF.After this variable has been set toUUID:NUMBERand a transaction has been committed or rolled back anexplicit SET GTID_NEXT statement mustagain be issued before any other statement.In MySQL 5.7.5 and later DROP TABLE orDROP TEMPORARY TABLE fails with anexplicit error when used on a combination of nontemporarytables with temporary tables or of temporary tables usingtransactional storage engines with temporary tables usingnontransactional storage engines. Prior to MySQL 5.7.5 whenGTIDs were enabled but gtid_next was notAUTOMATIC DROPTABLE did not work correctly when used with eitherof these combinations of tables. (Bug #17620053)In MySQL 5.7.1 you cannot execute any of the statementsCHANGE MASTER TOSTART SLAVESTOP SLAVEREPAIR TABLEOPTIMIZE TABLEANALYZE TABLECHECK TABLECREATE SERVERALTER SERVERDROP SERVERCACHE INDEXLOAD INDEX INTOCACHE FLUSH orRESET whengtid_next is set to anyvalue other than AUTOMATIC; in suchcases the statement fails with an error. Such statementsare not disallowed in MySQL 5.7.2 andlater. (Bug #16062608 Bug #16715809 Bug #69045) (Bug#16062608)" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"gtid_owned", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for gtid_owned", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1229", + "unit":"NULL", + "description":"This read-only variable holds a list whose contents dependon its scope. When used with session scope the list holdsall GTIDs that are owned by this client; when used withglobal scope it holds a list of all GTIDs along with theirowners." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"gtid_purged", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for gtid_purged", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"1230", + "unit":"NULL", + "description":"The set of all transactions that have been purged from thebinary log. This is a subset of the set of transactions ingtid_executed. The value ofthis variable is a GTID set seeGTID Sets formore information.When the server starts the global value ofgtid_purged is initializedto a set of GTIDs. Seebinlog_gtid_simple_recoveryfor more information on how binary logs are iterated topopulate gtid_purged.Issuing RESET MASTER causesthe value of this variable to be reset to an empty string.It is possible to update the value of this variable butonly when gtid_executed isthe empty string and thereforegtid_purged is the emptystring. This can occur either when replication has not beenstarted previously or when replication was not previouslyusing GTIDs. Prior to MySQL 5.7.6 this variable wassettable only whengtid_mode=ON. In MySQL5.7.6 and later this variable is settable regardless of thevalue of gtid_mode.If all existing binary logs were generated using MySQL 5.7.6or later after issuing a SET gtid_purgedstatementbinlog_gtid_simple_recovery=TRUE(the default setting in MySQL 5.7.7 and later) can safely beused. If binary logs from MySQL 5.7.7 or earlier existthere is a chance thatgtid_purged may be computedincorrectly. Seebinlog_gtid_simple_recoveryfor more information. If you are using MySQL 5.7.7 orearlier after issuing a SET gtid_purgedstatement note down the current binary log file name whichcan be checked using SHOW MASTERSTATUS. If the server is restarted before thisfile has been purged then you should usebinlog_gtid_simple_recovery=FALSEto avoid gtid_purged orgtid_executed beingcomputed incorrectly." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"FALSE", + "name":"simplified_binlog_gtid_recovery", + "deprecated":"t", + "valid_vals":"TRUE,FALSE", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for simplified_binlog_gtid_recovery", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1231", + "unit":"NULL", + "description":"This option is deprecated and will be removed in a futureMySQL release. Use the renamedbinlog_gtid_simple_recoveryto control how MySQL iterates through binary log files aftera crash." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"relay_log", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for relay-log", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"1242", + "unit":"NULL", + "description":"The base name of the relay log file with no paths and nofile extension. By default relay-log.The file name of individual files for the defaultreplication channel isrelay-log.XXXXXX and for additionalreplication channels isrelay-log-channel.XXXXXX." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"datadir + '/' + hostname + '-relay-bin'", + "name":"relay_log_basename", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for relay_log_basename", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"1243", + "unit":"NULL", + "description":"Holds the name and complete path to the relay log file." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"validate_password_dictionary_file", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for validate_password_dictionary_file", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"1232", + "unit":"NULL", + "description":"The path name of the dictionary file used by thevalidate_password plugin for checkingpasswords. This variable is unavailable unless that pluginis installed.By default this variable has an empty value and dictionarychecks are not performed. To enable dictionary checks youmust set this variable to a nonempty value. If the file isnamed as a relative path it is interpreted relative to theserver data directory. Its contents should be lowercase oneword per line. Contents are treated as having a characterset of utf8. The maximum permitted filesize is 1MB.For the dictionary file to be used during password checkingthe password policy must be set to 2(STRONG); see the description of thevalidate_password_policysystem variable. Assuming that is true each substring ofthe password of length 4 up to 100 is compared to the wordsin the dictionary file. Any match causes the password to berejected. Comparisons are not case sensitive.ForVALIDATE_PASSWORD_STRENGTH()the password is checked against all policies includingSTRONG so the strength assessmentincludes the dictionary check regardless of thevalidate_password_policyvalue.Changes to the dictionary file while the server is runningrequire a restart for the server to recognize the changes.Before MySQL 5.7.8 changes to the dictionary file while theserver is running require a restart for the server torecognize the changes. As of MySQL 5.7.8validate_password_dictionary_filecan be set at runtime and assigning a value causes the namedfile to be read without a restart." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"8", + "name":"validate_password_length", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for validate_password_length", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"1233", + "unit":"NULL", + "description":"The minimum number of characters that passwords checked bythe validate_password plugin must have.This variable is unavailable unless that plugin isinstalled.Thevalidate_password_lengthminimum value is a function of several other related systemvariables. The server will not set the value less than thevalue of this expression:If the validate_password plugin adjuststhe value ofvalidate_password_lengthdue to the preceding constraint it writes a message to theerror log." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"validate_password_mixed_case_count", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for validate_password_mixed_case_count", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"1234", + "unit":"NULL", + "description":"The minimum number of lowercase and uppercase charactersthat passwords checked by thevalidate_password plugin must have if thepassword policy is MEDIUM or stronger.This variable is unavailable unless that plugin isinstalled." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"validate_password_number_count", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for validate_password_number_count", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"1235", + "unit":"NULL", + "description":"The minimum number of numeric (digit) characters thatpasswords checked by thevalidate_password plugin must have if thepassword policy is MEDIUM or stronger.This variable is unavailable unless that plugin isinstalled." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"validate_password_policy", + "deprecated":"f", + "valid_vals":"0,1,2", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for validate_password_policy", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"1236", + "unit":"NULL", + "description":"The password policy enforced by thevalidate_password plugin. This variableis unavailable unless that plugin is installed.Thevalidate_password_policyvalue can be specified using numeric values 012 or thecorresponding symbolic values LOWMEDIUM STRONG. Thefollowing table describes the tests performed for eachpolicy. For the length test the required length is thevalue of thevalidate_password_lengthsystem variable. Similarly the required values for theother tests are given by othervalidate_password_xxxvariables." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"validate_password_special_char_count", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for validate_password_special_char_count", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"1237", + "unit":"NULL", + "description":"The minimum number of nonalphanumeric characters thatpasswords checked by thevalidate_password plugin must have if thepassword policy is MEDIUM or stronger.This variable is unavailable unless that plugin isinstalled." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"slave_compressed_protocol", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for slave_compressed_protocol", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1238", + "unit":"NULL", + "description":"If this option is set to 1 use compression for theslave/master protocol if both the slave and the mastersupport it. The default is 0 (no compression)." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"init_slave", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for init_slave", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"1239", + "unit":"NULL", + "description":"This variable is similar toinit_connect but is astring to be executed by a slave server each time the SQLthread starts. The format of the string is the same as forthe init_connect variable.The setting of this variable takes effect for subsequentSTART SLAVE statements." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"log_slow_slave_statements", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for log_slow_slave_statements", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1240", + "unit":"NULL", + "description":"When the slow query log is enabled this variable enableslogging for queries that have taken more thanlong_query_time seconds toexecute on the slave. This variable was added in MySQL5.7.1. Setting this variable has no immediate effect. Thestate of the variable applies on all subsequentSTART SLAVE statements." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"FILE", + "name":"master_info_repository", + "deprecated":"f", + "valid_vals":"FILE,TABLE", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for master_info_repository", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"1241", + "unit":"NULL", + "description":"The setting of this variable determines whether the slavelogs master status and connection information to aFILE (master.info)or to a TABLE(mysql.slave_master_info). You can onlychange the value of this variable when no replicationthreads are executing.The setting of this variable also has a direct influence onthe effect had by the setting of thesync_master_info systemvariable; see that variable's description for furtherinformation.This variable must be set to TABLE beforeconfiguring multiple replication channels. If you are usingmultiple replication channels then you cannot set thisvariable back to FILE." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"30", + "name":"checkpoint_warning", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Enables warnings if checkpoint segments are filled more frequently than this.", + "vartype":"integer", + "max_value":"2147483647", + "scope":"{Global}", + "id":"1485", + "unit":"s", + "description":"Write a message to the server log if checkpoints caused by the filling of checkpoint segment files happens more frequently than this number of seconds. Zero turns off the warning." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"*host_name*-relay-bin.index", + "name":"relay_log_index", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for relay_log_index", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"1244", + "unit":"NULL", + "description":"The name of the relay log index file for the defaultreplication channel. The default name ishost_name-relay-bin.indexin the data directory wherehost_name is the name of theslave server." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"relay-log.info", + "name":"relay_log_info_file", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for relay_log_info_file", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"1245", + "unit":"NULL", + "description":"The name of the file in which the slave records informationabout the relay logs whenrelay_log_info_repository=FILE.Ifrelay_log_info_repository=TABLEit is the file name that would be used in case therepository was changed to FILE). Thedefault name is relay-log.info in thedata directory." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"FILE", + "name":"relay_log_info_repository", + "deprecated":"f", + "valid_vals":"FILE,TABLE", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for relay_log_info_repository", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"1246", + "unit":"NULL", + "description":"This variable determines whether the slave's positionin the relay logs is written to a FILE(relay-log.info) or to aTABLE(mysql.slave_relay_log_info). You canonly change the value of this variable when no replicationthreads are executing.The setting of this variable also has a direct influence onthe effect had by the setting of thesync_relay_log_info systemvariable; see that variable's description for furtherinformation.This variable must be set to TABLE beforeconfiguring multiple replication channels. If you are usingmultiple replication channels then you cannot set thisvariable back to FILE." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"FALSE", + "name":"relay_log_recovery", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for relay_log_recovery", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1247", + "unit":"NULL", + "description":"Enables automatic relay log recovery immediately followingserver startup. The recovery process creates a new relay logfile initializes the SQL thread position to this new relaylog and initializes the I/O thread to the SQL threadposition. Reading of the relay log from the master thencontinues. In MySQL 5.7 this global variable is read-only;its value can be changed by starting the slave with the--relay-log-recovery optionwhich should be used following a crash on the replicationslave to ensure that no possibly corrupted relay logs areprocessed and must be used in order to guarantee acrash-safe slave. The default value is 0 (disabled).This variable also interacts withrelay-log-purge whichcontrols purging of logs when they are no longer needed.Enabling the--relay-log-recovery optionwhen relay-log-purge isdisabled risks reading the relay log from files that werenot purged leading to data inconsistency and is thereforenot crash-safe.When relay_log_recovery is enabled andthe slave has stopped due to errors encountered whilerunning in multi-threaded mode you can useSTART SLAVEUNTIL SQL_AFTER_MTS_GAPS to ensure that all gapsare processed before switching back to single-threaded modeor executing a CHANGE MASTER TOstatement." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"31536000", + "name":"rpl_stop_slave_timeout", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"2", + "dynamic":"t", + "rank":"-1", + "summary":"Options for rpl_stop_slave_timeout", + "vartype":"integer", + "max_value":"31536000", + "scope":"{Global}", + "id":"1248", + "unit":"NULL", + "description":"In MySQL 5.7.2 and later you can control the length of time(in seconds) that STOP SLAVEwaits before timing out by setting this variable. This canbe used to avoid deadlocks between STOPSLAVE and other slave SQL statements usingdifferent client connections to the slave. The maximum anddefault value of rpl_stop_slave_timeoutis 31536000 seconds (1 year). The minimum is 2 seconds.Changes to this variable take effect for subsequentSTOP SLAVE statements. Thisvariable affects only the client that issues aSTOP SLAVE statement. Whenthe timeout is reached the issuing client stops waiting forthe slave threads to stop but the slave threads continue totry to stop." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"512", + "name":"slave_checkpoint_group", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"32", + "dynamic":"t", + "rank":"-1", + "summary":"Options for slave_checkpoint_group", + "vartype":"integer", + "max_value":"524280", + "scope":"{Global}", + "id":"1249", + "unit":"8", + "description":"Sets the maximum number of transactions that can beprocessed by a multi-threaded slave before a checkpointoperation is called to update its status as shown bySHOW SLAVE STATUS. Settingthis variable has no effect on slaves for whichmulti-threading is not enabled. Setting this variable has noimmediate effect. The state of the variable applies on allsubsequent START SLAVEcommands.This variable works in combination with theslave_checkpoint_periodsystem variable in such a way that when either limit isexceeded the checkpoint is executed and the counterstracking both the number of transactions and the timeelapsed since the last checkpoint are reset.The minimum allowed value for this variable is 32 unlessthe server was built using-DWITH_DEBUG in which casethe minimum value is 1. The effective value is always amultiple of 8; you can set it to a value that is not such amultiple but the server rounds it down to the next lowermultiple of 8 before storing the value.(Exception: No such rounding isperformed by the debug server.) Regardless of how the serverwas built the default value is 512 and the maximum allowedvalue is 524280." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"16777216", + "name":"slave_pending_jobs_size_max", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1024", + "dynamic":"t", + "rank":"-1", + "summary":"Options for slave_pending_jobs_size_max", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"1257", + "unit":"1024", + "description":"For multi-threaded slaves this variable sets the maximumamount of memory (in bytes) available to slave worker queuesholding events not yet applied. Setting this variable has noeffect on slaves for which multi-threading is not enabled.Setting this variable has no immediate effect. The state ofthe variable applies on all subsequentSTART SLAVE commands.The minimum possible value for this variable is 1024; thedefault is 16MB. The maximum possible value is18446744073709551615 (16 exabytes). Values that are notexact multiples of 1024 are rounded down to the next-highestmultiple of 1024 prior to being stored." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"300", + "name":"slave_checkpoint_period", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for slave_checkpoint_period", + "vartype":"integer", + "max_value":"4294967296", + "scope":"{Global}", + "id":"1250", + "unit":"NULL", + "description":"Sets the maximum time (in milliseconds) that is allowed topass before a checkpoint operation is called to update thestatus of a multi-threaded slave as shown bySHOW SLAVE STATUS. Settingthis variable has no effect on slaves for whichmulti-threading is not enabled. Setting this variable takeseffect for all replication channels immediately includingrunning channels.This variable works in combination with theslave_checkpoint_groupsystem variable in such a way that when either limit isexceeded the checkpoint is executed and the counterstracking both the number of transactions and the timeelapsed since the last checkpoint are reset.The minimum allowed value for this variable is 1 unless theserver was built using-DWITH_DEBUG in which casethe minimum value is 0. Regardless of how the server wasbuilt the default value is 300 and the maximum possiblevalue is 4294967296 (4GB)." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":" (NDB)", + "name":"slave_exec_mode", + "deprecated":"f", + "valid_vals":"IDEMPOTENT,STRICT", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for slave_exec_mode", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"1251", + "unit":"NULL", + "description":"Controls how a slave thread resolves conflicts and errorsduring replication. IDEMPOTENT modecauses suppression of duplicate-key and no-key-found errors.This mode should be employed in multi-master replicationcircular replication and some other special replicationscenarios. STRICT mode is the defaultand is suitable for most other cases. Setting this variabletakes effect for all replication channels immediatelyincluding running channels.This mode is needed for multi-master replication circularreplication and some other special replication scenariosfor MySQL Cluster Replication. (SeeSection 18.6.10 MySQL Cluster Replication: Multi-Master and Circular ReplicationandSection 18.6.11 MySQL Cluster Replication Conflict Resolutionfor more information.) The mysqldsupplied with MySQL Cluster ignores any value explicitly setfor slave_exec_mode andalways treats it as IDEMPOTENT.In MySQL Server 5.7 STRICTmode is the default value. This should not be changed;currently IDEMPOTENT mode is supportedonly by NDB and is used whenreplicating NDB toInnoDB." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"/tmp", + "name":"slave_load_tmpdir", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for slave-load-tmpdir", + "vartype":"directory name", + "max_value":"NULL", + "scope":"{Global}", + "id":"1252", + "unit":"NULL", + "description":"The name of the directory where the slave creates temporaryfiles for replicatingLOAD DATAINFILE statements. Setting this variable takeseffect for all replication channels immediately includingrunning channels." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1073741824", + "name":"slave_max_allowed_packet", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1024", + "dynamic":"t", + "rank":"-1", + "summary":"Options for slave_max_allowed_packet", + "vartype":"integer", + "max_value":"1073741824", + "scope":"{Global}", + "id":"1253", + "unit":"NULL", + "description":"This variable sets the maximum packet size for the slave SQLand I/O threads so that large updates using row-basedreplication do not cause replication to fail because anupdate exceededmax_allowed_packet. Settingthis variable takes effect for all replication channelsimmediately including running channels.This global variable always has a value that is a positiveinteger multiple of 1024; if you set it to some value thatis not the value is rounded down to the next highestmultiple of 1024 for it is stored or used; settingslave_max_allowed_packet to 0 causes 1024to be used. (A truncation warning is issued in all suchcases.) The default and maximum value is 1073741824 (1 GB);the minimum is 1024.slave_max_allowed_packet can also be setat startup using the--slave-max-allowed-packetoption." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"60", + "name":"slave_net_timeout", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for slave-net-timeout", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"1254", + "unit":"NULL", + "description":"The number of seconds to wait for more data from amaster/slave connection before aborting the read. Settingthis variable has no immediate effect. The state of thevariable applies on all subsequentSTART SLAVE commands." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"DATABASE", + "name":"slave_parallel_type", + "deprecated":"f", + "valid_vals":"DATABASE,LOGICAL_CLOCK", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for slave-parallel-type", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{NA}", + "id":"1255", + "unit":"NULL", + "description":"When using a multi-threaded slave(slave_parallel_workers isgreater than 0) this variable specifies the policy used todecide which transactions are allowed to execute in parallelon the slave. See--slave-parallel-type formore information." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"slave_parallel_workers", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for slave_parallel_workers", + "vartype":"integer", + "max_value":"1024", + "scope":"{Global}", + "id":"1256", + "unit":"NULL", + "description":"Sets the number of slave applier threads for executingreplication transactions in parallel. Setting this variableto a number greater than 0 creates a multi-threaded slavewith this number of applier threads. When set to 0 (thedefault) parallel execution is disabled and the slave uses asingle applier thread. Settingslave_parallel_workers hasno immediate effect. The state of the variable applies onall subsequent START SLAVEstatements.A multi-threaded slave provides parallel execution by usinga coordinator thread and the number of applier threadsconfigured by this variable. The way which transactions aredistributed among applier threads is configured byslave_parallel_type. Thetransactions that the slave applies in parallel may commitout of order unlessslave_preserve_commit_order=1.Therefore checking for the most recently executedtransaction does not guarantee that all previoustransactions from the master have been executed on theslave. This has implications for logging and recovery whenusing a multi-threaded slave. For example on amulti-threaded slave theSTART SLAVEUNTIL statement only supports usingSQL_AFTER_MTS_GAPS.In MySQL 5.7.5 and later retrying of transactions issupported when multi-threading is enabled on a slave. Inprevious versionsslave_transaction_retrieswas treated as equal to 0 when using multi-threaded slaves." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"slave_preserve_commit_order", + "deprecated":"f", + "valid_vals":"0,1", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for slave_preserve_commit_order", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1258", + "unit":"NULL", + "description":"For multi-threaded slaves enabling this variable ensuresthat transactions are externalized on the slave in the sameorder as they appear in the slave's relay log. Settingthis variable has no effect on slaves for whichmulti-threading is not enabled. All replication threads (forall replication channels if you are using multiplereplication channels) must be stopped before changing thisvariable. --log-bin and--log-slave-updates must beenabled on the slave. In addition--slave-parallel-type must be set toLOGICAL_CLOCK.Once a multi-threaded slave has been started transactionscan begin to execute in parallel. Withslave_preserve_commit_orderenabled the executing thread waits until all previoustransactions are committed before committing. While theslave thread is waiting for other workers to commit theirtransactions it reports its status as Waiting forpreceding transaction to commit. (Prior to MySQL5.7.8 this was shown as Waiting for its turn tocommit.) Enabling this mode on a multi-threadedslave ensures that it never enters a state that the masterwas not in. This makes it well suited to using replicationfor read scale-out. SeeSection 17.3.3 Using Replication for Scale-Out.When using a multi-threaded slave ifslave_preserve_commit_orderis not enabled there is a chance of gaps in the sequence oftransactions that have been executed from the slave'srelay log. When this option is enabled there is not thischance of gaps but Exec_master_log_posmay be behind the position up to which has been executed.SeeSection 17.4.1.34 Replication and Transaction Inconsistenciesfor more information." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"TABLE_SCANINDEX_SCAN", + "name":"slave_rows_search_algorithms", + "deprecated":"f", + "valid_vals":"TABLE_SCAN,INDEX_SCAN,INDEX_SCAN,HASH_SCAN,TABLE_SCAN,HASH_SCAN,TABLE_SCAN,INDEX_SCAN,HASH_SCAN, (equivalent to INDEX_SCAN,HASH_SCAN)", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for slave_rows_search_algorithms", + "vartype":"set", + "max_value":"NULL", + "scope":"{Global}", + "id":"1259", + "unit":"NULL", + "description":"When preparing batches of rows for row-based logging andreplication this variable controls how the rows aresearched for matchesthat is whether or not hashingis used for searches using a primary or unique key usingsome other key or using no key at all. Setting thisvariable takes effect for all replication channelsimmediately including running channels.This variable takes a comma-separated list of at least 2values from the list INDEX_SCANTABLE_SCAN HASH_SCAN.The value expected as a string so the value must be quoted.In addition the value must not contain any spaces. Possiblecombinations (lists) and their effects are shown in thefollowing table:The order in which the algorithms are specified in the listdoes not make any difference in the order in which they aredisplayed by a SELECT orSHOW VARIABLES statement asshown here:The default value isTABLE_SCANINDEX_SCAN which means thatall searches that can use indexes do use them and searcheswithout any indexes use table scans.SpecifyingINDEX_SCANTABLE_SCANHASH_SCAN has thesame effect as specifyingINDEX_SCANHASH_SCAN. To use hashing forany searches that does not use a primary or unique key setthis variable to INDEX_SCANHASH_SCAN. Toforce hashing for all searches set itto TABLE_SCANHASH_SCAN." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"slave_skip_errors", + "deprecated":"f", + "valid_vals":"OFF,[list of error codes],all", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for slave-skip-errors", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"1260", + "unit":"NULL", + "description":"Normally replication stops when an error occurs on theslave which gives you the opportunity to resolve theinconsistency in the data manually. This variable causes theslave SQL thread to continue replication when a statementreturns any of the errors listed in the variable value. Thesetting of this variable takes effect immediately even forrunning replication threads." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"slave_sql_verify_checksum", + "deprecated":"f", + "valid_vals":"0,1", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for slave_sql_verify_checksum", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1261", + "unit":"NULL", + "description":"Cause the slave SQL thread to verify data using thechecksums read from the relay log. In the event of amismatch the slave stops with an error. Setting thisvariable takes effect for all replication channelsimmediately including running channels." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"10", + "name":"slave_transaction_retries", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for slave_transaction_retries", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"1262", + "unit":"NULL", + "description":"If a replication slave SQL thread fails to execute atransaction because of anInnoDB deadlock or because thetransaction's execution time exceededInnoDB'sinnodb_lock_wait_timeout orNDB'sTransactionDeadlockDetectionTimeoutorTransactionInactiveTimeoutit automatically retriesslave_transaction_retriestimes before stopping with an error. The default value is10. Setting this variable takes effect for all replicationchannels immediately including running channels.As of MySQL 5.7.5 retrying of transactions is supportedwhen multi-threading is enabled on a slave. In previousversionsslave_transaction_retrieswas treated as equal to 0 when using multi-threaded slaves." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"slave_type_conversions", + "deprecated":"f", + "valid_vals":"ALL_LOSSY,ALL_NON_LOSSY", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for slave_type_conversions", + "vartype":"set", + "max_value":"NULL", + "scope":"{Global}", + "id":"1263", + "unit":"NULL", + "description":"Controls the type conversion mode in effect on the slavewhen using row-based replication. In MySQL 5.7.2 and laterits value is a comma-delimited set of zero or more elementsfrom the list: ALL_LOSSYALL_NON_LOSSYALL_SIGNEDALL_UNSIGNED. Set this variable to anempty string to disallow type conversions between the masterand the slave. Setting this variable takes effect for allreplication channels immediately including runningchannels.ALL_SIGNED andALL_UNSIGNED were added in MySQL 5.7.2(Bug#15831300). For additional information on typeconversion modes applicable to attribute promotion anddemotion in row-based replication seeRow-based replication: attribute promotion and demotion." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"sql_slave_skip_counter", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sql_slave_skip_counter", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"1264", + "unit":"NULL", + "description":"The number of events from the master that a slave servershould skip. Setting the option has no immediate effect. Thevariable applies to the next STARTSLAVE statement; the nextSTART SLAVE statement alsochanges the value back to 0. When this variable is set to anon-zero value and there are multiple replication channelsconfigured the START SLAVEstatement can only be used with the FOR CHANNELchannel clause.This option is incompatible with GTID-based replication andmust not be set to a nonzero value when--gtid-mode=ON. In MySQL5.7.1 and later trying to do so is specifically disallowed.(Bug #15833516) If you need to skip transactions whenemploying GTIDs usegtid_executed from themaster instead. SeeInjecting empty transactions forinformation about how to do this." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"UTF8", + "name":"client_encoding", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the client's character set encoding.", + "vartype":"string", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1486", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"100", + "name":"default_statistics_target", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the default statistics target.", + "vartype":"integer", + "max_value":"10000", + "scope":"{GlobalSession}", + "id":"1506", + "unit":"", + "description":"This applies to table columns that have not had a column-specific target set via ALTER TABLE SET STATISTICS." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"10000", + "name":"sync_master_info", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sync_master_info", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"1265", + "unit":"NULL", + "description":"The effects of this variable on a replication slave dependon whether the slave'smaster_info_repository isset to FILE or TABLEas explained in the following paragraphs.master_info_repository = FILE. If the value of sync_master_info isgreater than 0 the slave synchronizes itsmaster.info file to disk (usingfdatasync()) after everysync_master_info events. If it is 0the MySQL server performs no synchronization of themaster.info file to disk; insteadthe server relies on the operating system to flush itscontents periodically as with any other file.master_info_repository = TABLE. If the value of sync_master_info isgreater than 0 the slave updates its master inforepository table after everysync_master_info events. If it is 0the table is never updated.The default value for sync_master_info is10000. Setting this variable takes effect for allreplication channels immediately including runningchannels." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"10000", + "name":"sync_relay_log", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sync_relay_log", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"1266", + "unit":"NULL", + "description":"If the value of this variable is greater than 0 the MySQLserver synchronizes its relay log to disk (usingfdatasync()) after everysync_relay_log events are written to therelay log. Setting this variable takes effect for allreplication channels immediately including runningchannels.Setting sync_relay_log to 0 causes nosynchronization to be done to disk; in this case the serverrelies on the operating system to flush the relay log'scontents from time to time as for any other file.A value of 1 is the safest choice because in the event of acrash you lose at most one event from the relay log.However it is also the slowest choice (unless the disk hasa battery-backed cache which makes synchronization veryfast)." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"10000", + "name":"sync_relay_log_info", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sync_relay_log_info", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"1267", + "unit":"NULL", + "description":"The effects of this variable on the slave depend on theserver'srelay_log_info_repositorysetting (FILE orTABLE) and if this isTABLE additionally on whether thestorage engine used by the relay log info table istransactional (such as InnoDB)or not (MyISAM). The effects ofthese factors on the behavior of the server forsync_relay_log_info values of zero andgreater than zero are shown in the following table:The default value for sync_relay_log_infois 10000. Setting this variable takes effect for allreplication channels immediately including runningchannels." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"mysql_firewall_mode", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for mysql_firewall_mode", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1268", + "unit":"NULL", + "description":"Whether MySQL Enterprise Firewall is enabled (the default) or disabled." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"mysql_firewall_trace", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for mysql_firewall_trace", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1269", + "unit":"NULL", + "description":"Whether the MySQL Enterprise Firewall trace is enabled or disabled (thedefault). Whenmysql_firewall_trace isenabled for PROTECTING mode thefirewall writes rejected statements to the error log." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"false", + "name":"daemon_memcached_enable_binlog", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for daemon_memcached_enable_binlog", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1270", + "unit":"NULL", + "description":"See Section 14.18 InnoDB memcached Plugin for usage details forthis option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"innodb_engine.so", + "name":"daemon_memcached_engine_lib_name", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for daemon_memcached_engine_lib_name", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"1271", + "unit":"NULL", + "description":"Specifies the shared library that implements theInnoDB memcached plugin.See Section 14.18 InnoDB memcached Plugin for usage details forthis option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"NULL", + "name":"daemon_memcached_engine_lib_path", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for daemon_memcached_engine_lib_path", + "vartype":"directory name", + "max_value":"NULL", + "scope":"{Global}", + "id":"1272", + "unit":"NULL", + "description":"The path of the directory containing the shared library thatimplements the InnoDBmemcached plugin. The default value isNULL representing the MySQL plugin directory. You should notneed to modify this parameter unless specifying a differentstorage engine memcached plugin that islocated outside of the MySQL plugin directory.See Section 14.18 InnoDB memcached Plugin for usage details forthis option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"daemon_memcached_option", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for daemon_memcached_option", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"1273", + "unit":"NULL", + "description":"Used to pass space-separated memcached options to theunderlying memcached memory object cachingdaemon on startup. For example you might change the port thatmemcached listens on reduce the maximumnumber of simultaneous connections change the maximum memorysize for a key/value pair or enable debugging messages forthe error log.See Section 14.18 InnoDB memcached Plugin for usage details forthis option. For information about memcached options refer tothe memcached man page." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"8388608", + "name":"innodb_additional_mem_pool_size", + "deprecated":"t", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"2097152", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_additional_mem_pool_size", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{Global}", + "id":"1282", + "unit":"NULL", + "description":"The size in bytes of a memory pool InnoDBuses to store datadictionary information and other internal datastructures. The more tables you have in your application themore memory you allocate here. If InnoDBruns out of memory in this pool it starts to allocate memoryfrom the operating system and writes warning messages to theMySQL error log. The default value is 8MB.This variable relates to the InnoDBinternal memory allocator which is unused ifinnodb_use_sys_malloc isenabled.innodb_additional_mem_pool_size wasdeprecated in MySQL 5.6.3 and removed in MySQL 5.7.4." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"daemon_memcached_r_batch_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for daemon_memcached_r_batch_size", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"1274", + "unit":"NULL", + "description":"Specifies how many memcached readoperations (get) to perform before doing aCOMMIT to start a newtransaction. Counterpart ofdaemon_memcached_w_batch_size.This value is set to 1 by default so that any changes made tothe table through SQL statements are immediately visible tothe memcached operations. You mightincrease it to reduce the overhead from frequent commits on asystem where the underlying table is only being accessedthrough the memcached interface. If you setthe value too large the amount of undo or redo data couldimpose some storage overhead as with any long-runningtransaction.See Section 14.18 InnoDB memcached Plugin for usage details forthis option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"daemon_memcached_w_batch_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for daemon_memcached_w_batch_size", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"1275", + "unit":"NULL", + "description":"Specifies how many memcached writeoperations such as addset or incr to performbefore doing a COMMIT to starta new transaction. Counterpart ofdaemon_memcached_r_batch_size.This value is set to 1 by default on the assumption that anydata being stored is important to preserve in case of anoutage and should immediately be committed. When storingnon-critical data you might increase this value to reduce theoverhead from frequent commits; but then the lastN-1 uncommitted write operationscould be lost in case of a crash.See Section 14.18 InnoDB memcached Plugin for usage details forthis option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"ignore_builtin_innodb", + "deprecated":"t", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for ignore-builtin-innodb", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1276", + "unit":"NULL", + "description":"See the description of--ignore-builtin-innodb underInnoDB Command Optionsearlier in this section." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"ON", + "name":"innodb_adaptive_flushing", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_adaptive_flushing", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1277", + "unit":"NULL", + "description":"Specifies whether to dynamically adjust the rate of flushingdirty pages in theInnoDBbuffer pool based onthe workload. Adjusting the flush rate dynamically is intendedto avoid bursts of I/O activity. This setting is enabled bydefault. SeeSection 14.4.3.2 Configuring the Rate of InnoDB Buffer Pool Flushing formore information. For general I/O tuning advice seeSection 8.5.8 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"10", + "name":"innodb_adaptive_flushing_lwm", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_adaptive_flushing_lwm", + "vartype":"integer", + "max_value":"70", + "scope":"{Global}", + "id":"1278", + "unit":"NULL", + "description":"Low water mark representing percentage ofredo log capacity atwhich adaptiveflushing is enabled." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"ON", + "name":"innodb_adaptive_hash_index", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_adaptive_hash_index", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1279", + "unit":"NULL", + "description":"Whether the InnoDBadaptive hashindex is enabled or disabled. It may be desirabledepending on your workload to dynamically enable or disableadaptive hashindexing to improve query performance. Because theadaptive hash index may not be useful for all workloadsconduct benchmarks with it both enabled and disabled usingrealistic workloads. SeeSection 14.2.6.6 Adaptive Hash Indexes for details.This variable is enabled by default. You can modify thisparameter using the SET GLOBAL statementwithout restarting the server. Changing the setting requiresthe SUPER privilege. You can also use--skip-innodb_adaptive_hash_index at serverstartup to disable it.Disabling the adaptive hash index empties the hash tableimmediately. Normal operations can continue while the hashtable is emptied and executing queries that were using thehash table access the index B-trees directly instead. When theadaptive hash index is re-enabled the hash table is populatedagain during normal operation." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"8", + "name":"innodb_adaptive_hash_index_parts", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_adaptive_hash_index_parts", + "vartype":"numeric", + "max_value":"512", + "scope":"{Global}", + "id":"1280", + "unit":"NULL", + "description":"Partitions the adaptive hash index search system. Each indexis bound to a specific partition with each partitionprotected by a separate latch.Prior to MySQL 5.7.8 the adaptive hash index search systemwas protected by a single latch(btr_search_latch) which could become apoint of contention. With the introduction of theinnodb_adaptive_hash_index_parts optionthe search system is partitioned into 8 parts by default. Themaximum setting is 512.For related information seeSection 14.2.6.6 Adaptive Hash Indexes." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"150000", + "name":"innodb_adaptive_max_sleep_delay", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_adaptive_max_sleep_delay", + "vartype":"integer", + "max_value":"1000000", + "scope":"{Global}", + "id":"1281", + "unit":"NULL", + "description":"Allows InnoDB to automatically adjust thevalue ofinnodb_thread_sleep_delay upor down according to the current workload. Any non-zero valueenables automated dynamic adjustment of theinnodb_thread_sleep_delay value up to themaximum value specified in theinnodb_adaptive_max_sleep_delay option. Thevalue represents the number of microseconds. This option canbe useful in busy systems with greater than 16InnoDB threads. (In practice it is mostvaluable for MySQL systems with hundreds or thousands ofsimultaneous connections.)For more information seeSection 14.4.6 Configuring Thread Concurrency for InnoDB." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"5", + "name":"innodb_api_bk_commit_interval", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_api_bk_commit_interval", + "vartype":"integer", + "max_value":"1073741824", + "scope":"{Global}", + "id":"1283", + "unit":"NULL", + "description":"How often to auto-commit idle connections that use theInnoDB memcachedinterface in seconds. See Section 14.18 InnoDB memcached Pluginfor usage details for this option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"notice", + "name":"client_min_messages", + "deprecated":"f", + "valid_vals":"debug5,debug4,debug3,debug2,debug1,log,notice,warning,error", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the message levels that are sent to the client.", + "vartype":"enum", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1487", + "unit":"", + "description":"Each level includes all the levels that follow it. The later the level the fewer messages are sent." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_api_disable_rowlock", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_api_disable_rowlock", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1284", + "unit":"NULL", + "description":"Use this variable to disable row locks whenInnoDB memcachedperforms DML operations. By defaultinnodb_api_disable_rowlock is set toOFF which means thatmemcached requests row locks for get andset operations. Wheninnodb_api_disable_rowlock is set toON memcached requests atable lock instead of row locks.The innodb_api_disable_rowlock option isnot dynamic. It must be specified on themysqld command line or entered in the MySQLconfiguration file. Configuration takes effect when the pluginis installed which you do each time the MySQL server isstarted." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_api_enable_binlog", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_api_enable_binlog", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1285", + "unit":"NULL", + "description":"Lets you use the InnoDBmemcached plugin with the MySQLbinary log. SeeSection 14.18 InnoDB memcached Plugin for usage details for thisoption." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_api_enable_mdl", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_api_enable_mdl", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1286", + "unit":"NULL", + "description":"Locks the table used by the InnoDBmemcached plugin so that it cannot bedropped or altered by DDLthrough the SQL interface. SeeSection 14.18 InnoDB memcached Plugin for usage details for thisoption." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"innodb_api_trx_level", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_api_trx_level", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"1287", + "unit":"NULL", + "description":"Lets you control the transactionisolation level onqueries processed by the memcachedinterface. See Section 14.18 InnoDB memcached Plugin for usagedetails for this option. The constants corresponding to thefamiliar names are:" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"64", + "name":"innodb_autoextend_increment", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_autoextend_increment", + "vartype":"integer", + "max_value":"1000", + "scope":"{Global}", + "id":"1288", + "unit":"NULL", + "description":"The increment size (in MB) for extending the size of anauto-extend InnoDBsystemtablespace file when it becomes full. The default valueis 64. This variable does not affect file-per-table(.ibd) data files that are created if youuse innodb_file_per_table=1or general tablespace .ibd data files.Those files are auto-extending regardless of the value ofinnodb_autoextend_increment.The initial extensions are by small amounts after whichextensions occur in increments of 4MB." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1", + "name":"innodb_autoinc_lock_mode", + "deprecated":"f", + "valid_vals":"0,1,2", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_autoinc_lock_mode", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"1289", + "unit":"NULL", + "description":"The lock mode to use forgeneratingauto-incrementvalues. The permissible values are 01 or 2 fortraditional consecutive orinterleaved lock mode respectively.Section 14.6.5 AUTO_INCREMENT Handling in InnoDB describesthe characteristics of these modes.This variable has a default of 1 (consecutivelock mode)." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_background_drop_list_empty", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_background_drop_list_empty", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1290", + "unit":"NULL", + "description":"Enabling theinnodb_background_drop_list_empty debugoption helps avoid test case failures by delaying tablecreation until the background drop list is empty. For exampleif test case A places table t1 on thebackground drop list test case B waits until the backgrounddrop list is empty before creating tablet1." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"134217728", + "name":"innodb_buffer_pool_chunk_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1048576", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_buffer_pool_chunk_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"1291", + "unit":"NULL", + "description":"innodb_buffer_pool_chunk_size defines thechunk size for online InnoDB buffer poolresizing operations.As of MySQL 5.7.5 theinnodb_buffer_pool_sizeparameter is dynamic which allows you to resize the bufferpool without restarting the server. To avoid copying allbuffer pool pages during resizing operations the operation isperformed in chunks. Chunk size is defined byinnodb_buffer_pool_chunk_size. By defaultinnodb_buffer_pool_chunk_size is 128MB(134217728 bytes). The number of pages contained in a chunkdepends on the value ofinnodb_page_size.innodb_buffer_pool_chunk_size can beincreased or decreased in units of 1MB (1048576 bytes).The following conditions apply when altering theinnodb_buffer_pool_chunk_sizevalue:To avoid potential performance issues the number of chunks(innodb_buffer_pool_size /innodb_buffer_pool_chunk_size)should not exceed 1000.See Configuring InnoDB Buffer Pool Size Online formore information." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_buffer_pool_dump_at_shutdown", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_buffer_pool_dump_at_shutdown", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1292", + "unit":"NULL", + "description":"Specifies whether to record the pages cached in the InnoDBbuffer pool when theMySQL server is shut down to shorten thewarmup process at the nextrestart. Typically used in combination withinnodb_buffer_pool_load_at_startup.Theinnodb_buffer_pool_dump_pctoption defines the percentage of most recently used bufferpool pages to dump.Bothinnodb_buffer_pool_dump_at_shutdownand innodb_buffer_pool_load_at_startup areenabled by default as of MySQL 5.7.7.For related information seeSection 14.4.3.5 Preloading the InnoDB Buffer Pool for Faster Restart." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_buffer_pool_dump_now", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_buffer_pool_dump_now", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1293", + "unit":"NULL", + "description":"Immediately records the pages cached in the InnoDBbuffer pool. Typicallyused in combination withinnodb_buffer_pool_load_now.For related information seeSection 14.4.3.5 Preloading the InnoDB Buffer Pool for Faster Restart." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"0", + "name":"commit_delay", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the delay in microseconds between transaction commit and flushing WAL to disk.", + "vartype":"integer", + "max_value":"100000", + "scope":"{GlobalSession}", + "id":"1488", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"100", + "name":"innodb_buffer_pool_dump_pct", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_buffer_pool_dump_pct", + "vartype":"integer", + "max_value":"100", + "scope":"{Global}", + "id":"1294", + "unit":"NULL", + "description":"Specifies the percentage of the most recently used pages foreach buffer pool to read out and dump. The range is 1 to 100.Prior to MySQL 5.7.7 the default value is 100 (dump allpages). As of MySQL 5.7.7 the default value is 25. Forexample if there are 4 buffer pools with 100 pages each andinnodb_buffer_pool_dump_pctis set to 25 the 25 most recently used pages from each bufferpool are dumped.The change to theinnodb_buffer_pool_dump_pctdefault value in MySQL 5.7.7 coincides with default valuechanges forinnodb_buffer_pool_dump_at_shutdownandinnodb_buffer_pool_load_at_startupwhich are both enabled by default as of MySQL 5.7.7." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ib_buffer_pool", + "name":"innodb_buffer_pool_filename", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_buffer_pool_filename", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"1295", + "unit":"NULL", + "description":"Specifies the name of the file that holds the list oftablespace IDs and page IDs produced byinnodb_buffer_pool_dump_at_shutdownorinnodb_buffer_pool_dump_now.Tablespace IDs and page IDs are saved in the following format:space page_id. By default the file islocated in the InnoDB data directory.For related information seeSection 14.4.3.5 Preloading the InnoDB Buffer Pool for Faster Restart." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1", + "name":"innodb_buffer_pool_instances", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_buffer_pool_instances", + "vartype":"integer", + "max_value":"64", + "scope":"{Global}", + "id":"1296", + "unit":"NULL", + "description":"The number of regions that the InnoDBbuffer pool is dividedinto. For systems with buffer pools in the multi-gigabyterange dividing the buffer pool into separate instances canimprove concurrency by reducing contention as differentthreads read and write to cached pages. Each page that isstored in or read from the buffer pool is assigned to one ofthe buffer pool instances randomly using a hashing function.Each buffer pool manages its own free listsflush listsLRUs and all other datastructures connected to a buffer pool and is protected by itsown buffer pool mutex.This option only takes effect when you setinnodb_buffer_pool_size to1GB or more. The total buffer pool size is divided among allthe buffer pools. For best efficiency specify a combinationofinnodb_buffer_pool_instancesand innodb_buffer_pool_sizeso that each buffer pool instance is at least 1GB.The default value in on 32-bit Windows systems depends on thevalue ofinnodb_buffer_pool_size asdescribed below:On all other platforms the default value is 8 wheninnodb_buffer_pool_size isgreater than or equal to 1GB. Otherwise the default is 1.For related information seeSection 14.4.3.7 Configuring InnoDB Buffer Pool Size." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_buffer_pool_load_abort", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_buffer_pool_load_abort", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1297", + "unit":"NULL", + "description":"Interrupts the process of restoring InnoDBbuffer pool contentstriggered byinnodb_buffer_pool_load_at_startuporinnodb_buffer_pool_load_now.For related information seeSection 14.4.3.5 Preloading the InnoDB Buffer Pool for Faster Restart." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_buffer_pool_load_at_startup", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_buffer_pool_load_at_startup", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1298", + "unit":"NULL", + "description":"Specifies that on MySQL server startup the InnoDBbuffer pool isautomatically warmed up byloading the same pages it held at an earlier time. Typicallyused in combination withinnodb_buffer_pool_dump_at_shutdown.Bothinnodb_buffer_pool_dump_at_shutdownand innodb_buffer_pool_load_at_startup areenabled by default as of MySQL 5.7.7.For related information seeSection 14.4.3.5 Preloading the InnoDB Buffer Pool for Faster Restart." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_buffer_pool_load_now", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_buffer_pool_load_now", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1299", + "unit":"NULL", + "description":"Immediately warms up theInnoDBbuffer pool by loadinga set of data pages without waiting for a server restart. Canbe useful to bring cache memory back to a known state duringbenchmarking or to ready the MySQL server to resume itsnormal workload after running queries for reports ormaintenance.For related information seeSection 14.4.3.5 Preloading the InnoDB Buffer Pool for Faster Restart." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"134217728", + "name":"innodb_buffer_pool_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"5242880", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_buffer_pool_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"1300", + "unit":"NULL", + "description":"The size in bytes of thebuffer pool thememory area where InnoDB caches table andindex data. The default value is 128MB. The maximum valuedepends on the CPU architecture; the maximum is 4294967295(232-1) on 32-bit systems and18446744073709551615 (264-1) on64-bit systems. On 32-bit systems the CPU architecture andoperating system may impose a lower practical maximum sizethan the stated maximum. When the size of the buffer pool isgreater than 1GB settinginnodb_buffer_pool_instancesto a value greater than 1 can improve the scalability on abusy server.A larger buffer pool requires less disk I/O to access the sametable data more than once. On a dedicated database server youmight set the buffer pool size to 80% of the machine'sphysical memory size. Be aware of the following potentialissues when configuring buffer pool size and be prepared toscale back the size of the buffer pool if necessary.As of MySQL 5.7.5 when you increase or decrease buffer poolsize the operation is performed in chunks. Chunk size isdefined by theinnodb_buffer_pool_chunk_sizeconfiguration option which has a default of 128 MB.Buffer pool size must always be equal to or a multiple ofinnodb_buffer_pool_chunk_size*innodb_buffer_pool_instances.If you alter the buffer pool size to a value that is not equalto or a multiple ofinnodb_buffer_pool_chunk_size*innodb_buffer_pool_instancesbuffer pool size is automatically adjusted to a value that isequal to or a multiple ofinnodb_buffer_pool_chunk_size*innodb_buffer_pool_instancesthat is not less than the specified buffer pool size.As of MySQL 5.7.5 innodb_buffer_pool_sizecan be set dynamically which allows you to resize the bufferpool without restarting the server. TheInnodb_buffer_pool_resize_statusstatus variable reports the status of online buffer poolresizing operations. SeeConfiguring InnoDB Buffer Pool Size Online for moreinformation." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"25", + "name":"innodb_change_buffer_max_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_change_buffer_max_size", + "vartype":"integer", + "max_value":"50", + "scope":"{Global}", + "id":"1301", + "unit":"NULL", + "description":"Maximum size for the InnoDBchange buffer as apercentage of the total size of thebuffer pool. You mightincrease this value for a MySQL server with heavy insertupdate and delete activity or decrease it for a MySQL serverwith unchanging data used for reporting. For general I/Otuning advice see Section 8.5.8 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"all", + "name":"innodb_change_buffering", + "deprecated":"f", + "valid_vals":"none,inserts,deletes,changes,purges,all", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_change_buffering", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"1302", + "unit":"NULL", + "description":"Whether InnoDB performschange bufferingan optimization that delays write operations to secondaryindexes so that the I/O operations can be performedsequentially. The permitted values are described in thefollowing table. For more information seeSection 14.4.5 Configuring InnoDB Change Buffering. Forgeneral I/O tuning advice seeSection 8.5.8 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"innodb_change_buffering_debug", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_change_buffering_debug", + "vartype":"integer", + "max_value":"2", + "scope":"{Global}", + "id":"1303", + "unit":"NULL", + "description":"Sets a debug flag for InnoDB changebuffering. A value of 1 forces all changes to the changebuffer. A value of 2 causes a crash at merge. A default valueof 0 indicates that the change buffering debug flag is notset. This option is only available when debugging support iscompiled in using the WITH_DEBUGCMake option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"innodb", + "name":"innodb_checksum_algorithm", + "deprecated":"f", + "valid_vals":"innodb,crc32,none,strict_innodb,strict_crc32,strict_none", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_checksum_algorithm", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"1304", + "unit":"NULL", + "description":"Specifies how to generate and verify thechecksum stored in eachdisk block of each InnoDBtablespace.The default value forinnodb_checksum_algorithm was changed frominnodb to crc32 in MySQL5.6.6 but switched back to innodb in 5.6.7for improved compatibility of InnoDB datafiles during a downgrade to an earlier MySQL version and foruse with MySQLEnterprise Backup. The limitations encounteredincluded:As of MySQL 5.7.7 crc32 is onceagain the default value forinnodb_checksum_algorithm.innodb_checksum_algorithm replaced theinnodb_checksums option inMySQL 5.6.3. The following values were provided forcompatibility up to and including MySQL 5.7.6:As of MySQl 5.7.7 with a defaultinnodb_checksum_algorithm value of crc32innodb_checksums=ON is now the same asinnodb_checksum_algorithm=crc32.innodb_checksums=OFF is still the same asinnodb_checksum_algorithm=none.To avoid conflicts remove references toinnodb_checksums from yourconfiguration file and MySQL startup scripts.The value innodb is backward-compatiblewith all versions of MySQL. The value crc32uses an algorithm that is faster to compute the checksum forevery modified block and to check the checksums for each diskread. It scans blocks 32 bits at a time which is faster theinnodb checksum algorithm which scansblocks 8 bits at a time. The value nonewrites a constant value in the checksum field rather thancomputing a value based on the block data. The blocks in atablespace can use a mix of old new and no checksum valuesbeing updated gradually as the data is modified; once anyblocks in a tablespace are modified to use thecrc32 algorithm the associated tablescannot be read by earlier versions of MySQL.The strict_* forms work the same asinnodb crc32 andnone except that InnoDBreports an error if it encounters a valid but non-matchingchecksum value in the tablespace. It is recommended that youonly use the strict_* options in a newinstance to set up all tablespaces for the first time. Thestrict_* settings are somewhat fasterbecause they do not need to compute all checksum values duringdisk reads.The following table illustrates the difference between thenone innodb andcrc32 option values and theirstrict_* counterparts.none innodb andcrc32 write the specified type of checksumvalue into each data block but for compatibility accept anyof the other checksum values when verifying a block during aread operation. The strict_* form of eachparameter also accepts any valid checksum value but prints anerror message when a valid non-matching checksum value isencountered. Using the strict_* form canmake verification faster if all InnoDB datafiles in an instance are created under an identicalinnodb_checksum_algorithm value." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"ON", + "name":"innodb_checksums", + "deprecated":"t", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_checksums", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1305", + "unit":"NULL", + "description":"InnoDB can usechecksum validation onall tablespace pages read from the disk to ensure extra faulttolerance against hardware faults or corrupted data files.This validation is enabled by default. Under specializedcircumstances (such as when running benchmarks) this extrasafety feature can be disabled with--skip-innodb-checksums. You can specify themethod of calculating the checksum withinnodb_checksum_algorithm.In MySQL 5.6.3 and higher innodb_checksumsis deprecated replaced byinnodb_checksum_algorithm.Prior to MySQL 5.7.7 innodb_checksums=ONis the same asinnodb_checksum_algorithm=innodb.As of MySQL 5.7.7 theinnodb_checksum_algorithmdefault value is crc32 andinnodb_checksums=ON is the same asinnodb_checksum_algorithm=crc32.innodb_checksums=OFF is the same asinnodb_checksum_algorithm=none.It is recommended that you remove anyinnodb_checksums options from yourconfiguration files and startup scripts to avoid conflictswith innodb_checksum_algorithm.innodb_checksums=OFF automatically setsinnodb_checksum_algorithm=none.innodb_checksums=ON is ignored andoverridden by any other setting forinnodb_checksum_algorithm." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_cmp_per_index_enabled", + "deprecated":"f", + "valid_vals":"OFF,ON", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_cmp_per_index_enabled", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1306", + "unit":"NULL", + "description":"Enables per-index compression-related statistics in theINFORMATION_SCHEMA.INNODB_CMP_PER_INDEXtable. Because these statistics can be expensive to gatheronly enable this option on development test or slaveinstances during performance tuning related toInnoDBcompressed tables." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"innodb_commit_concurrency", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_commit_concurrency", + "vartype":"integer", + "max_value":"1000", + "scope":"{Global}", + "id":"1307", + "unit":"NULL", + "description":"The number of threads thatcan commit at the sametime. A value of 0 (the default) permits any number oftransactions to commitsimultaneously.The value of innodb_commit_concurrencycannot be changed at runtime from zero to nonzero or viceversa. The value can be changed from one nonzero value toanother." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"none", + "name":"innodb_compress_debug", + "deprecated":"f", + "valid_vals":"none,zlib,lz4,lz4hc", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_compress_debug", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"1308", + "unit":"NULL", + "description":"Compresses all tables using a specified compression algorithmwithout having to define a COMPRESSIONattribute for each table. This option is only available ifdebugging support is compiled in using theWITH_DEBUGCMake option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"5", + "name":"innodb_compression_failure_threshold_pct", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_compression_failure_threshold_pct", + "vartype":"integer", + "max_value":"100", + "scope":"{Global}", + "id":"1309", + "unit":"NULL", + "description":"Sets the cutoff point at which MySQL begins adding paddingwithin compressedpages to avoid expensivecompressionfailures. A value of zero disables the mechanism thatmonitors compression efficiency and dynamically adjusts thepadding amount.For more information seeSection 14.7.1.6 Compression for OLTP Workloads." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"6", + "name":"innodb_compression_level", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_compression_level", + "vartype":"integer", + "max_value":"9", + "scope":"{Global}", + "id":"1310", + "unit":"NULL", + "description":"Specifies the level of zlib compression to use forInnoDBcompressed tables andindexes.For more information seeSection 14.7.1.6 Compression for OLTP Workloads." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"50", + "name":"innodb_compression_pad_pct_max", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_compression_pad_pct_max", + "vartype":"integer", + "max_value":"75", + "scope":"{Global}", + "id":"1311", + "unit":"NULL", + "description":"Specifies the maximum percentage that can be reserved as freespace within each compressedpage allowing room toreorganize the data and modification log within the page whena compressed table orindex is updated and the data might be recompressed. Onlyapplies wheninnodb_compression_failure_threshold_pctis set to a non-zero value and the rate ofcompressionfailures passes the cutoff point.For more information seeSection 14.7.1.6 Compression for OLTP Workloads." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"5000", + "name":"innodb_concurrency_tickets", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_concurrency_tickets", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{Global}", + "id":"1312", + "unit":"NULL", + "description":"Determines the number ofthreads that can enterInnoDB concurrently. A thread is placed ina queue when it tries to enter InnoDB ifthe number of threads has already reached the concurrencylimit. When a thread is permitted to enterInnoDB it is given a number of freetickets equal to the value ofinnodb_concurrency_ticketsand the thread can enter and leave InnoDBfreely until it has used up its tickets. After that point thethread again becomes subject to the concurrency check (andpossible queuing) the next time it tries to enterInnoDB. The default value is 5000.With a small innodb_concurrency_ticketsvalue small transactions that only need to process a few rowscompete fairly with larger transactions that process manyrows. The disadvantage of a smallinnodb_concurrency_tickets value is thatlarge transactions must loop through the queue many timesbefore they can complete which extends the length of timerequired to complete their task.With a large innodb_concurrency_ticketsvalue large transactions spend less time waiting for aposition at the end of the queue (controlled byinnodb_thread_concurrency)and more time retrieving rows. Large transactions also requirefewer trips through the queue to complete their task. Thedisadvantage of a largeinnodb_concurrency_tickets value is thattoo many large transactions running at the same time canstarve smaller transactions by making them wait a longer timebefore executing.With a non-zeroinnodb_thread_concurrencyvalue you may need to adjust theinnodb_concurrency_tickets value up or downto find the optimal balance between larger and smallertransactions. The SHOW ENGINE INNODB STATUSreport shows the number of tickets remaining for an executingtransaction in its current pass through the queue. This datamay also be obtained from theTRX_CONCURRENCY_TICKETS column of theINFORMATION_SCHEMA.INNODB_TRXtable.For more information seeSection 14.4.6 Configuring Thread Concurrency for InnoDB." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_create_intrinsic", + "deprecated":"t", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_create_intrinsic", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Session}", + "id":"1313", + "unit":"NULL", + "description":"When innodb_create_intrinsic is enabledCREATE TEMPORYTABLE creates optimized temporarytables instead of normal temporary tables.An optimized temporary table is a lightweight subclass oftemporary table that excludes certain functionality andbenefits from optimizations that makes it faster than a normaltemporary table. Like normal temporary tables optimizedtemporary tables are only visible to the current connectionand are dropped when the connection is terminated. Unlikenormal temporary tables optimized temporary tables areoperational when InnoDB is in read-onlymode.Row format COMPRESSED is not supported. Ifyou attempt to create a compressed optimized temporary tablethe innodb_create_intrinsic=ON setting isignored and InnoDB creates a normaltemporary table.Optimized temporary table metadata is not available in theINFORMATION_SCHEMA.INNODB_TEMP_TABLE_INFOtable.Undo logging is disabled for optimized temporary tables whichmeans that rollback is also not supported.Atomicity for optimized temporary tables is supported at therow-level not at the statement level.Statistics generated by the same workload may differ forintrinsic temporary tables compared to normal temporarytables as optimized temporary tables may use a differentalgorithm to complete certain types of operations.innodb_create_intrinsic was removed inMySQL 5.7.6." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ibdata1:12M:autoextend", + "name":"innodb_data_file_path", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_data_file_path", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"1314", + "unit":"NULL", + "description":"The paths to individual InnoDBdata files and theirsizes. The full directory path to each data file is formed byconcatenatinginnodb_data_home_dir to eachpath specified here. The file sizes are specified KB MB or GB(1024MB) by appending KM or G to the sizevalue. If specifying data file size in kilobytes (KB) do soin multiples of 1024. Otherwise KB values are rounded off tonearest megabyte (MB) boundary. The sum of the sizes of thefiles must be at least slightly larger than 10MB. If you donot specify innodb_data_file_path thedefault behavior is to create a single auto-extending datafile slightly larger than 12MB namedibdata1. The size limit of individualfiles is determined by your operating system. You can set thefile size to more than 4GB on those operating systems thatsupport big files. You can alsouse raw disk partitions asdata files. For detailed information on configuringInnoDBtablespace files seeSection 14.4 InnoDB Configuration.As of MySQL 5.7.8 the following minimum file sizes areenforced for the first system tablespacedata file (ibdata1) to ensure that there isenough space for doublewrite buffer blocks (Bug #20972309):" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"innodb_data_home_dir", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_data_home_dir", + "vartype":"directory name", + "max_value":"NULL", + "scope":"{Global}", + "id":"1315", + "unit":"NULL", + "description":"The common part of the directory path for allInnoDB datafiles in thesystemtablespace. This setting does not affect the locationof file-per-tabletablespaces wheninnodb_file_per_table isenabled. The default value is the MySQLdata directory. If you specify the valueas an empty string you can use absolute file paths ininnodb_data_file_path." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"Antelope", + "name":"innodb_file_format_max", + "deprecated":"t", + "valid_vals":"Antelope,Barracuda", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_file_format_max", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"1324", + "unit":"NULL", + "description":"At server startup InnoDB sets the value ofthis variable to the fileformat tag in thesystemtablespace (for example Antelope orBarracuda). If the server creates or opensa table with a higher file format it sets thevalue ofinnodb_file_format_max tothat format.The innodb_file_format_maxoption is deprecated in MySQL 5.7.7 together with theinnodb_file_format option.Both options will be removed in a future release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"5", + "name":"commit_siblings", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the minimum concurrent open transactions before performing commit_delay.", + "vartype":"integer", + "max_value":"1000", + "scope":"{GlobalSession}", + "id":"1489", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"/etc/postgresql/9.3/main/postgresql.conf", + "name":"config_file", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"f", + "rank":"-1", + "summary":"Sets the server's main configuration file.", + "vartype":"string", + "max_value":"", + "scope":"{Global}", + "id":"1490", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"DYNAMIC", + "name":"innodb_default_row_format", + "deprecated":"f", + "valid_vals":"DYNAMIC,COMPACT,REDUNDANT", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_default_row_format", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"1316", + "unit":"NULL", + "description":"The innodb_default_row_format optionintroduced in MySQL 5.7.9 defines the default row format forInnoDB tables (including user-createdInnoDB temporary tables). The defaultsetting is DYNAMIC. Other permitted valuesare COMPACT andREDUNDANT. TheCOMPRESSED row format which is notsupported for use in the system tablespace cannot be definedas the default.Newly created tables use the row format defined byinnodb_default_row_formatwhen a ROW_FORMAT option is not specifiedexplicitly or when ROW_FORMAT=DEFAULT isused.When a ROW_FORMAT option is not specifiedexplicitly or when ROW_FORMAT=DEFAULT isused any operation that rebuilds a table also silentlychanges the row format of the table to the format defined byinnodb_default_row_format.For more information seeSection 14.9.2 Specifying the Row Format for a Table.Internal InnoDB temporary tables created bythe server to process queries use theDYNAMIC row format regardless of theinnodb_default_row_formatsetting.In MySQL 5.7.8 and earlier the default row format isCOMPACT." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_disable_sort_file_cache", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_disable_sort_file_cache", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1317", + "unit":"NULL", + "description":"If enabled this variable disables the operating system filesystem cache for merge-sort temporary files. The effect is toopen such files with the equivalent ofO_DIRECT." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"innodb_disable_resize_buffer_pool_debug", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_disable_resize_buffer_pool_debug", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1318", + "unit":"NULL", + "description":"Disables resizing of the InnoDB bufferpool. This option is only available if debugging support iscompiled in using the WITH_DEBUGCMake option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"ON", + "name":"innodb_doublewrite", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_doublewrite", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1319", + "unit":"NULL", + "description":"If this variable is enabled (the default)InnoDB stores all data twice first to thedoublewritebuffer then to the actualdata files. Thisvariable can be turned off with--skip-innodb_doublewrite for benchmarks orcases when top performance is needed rather than concern fordata integrity or possible failures." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1", + "name":"innodb_fast_shutdown", + "deprecated":"f", + "valid_vals":"0,1,2", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_fast_shutdown", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"1320", + "unit":"NULL", + "description":"The InnoDBshutdown mode. If thevalue is 0 InnoDB does aslow shutdown afull purge and a changebuffer merge before shutting down. If the value is 1 (thedefault) InnoDB skips these operations atshutdown a process known as afast shutdown. Ifthe value is 2 InnoDB flushes its logs andshuts down cold as if MySQL had crashed; no committedtransactions are lost but thecrash recoveryoperation makes the next startup take longer.The slow shutdown can take minutes or even hours in extremecases where substantial amounts of data are still buffered.Use the slow shutdown technique before upgrading ordowngrading between MySQL major releases so that all datafiles are fully prepared in case the upgrade process updatesthe file format.Use innodb_fast_shutdown=2 in emergency ortroubleshooting situations to get the absolute fastestshutdown if data is at risk of corruption." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"innodb_fil_make_page_dirty_debug", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_fil_make_page_dirty_debug", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{Global}", + "id":"1321", + "unit":"NULL", + "description":"By default settinginnodb_fil_make_page_dirty_debug to the IDof a tablespace immediately dirties the first page of thetablespace. Ifinnodb_saved_page_number_debugis set to a non-default value settinginnodb_fil_make_page_dirty_debug dirtiesthe specified page. Theinnodb_fil_make_page_dirty_debug option isonly available if debugging support is compiled in using theWITH_DEBUGCMake option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"Antelope", + "name":"innodb_file_format", + "deprecated":"t", + "valid_vals":"Antelope,Barracuda", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_file_format", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"1322", + "unit":"NULL", + "description":"The file format to usefor new InnoDB tables. CurrentlyAntelope and Barracudaare supported. This setting only applies to tables that havetheir ownfile-per-tabletablespace so for itto have an effectinnodb_file_per_table must beenabled. The Barracudafile format is required to useCompressedor Dynamic rowformats and associated features such ascompression off-pagestorage for large variable-length columns and large index keyprefixes (seeinnodb_large_prefix). Thisrestriction does not apply to tables stored in generaltablespaces. For more information seeSection 14.5.9 InnoDB General Tablespaces.Be aware that ALTER TABLEoperations that recreate InnoDB tables(ALGORITHM=COPY) in file-per-tabletablespaces will use the currentinnodb_file_format setting (the conditionsoutlined above still apply).The innodb_file_format default value waschanged to Barracuda in MySQL 5.7.7. Thischange allowsCompressedor Dynamic rowformats to be used for tables stored in file-per-tabletablespaces.The innodb_file_format optionis also deprecated in MySQL 5.7.7 and will be removed in afuture release. The purpose of theinnodb_file_format option was to allowusers to downgrade to the built-in version ofInnoDB in MySQL 5.1. Now that MySQL 5.1 hasreached the end of its product lifecycle downgrade supportprovided by this option is no longer necessary." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"innodb_file_format_check", + "deprecated":"t", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_file_format_check", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1323", + "unit":"NULL", + "description":"This variable can be set to 1 or 0 at server startup to enableor disable whether InnoDB checks thefile format tag in thesystemtablespace (for example Antelope orBarracuda). If the tag is checked and ishigher than that supported by the current version ofInnoDB an error occurs andInnoDB does not start. If the tag is nothigher InnoDB sets the value ofinnodb_file_format_max to thefile format tag.The innodb_file_format_checkoption is deprecated in MySQL 5.7.7 together with theinnodb_file_format option.Both options will be removed in a future release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"partition", + "name":"constraint_exclusion", + "deprecated":"f", + "valid_vals":"partition,on,off", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Enables the planner to use constraints to optimize queries.", + "vartype":"enum", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1491", + "unit":"", + "description":"Table scans will be skipped if their constraints guarantee that no rows match the query." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"ON", + "name":"innodb_file_per_table", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_file_per_table", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1325", + "unit":"NULL", + "description":"When innodb_file_per_table is enabled (thedefault in 5.6.6 and higher) InnoDB storesthe data and indexes for each newly created table in aseparate.ibdfile rather than in the system tablespace. The storagefor these InnoDB tables is reclaimed whenthe tables are dropped or truncated. This setting enablesseveral other InnoDB features such astable compression. SeeSection 14.5.4 InnoDB File-Per-Table Tablespaces for detailsabout such features as well as advantages and disadvantages ofusing per-table tablespaces.Be aware that enablinginnodb_file_per_table alsomeans that an ALTER TABLEoperation will move InnoDB table from thesystem tablespace to an individual .ibdfile in cases where ALTER TABLErecreates the table (ALGORITHM=COPY). Anexception to this rule is for tables that were placed in thesystem tablespace using theTABLESPACE=innodb_system option withCREATE TABLE orALTER TABLE. These tables areunaffected by the innodb_file_per_tablesetting and can only be moved to file-per-table tablespacesusing ALTER TABLE... TABLESPACE=innodb_file_per_table.When innodb_file_per_table is disabledInnoDB stores the data for all tables andindexes in the ibdatafiles that make up thesystemtablespace. This setting reduces the performanceoverhead of filesystem operations for operations such asDROP TABLE orTRUNCATE TABLE. It is mostappropriate for a server environment where entire storagedevices are devoted to MySQL data. Because the systemtablespace never shrinks and is shared across all databasesin an instance avoidloading huge amounts of temporary data on a space-constrainedsystem when innodb_file_per_table=OFF. Setup a separate instance in such cases so that you can drop theentire instance to reclaim the space.By default innodb_file_per_table isenabled as of MySQL 5.6.6 disabled before that. Considerdisabling it if backward compatibility with MySQL 5.5 or 5.1is a concern. This will prevent ALTERTABLE from movingInnoDB tables from the systemtablespace to individual .ibd files.innodb_file_per_table isdynamic and can be set ON orOFF using SET GLOBAL.You can also set this parameter in the MySQLconfigurationfile (my.cnf ormy.ini) but this requires shutting downand restarting the server.Dynamically changing the value of this parameter requires theSUPER privilege and immediately affects theoperation of all connections." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"100", + "name":"innodb_fill_factor", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"10", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_fill_factor", + "vartype":"integer", + "max_value":"100", + "scope":"{Global}", + "id":"1326", + "unit":"NULL", + "description":"As of MySQL 5.7.5 InnoDB performs a bulkload when creating or rebuilding indexes. This method of indexcreation is known as a sorted index build.innodb_fill_factor defines the percentageof space on each B-tree page that is filled during a sortedindex build with the remaining space reserved for futureindex growth. For example settinginnodb_fill_factor to 80 reserves 20percent of the space on each B-tree page for future indexgrowth. Actual percentages may vary. Theinnodb_fill_factor setting is interpretedas a hint rather than a hard limit.As of MySQL 5.7.8 aninnodb_fill_factor setting of100 leaves 1/16 of the space in clustered index pages free forfuture index growth (MySQL Bug #74325).innodb_fill_factor applies to both B-treeleaf and non-leaf pages. It does not apply to external pagesused for TEXT orBLOB entries.For more information seeSection 14.2.6.8 Sorted Index Builds." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1", + "name":"innodb_flush_log_at_timeout", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_flush_log_at_timeout", + "vartype":"integer", + "max_value":"2700", + "scope":"{Global}", + "id":"1327", + "unit":"NULL", + "description":"Write and flush the logs every Nseconds.innodb_flush_log_at_timeoutwas introduced in MySQL 5.6.6. It allows the timeout periodbetween flushes to be increased in order to reduce flushingand avoid impacting performance of binary log group commit.Prior to MySQL 5.6.6 flushing frequency was once per second.The default setting forinnodb_flush_log_at_timeoutis also once per second." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1", + "name":"innodb_flush_log_at_trx_commit", + "deprecated":"f", + "valid_vals":"0,1,2", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_flush_log_at_trx_commit", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"1328", + "unit":"NULL", + "description":"Controls the balance between strictACID compliance forcommit operations andhigher performance that is possible when commit-related I/Ooperations are rearranged and done in batches. You can achievebetter performance by changing the default value but then youcan lose up to a second of transactions in a crash.For durability and consistency in a replication setup thatuses InnoDB with transactions:" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULLfsyncO_DSYNCO_DIRECT}", + "dangerous":"PARTIALLY", + "default_val":"NULL", + "name":"innodb_flush_method", + "deprecated":"f", + "valid_vals":"NULL,fsync,O_DSYNC,O_DIRECT,O_DIRECT_NO_FSYNC,littlesync,nosync", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_flush_method", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"1329", + "unit":"NULL", + "description":"Defines the method used toflush data to theInnoDB datafiles and logfiles which can affect I/O throughput.If innodb_flush_method=NULL on a Unix-likesystem the fsync option is used bydefault. If innodb_flush_method=NULL onWindows the async_unbuffered option isused by default.The innodb_flush_method options forUnix-like systems include:The innodb_flush_method options for Windowssystems include:How each settings affects performance depends on hardwareconfiguration and workload. Benchmark your particularconfiguration to decide which setting to use or whether tokeep the default setting. Examine theInnodb_data_fsyncs statusvariable to see the overall number offsync() calls for each setting. The mix ofread and write operations in your workload can affect how asetting performs. For example on a system with a hardwareRAID controller and battery-backed write cacheO_DIRECT can help to avoid double bufferingbetween the InnoDB buffer pool and theoperating system's file system cache. On some systems whereInnoDB data and log files are located on aSAN the default value or O_DSYNC might befaster for a read-heavy workload with mostlySELECT statements. Always test thisparameter with hardware and workload that reflect yourproduction environment. For general I/O tuning advice seeSection 8.5.8 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1", + "name":"innodb_flush_neighbors", + "deprecated":"f", + "valid_vals":"0,1,2", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_flush_neighbors", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"1330", + "unit":"NULL", + "description":"Specifies whether flushing apage from the InnoDB bufferpool also flushes otherdirty pages in the sameextent.When the table data is stored on a traditionalHDD storage device flushingsuch neighbor pagesin one operation reduces I/O overhead (primarily for disk seekoperations) compared to flushing individual pages at differenttimes. For table data stored onSSD seek time is not asignificant factor and you can turn this setting off to spreadout the write operations. For general I/O tuning advice seeSection 8.5.8 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"ON", + "name":"innodb_flush_sync", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_flush_sync", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1331", + "unit":"NULL", + "description":"The innodb_flush_sync parameter which isenabled by default causes theinnodb_io_capacity setting tobe ignored for bursts of I/O activity that occur atcheckpoints. To adhereto the limit on InnoDB background I/O activity defined by theinnodb_io_capacitysetting disable innodb_flush_sync." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"0.005", + "name":"cpu_index_tuple_cost", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the planner's estimate of the cost of processing each index entry during an index scan.", + "vartype":"real", + "max_value":"1.79769e+308", + "scope":"{GlobalSession}", + "id":"1492", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"0.0025", + "name":"cpu_operator_cost", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the planner's estimate of the cost of processing each operator or function call.", + "vartype":"real", + "max_value":"1.79769e+308", + "scope":"{GlobalSession}", + "id":"1493", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"30", + "name":"innodb_flushing_avg_loops", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_flushing_avg_loops", + "vartype":"integer", + "max_value":"1000", + "scope":"{Global}", + "id":"1332", + "unit":"NULL", + "description":"Number of iterations for which InnoDB keeps the previouslycalculated snapshot of the flushing state controlling howquickly adaptiveflushing responds to changingworkloads. Increasing thevalue makes the rate offlush operations changesmoothly and gradually as the workload changes. Decreasing thevalue makes adaptive flushing adjust quickly to workloadchanges which can cause spikes in flushing activity if theworkload increases and decreases suddenly." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_force_load_corrupted", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_force_load_corrupted", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1333", + "unit":"NULL", + "description":"Lets InnoDB load tables at startup that are marked ascorrupted. Use only during troubleshooting to recover datathat is otherwise inaccessible. When troubleshooting iscomplete turn this setting back off and restart the server." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"innodb_force_recovery", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_force_recovery", + "vartype":"integer", + "max_value":"6", + "scope":"{Global}", + "id":"1334", + "unit":"NULL", + "description":"The crash recoverymode typically only changed in serious troubleshootingsituations. Possible values are from 0 to 6. For the meaningsof these values and important information aboutinnodb_force_recovery seeSection 14.19.2 Forcing InnoDB Recovery." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"innodb_ft_aux_table", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_ft_aux_table", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"1335", + "unit":"NULL", + "description":"Specifies the qualified name of an InnoDBtable containing a FULLTEXT index. Thisvariable is intended for diagnostic purposes.After you set this variable to a name in the formatdb_name/table_namethe INFORMATION_SCHEMA tablesINNODB_FT_INDEX_TABLEINNODB_FT_INDEX_CACHEINNODB_FT_CONFIGINNODB_FT_DELETED andINNODB_FT_BEING_DELETED will showinformation about the search index for the specified table." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"8000000", + "name":"innodb_ft_cache_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1600000", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_ft_cache_size", + "vartype":"integer", + "max_value":"80000000", + "scope":"{Global}", + "id":"1336", + "unit":"NULL", + "description":"The memory allocated in bytes for theInnoDB FULLTEXT searchindex cache which holds a parsed document in memory whilecreating an InnoDBFULLTEXT index. Index inserts and updatesare only committed to disk when theinnodb_ft_cache_size size limit is reached.innodb_ft_cache_size defines the cache sizeon a per table basis. To set a global limit for all tablesseeinnodb_ft_total_cache_size." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_ft_enable_diag_print", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_ft_enable_diag_print", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1337", + "unit":"NULL", + "description":"Whether to enable additional full-text search (FTS) diagnosticoutput. This option is primarily intended for advanced FTSdebugging and will not be of interest to most users. Output isprinted to the error log and includes information such as:" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"ON", + "name":"innodb_ft_enable_stopword", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_ft_enable_stopword", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1338", + "unit":"NULL", + "description":"Specifies that a set ofstopwords is associatedwith an InnoDB FULLTEXTindex at the time the index is created. If theinnodb_ft_user_stopword_tableoption is set the stopwords are taken from that table. Elseif theinnodb_ft_server_stopword_tableoption is set the stopwords are taken from that table.Otherwise a built-in set of default stopwords is used." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"84", + "name":"innodb_ft_max_token_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"10", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_ft_max_token_size", + "vartype":"integer", + "max_value":"252", + "scope":"{Global}", + "id":"1339", + "unit":"NULL", + "description":"Maximum character length of words that are stored in an InnoDBFULLTEXT index. Setting a limit on thisvalue reduces the size of the index thus speeding up queriesby omitting long keywords or arbitrary collections of lettersthat are not real words and are not likely to be search terms." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"3", + "name":"innodb_ft_min_token_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_ft_min_token_size", + "vartype":"integer", + "max_value":"16", + "scope":"{Global}", + "id":"1340", + "unit":"NULL", + "description":"Minimum length of words that are stored in an InnoDBFULLTEXT index. Increasing this valuereduces the size of the index thus speeding up queries byomitting common word that are unlikely to be significant in asearch context such as the English words a andto. For content using a CJK (Chinese JapaneseKorean) character set specify a value of 1." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"2000", + "name":"innodb_ft_num_word_optimize", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_ft_num_word_optimize", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"1341", + "unit":"NULL", + "description":"Number of words to process during eachOPTIMIZE TABLE operation on anInnoDB FULLTEXT index.Because a bulk insert or update operation to a tablecontaining a full-text search index could require substantialindex maintenance to incorporate all changes you might do aseries of OPTIMIZE TABLEstatements each picking up where the last left off." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"2000000000", + "name":"innodb_ft_result_cache_limit", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1000000", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_ft_result_cache_limit", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"1342", + "unit":"NULL", + "description":"The InnoDB FULLTEXT search (FTS) queryresult cache limit (defined in bytes) per FTS query or perthread. Intermediate and final InnoDB FTSquery results are handled in memory. Useinnodb_ft_result_cache_limit to place asize limit on the InnoDB FTS query resultcache to avoid excessive memory consumption in case of verylarge InnoDB FTS query results (millions orhundreds of millions of rows for example). Memory isallocated as required when an FTS query is processed. If theresult cache size limit is reached an error is returnedindicating that the query exceeds the maximum allowed memory.As of MySQL 5.7.4 the maximum value ofinnodb_ft_result_cache_limit for allplatform types and platform bit sizes is 2**32-1. Bug #71554." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"0.01", + "name":"cpu_tuple_cost", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the planner's estimate of the cost of processing each tuple (row).", + "vartype":"real", + "max_value":"1.79769e+308", + "scope":"{GlobalSession}", + "id":"1494", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"NULL", + "name":"innodb_ft_server_stopword_table", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_ft_server_stopword_table", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"1343", + "unit":"NULL", + "description":"This option is used to specify your ownInnoDB FULLTEXT indexstopword list for all InnoDB tables. Toconfigure your own stopword list for a specificInnoDB table useinnodb_ft_user_stopword_table.Set innodb_ft_server_stopword_table to thename of the table containing a list of stopwords in theformatdb_name/table_name.The stopword table must exist before you configureinnodb_ft_server_stopword_table.innodb_ft_enable_stopword must be enabledand innodb_ft_server_stopword_table optionmust be configured before you create theFULLTEXT index.The stopword table must be an InnoDB tablecontaining a single VARCHAR column namedvalue.For more information seeSection 12.9.4 Full-Text Stopwords." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"2", + "name":"innodb_ft_sort_pll_degree", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_ft_sort_pll_degree", + "vartype":"integer", + "max_value":"32", + "scope":"{Global}", + "id":"1344", + "unit":"NULL", + "description":"Number of threads used in parallel to index and tokenize textin an InnoDB FULLTEXTindex when building asearch index. Seeinnodb_sort_buffer_size foradditional usage information." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"640000000", + "name":"innodb_ft_total_cache_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"32000000", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_ft_total_cache_size", + "vartype":"integer", + "max_value":"1600000000", + "scope":"{Global}", + "id":"1345", + "unit":"NULL", + "description":"The total memory allocated in bytes for theInnoDB FULLTEXT search index cache for alltables. Creating numerous tables each with a full-text searchindex could consume a significant portion of availablememory.innodb_ft_total_cache_sizedefines a global memory limit for all full-text search indexesto help avoid excessive memory consumption. If the globallimit is reached by an index operation a force sync istriggered." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"NULL", + "name":"innodb_ft_user_stopword_table", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_ft_user_stopword_table", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1346", + "unit":"NULL", + "description":"This option is used to specify your ownInnoDB FULLTEXT indexstopword list on a specific table. To configure your ownstopword list for all InnoDB tables useinnodb_ft_server_stopword_table.Set innodb_ft_user_stopword_table to thename of the table containing a list of stopwords in theformatdb_name/table_name.The stopword table must exist before you configureinnodb_ft_user_stopword_table.innodb_ft_enable_stopword must be enabledand innodb_ft_user_stopword_table must beconfigured before you create the FULLTEXTindex.The stopword table must be an InnoDB tablecontaining a single VARCHAR column namedvalue.For more information seeSection 12.9.4 Full-Text Stopwords." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"200", + "name":"innodb_io_capacity", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"100", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_io_capacity", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"1347", + "unit":"NULL", + "description":"The innodb_io_capacityparameter sets an upper limit on the I/O activity performed bythe InnoDB background tasks such asflushing pages from thebuffer pool andmerging data from thechange buffer. Thedefault value is 200. For busy systems capable of higher I/Orates you can set a higher value at server startup to helpthe server handle the background maintenance work associatedwith a high rate of row changes.The innodb_io_capacity limitis a total limit for all buffer pool instances. When dirtypages are flushed theinnodb_io_capacity limit isdivided equally among buffer pool instances.As of MySQL 5.7.2 theinnodb_io_capacity setting isalso used to limit the number of buffer pool load operationsper second when there is other I/O activity being performed byInnoDB background tasks.For systems with individual 5400 RPM or 7200 RPM drives youmight lower the value to the former default of100This parameter should be set to approximately the number ofI/O operations that the system can perform per second.Ideally keep this setting as low as practical but not so lowthat these background activities fall behind. If the value istoo high data is removed from the buffer pool and insertbuffer too quickly to provide significant benefit from thecaching.The value represents an estimated proportion of the I/Ooperations per second (IOPS) available to older-generationdisk drives that could perform about 100 IOPS. The currentdefault of 200 reflects that modern storage devices arecapable of much higher I/O rates.In general you can increase the value as a function of thenumber of drives used for InnoDBI/O particularly fast drives capable of high numbers of IOPS.For example systems that use multiple disks or solid-statedisks for InnoDB are likely tobenefit from the ability to control this parameter.Although you can specify a very high number in practice suchlarge values have little if any benefit; for example a valueof one million would be considered very high.You can set the innodb_io_capacity value toany number 100 or greater to a maximum defined byinnodb_io_capacity_max. Thedefault value is 200. You can set the valueof this parameter in the MySQL option file(my.cnf or my.ini) orchange it dynamically with the SET GLOBALcommand which requires the SUPERprivilege.The innodb_flush_syncconfiguration option introduced in MySQL 5.7.8 causes theinnodb_io_capacity setting tobe ignored during bursts of I/O activity that occur atcheckpoints.innodb_flush_sync is enabledby default.See Section 14.4.8 Configuring the InnoDB Master Thread I/O Rate formore information about theinnodb_io_capacity setting. For generalinformation about InnoDB I/O performance seeSection 8.5.8 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"2000", + "name":"innodb_io_capacity_max", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"2000", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_io_capacity_max", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"1348", + "unit":"NULL", + "description":"The limit up to which InnoDB is allowed toextend the innodb_io_capacitysetting in case of emergency. If you specify aninnodb_io_capacity setting atstartup and do not specify a value forinnodb_io_capacity_max theinnodb_io_capacity_max value defaults totwice the value ofinnodb_io_capacity with alower limit of 2000. 2000 is also the initial defaultinnodb_io_capacity_max configuration value.The innodb_io_capacity_maxsetting is a total limit for all buffer pool instances.For a brief period during MySQL 5.6 development this variablewas known as innodb_max_io_capacity." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"50331648", + "name":"innodb_log_file_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1048576", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_log_file_size", + "vartype":"integer", + "max_value":"512GB / innodb_log_files_in_group", + "scope":"{Global}", + "id":"1357", + "unit":"NULL", + "description":"The size in bytes of each logfile in alog group.The combined size of log files(innodb_log_file_size *innodb_log_files_in_group)cannot exceed a maximum value that is slightly less than512GB. A pair of 255 GB log files for example would allowyou to approach the limit but not exceed it. The default valueis 48MB. Sensible values range from 4MB to1/N-th of the size of thebuffer pool whereN is the number of log files in thegroup. The larger the value the less checkpoint flushactivity is needed in the buffer pool saving disk I/O. Largerlog files also makecrashrecovery slower although improvements to recoveryperformance in MySQL 5.5 and higher make the log file sizeless of a consideration. For general I/O tuning advice seeSection 8.5.8 Optimizing InnoDB Disk I/O.The minimum innodb_log_file_size value wasincreased from 1MB to 4MB in MySQL 5.7.11." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_large_prefix", + "deprecated":"t", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_large_prefix", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1349", + "unit":"NULL", + "description":"When this option is enabled index key prefixes longer than767 bytes (up to 3072 bytes) are allowed forInnoDB tables that use theDYNAMICandCOMPRESSEDrow formats. See Section 14.6.7 Limits on InnoDB Tables for therelevant maximums associated with index key prefixes undervarious settings.For tables using theREDUNDANTandCOMPACTrow formats this option does not affect the allowed index keyprefix length.innodb_large_prefix is enabled by defaultin MySQL 5.7.7. This change coincides with the default valuechange for innodb_file_format which is setto Barracuda by default in MySQL 5.7.7.Together these default value changes allow larger index keyprefixes to be created when usingROW_FORMAT=DYNAMIC orROW_FORMAT=COMPRESSED. If either option isset to a non-default value index key prefixes larger than 767bytes are silently truncated.innodb_large_prefix is deprecated in MySQL5.7.7 and will be removed in a future release.innodb_large_prefix was introduced in MySQL5.5 to allow users to disable large index key prefixes forcompatibility with earlier versions of MySQL andInnoDB that do not support large index keyprefixes." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"innodb_limit_optimistic_insert_debug", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_limit_optimistic_insert_debug", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{Global}", + "id":"1350", + "unit":"NULL", + "description":"Limits the number of records perB-tree page. A defaultvalue of 0 means that no limit is imposed. This option is onlyavailable if debugging support is compiled in using theWITH_DEBUGCMake option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"50", + "name":"innodb_lock_wait_timeout", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_lock_wait_timeout", + "vartype":"integer", + "max_value":"1073741824", + "scope":"{GlobalSession}", + "id":"1351", + "unit":"NULL", + "description":"The length of time in seconds an InnoDBtransaction waits fora row lock before givingup. The default value is 50 seconds. A transaction that triesto access a row that is locked by anotherInnoDB transaction waits at most this manyseconds for write access to the row before issuing thefollowing error:When a lock wait timeout occurs the current statement isrolled back (not theentire transaction). To have the entire transaction roll backstart the server with the--innodb_rollback_on_timeoutoption. See also Section 14.19.4 InnoDB Error Handling.You might decrease this value for highly interactiveapplications or OLTP systemsto display user feedback quickly or put the update into aqueue for processing later. You might increase this value forlong-running back-end operations such as a transform step ina data warehouse that waits for other large insert or updateoperations to finish.innodb_lock_wait_timeout applies toInnoDB row locks only. A MySQLtable lock does nothappen inside InnoDB and this timeout doesnot apply to waits for table locks.The lock wait timeout value does not apply todeadlocks becauseInnoDB detects them immediately and rollsback one of the deadlocked transactions.innodb_lock_wait_timeout canbe set at runtime with the SET GLOBAL orSET SESSION statement. Changing theGLOBAL setting requires theSUPER privilege and affects the operationof all clients that subsequently connect. Any client canchange the SESSION setting forinnodb_lock_wait_timeoutwhich affects only that client." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_locks_unsafe_for_binlog", + "deprecated":"t", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_locks_unsafe_for_binlog", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1352", + "unit":"NULL", + "description":"This variable affects how InnoDB usesgap locking for searchesand index scans. As of MySQL 5.6.3innodb_locks_unsafe_for_binlog isdeprecated and will be removed in a future MySQL release.Normally InnoDB uses an algorithm callednext-key locking that combines index-row locking withgap locking.InnoDB performs row-level locking in such away that when it searches or scans a table index it setsshared or exclusive locks on the index records it encounters.Thus the row-level locks are actually index-record locks. Inaddition a next-key lock on an index record also affects thegap before that index record. That is anext-key lock is an index-record lock plus a gap lock on thegap preceding the index record. If one session has a shared orexclusive lock on record R in an indexanother session cannot insert a new index record in the gapimmediately before R in the index order.See Section 14.3.2 InnoDB Record Gap and Next-Key Locks.By default the value ofinnodb_locks_unsafe_for_binlog is 0(disabled) which means that gap locking is enabled:InnoDB uses next-key locks for searches andindex scans. To enable the variable set it to 1. This causesgap locking to be disabled: InnoDB usesonly index-record locks for searches and index scans.Enabling innodb_locks_unsafe_for_binlogdoes not disable the use of gap locking for foreign-keyconstraint checking or duplicate-key checking.The effect of enablinginnodb_locks_unsafe_for_binlog is similarto but not identical to setting the transaction isolationlevel to READ COMMITTED:READ COMMITTED thereforeoffers finer and more flexible control thaninnodb_locks_unsafe_for_binlog.For additional details about the effect of isolation level ongap locking see Section 13.3.6 SET TRANSACTION Syntax.Enabling innodb_locks_unsafe_for_binlog maycause phantom problems because other sessions can insert newrows into the gaps when gap locking is disabled. Suppose thatthere is an index on the id column of thechild table and that you want to read andlock all rows from the table having an identifier value largerthan 100 with the intention of updating some column in theselected rows later:The query scans the index starting from the first record whereid is greater than 100. If the locks set onthe index records in that range do not lock out inserts madein the gaps another session can insert a new row into thetable. Consequently if you were to execute the sameSELECT again within the sametransaction you would see a new row in the result setreturned by the query. This also means that if new items areadded to the database InnoDB does notguarantee serializability. Therefore ifinnodb_locks_unsafe_for_binlog is enabledInnoDB guarantees at most an isolationlevel of READ COMMITTED.(Conflict serializability is still guaranteed.) For additionalinformation about phantoms seeSection 14.3.3 Avoiding the Phantom Problem Using Next-Key Locking.Enabling innodb_locks_unsafe_for_binlog hasadditional effects:Consider the following example beginning with this table:In this case table has no indexes so searches and indexscans use the hidden clustered index for record locking (seeSection 14.2.6.2 Clustered and Secondary Indexes).Suppose that one client performs anUPDATE using these statements:Suppose also that a second client performs anUPDATE by executing thesestatements following those of the first client:As InnoDB executes eachUPDATE it first acquires anexclusive lock for each row and then determines whether tomodify it. If InnoDB does not modify therow and innodb_locks_unsafe_for_binlog isenabled it releases the lock. OtherwiseInnoDB retains the lock until the end ofthe transaction. This affects transaction processing asfollows.If innodb_locks_unsafe_for_binlog isdisabled the first UPDATEacquires x-locks and does not release any of them:The second UPDATE blocks assoon as it tries to acquire any locks (because first updatehas retained locks on all rows) and does not proceed untilthe first UPDATE commits orrolls back:If innodb_locks_unsafe_for_binlog isenabled the first UPDATEacquires x-locks and releases those for rows that it does notmodify:For the second UPDATEInnoDB does asemi-consistent read returning the latestcommitted version of each row to MySQL so that MySQL candetermine whether the row matches the WHEREcondition of the UPDATE:" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"8388608", + "name":"innodb_log_buffer_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"262144", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_log_buffer_size", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{Global}", + "id":"1353", + "unit":"NULL", + "description":"The size in bytes of the buffer that InnoDBuses to write to the logfiles on disk. The default value changed from 8MB to16MB in 5.7.6 with the introduction of 32k and 64kinnodb_page_size values. Alarge log bufferenables largetransactions to runwithout a need to write the log to disk before thetransactions commit. Thusif you have transactions that update insert or delete manyrows making the log buffer larger saves disk I/O. For generalI/O tuning advice seeSection 8.5.8 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"innodb", + "name":"innodb_log_checksum_algorithm", + "deprecated":"t", + "valid_vals":"innodb,crc32,none,strict_innodb,strict_crc32,strict_none", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_log_checksum_algorithm", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"1354", + "unit":"NULL", + "description":"This configuration option was removed in MySQL 5.7.9 andreplaced by innodb_log_checksums.Specifies how to generate and verify thechecksum stored in eachredo log disk block.innodb_log_checksum_algorithm supports samealgorithms as innodb_checksum_algorithm.Previously only the innodb algorithm wassupported for redo log disk blocks.innodb_log_checksum_algorithm=innodb is thedefault setting.The strict_* forms work the same asinnodb crc32 andnone except that InnoDBhalts if it encounters a mix of checksum values in the sameredo log. You can only use these options in a completely newinstance. The strict_* settings aresomewhat faster because they do not need to compute both newand old checksum values to accept both during disk reads.The following table illustrates the difference between thenone innodb andcrc32 option values and theirstrict_ counterparts.none innodb andcrc32 write the specified type checksumvalue into each data block but for compatibility accept anyof the other checksum values when verifying a block during aread operation. The strict_ form of eachparameter only recognizes one kind of checksum which makesverification faster but requires that allInnoDB redo logs in an instance be createdunder the identicalinnodb_log_checksum_algorithm value." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"ON", + "name":"innodb_log_checksums", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_log_checksums", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1355", + "unit":"NULL", + "description":"Enables or disables checksums for redo log pages.innodb_log_checksums replacesinnodb_log_checksum_algorithmwhich was removed in MySQL 5.7.9.innodb_log_checksums=ON enables theCRC-32C checksum algorithm for redo logpages. When innodb_log_checksums isdisabled the contents of the redo log page checksum field areignored.Checksums on the redo log header page and redo log checkpointpages are never disabled." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"ON", + "name":"innodb_log_compressed_pages", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_log_compressed_pages", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1356", + "unit":"NULL", + "description":"Specifies whether images ofre-compressedpages are stored inInnoDB redologs." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"2", + "name":"innodb_log_files_in_group", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"2", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_log_files_in_group", + "vartype":"integer", + "max_value":"100", + "scope":"{Global}", + "id":"1358", + "unit":"NULL", + "description":"The number of log filesin the log group.InnoDB writes to the files in a circularfashion. The default (and recommended) value is 2. Thelocation of these files is specified byinnodb_log_group_home_dir.The combined size of log files(innodb_log_file_size *innodb_log_files_in_group) can be up to512GB." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"innodb_log_group_home_dir", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_log_group_home_dir", + "vartype":"directory name", + "max_value":"NULL", + "scope":"{Global}", + "id":"1359", + "unit":"NULL", + "description":"The directory path to the InnoDBredo log files whosenumber is specified byinnodb_log_files_in_group. Ifyou do not specify any InnoDB logvariables the default is to create two files namedib_logfile0 andib_logfile1 in the MySQL data directory.Their size is given by the size of theinnodb_log_file_size systemvariable." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"8192", + "name":"innodb_log_write_ahead_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"512", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_log_write_ahead_size", + "vartype":"integer", + "max_value":"16384", + "scope":"{Global}", + "id":"1360", + "unit":"NULL", + "description":"The write-ahead block size for the redo log in bytes. Toavoid read-on-write setinnodb_log_write_ahead_size to match theoperating system or file system cache block size.Read-on-write occurs when redo log blocks are not entirelycached to the operating system or file system due to amismatch between write-ahead block size for redo logs andoperating system or file system cache block size.Valid values forinnodb_log_write_ahead_size are multiplesof the InnoDB log file block size (2^n).The minimum value is the InnoDB log fileblock size (512). Write-ahead does not occur when the minimumvalue is specified. The maximum value is equal toinnodb_page_size. If youspecify a value forinnodb_log_write_ahead_size that is largerthan the innodb_page_sizevalue the innodb_log_write_ahead_sizevalue is truncated to theinnodb_page_size value.Setting the innodb_log_write_ahead_sizevalue too low in relation to the operating system or filesystem cache block size will result inread-on-write. Setting the value too high mayhave a slight impact on fsync performancefor log file writes due to several blocks being written atonce." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1024", + "name":"innodb_lru_scan_depth", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"100", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_lru_scan_depth", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"1361", + "unit":"NULL", + "description":"A parameter that influences the algorithms and heuristics forthe flush operation for theInnoDBbuffer pool. Primarilyof interest to performance experts tuning I/O-intensiveworkloads. It specifies per buffer pool instance how fardown the buffer pool LRU list thepage_cleaner thread scans looking fordirty pages to flush.This is a background operation performed once a second. If youhave spare I/O capacity under a typical workload increase thevalue. If a write-intensive workload saturates your I/Ocapacity decrease the value especially if you have a largebuffer pool. For general I/O tuning advice seeSection 8.5.8 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"75", + "name":"innodb_max_dirty_pages_pct", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_max_dirty_pages_pct", + "vartype":"numeric", + "max_value":"99", + "scope":"{Global}", + "id":"1362", + "unit":"NULL", + "description":"InnoDB tries toflush data from thebuffer pool so thatthe percentage of dirtypages does not exceed this value. The default value is75Theinnodb_max_dirty_pages_pctsetting establishes a target for flushing activity. It doesnot affect the rate of flushing. For information aboutmanaging the rate of flushing seeSection 14.4.3.2 Configuring the Rate of InnoDB Buffer Pool Flushing.For additional information about this variable seeSection 14.4.3.6 Tuning InnoDB Buffer Pool Flushing. For generalI/O tuning advice seeSection 8.5.8 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"innodb_max_dirty_pages_pct_lwm", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_max_dirty_pages_pct_lwm", + "vartype":"numeric", + "max_value":"99", + "scope":"{Global}", + "id":"1363", + "unit":"NULL", + "description":"Low water mark representing percentage ofdirty pages wherepreflushing is enabled to control the dirty page ratio. Thedefault of 0 disables the pre-flushing behavior entirely. Foradditional information about this variable seeSection 14.4.3.6 Tuning InnoDB Buffer Pool Flushing." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"innodb_max_purge_lag", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_max_purge_lag", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{Global}", + "id":"1364", + "unit":"NULL", + "description":"This variable controls how to delayINSERTUPDATE andDELETE operations whenpurge operations are lagging(see Section 14.2.2 InnoDB Multi-Versioning). The defaultvalue is 0 (no delays).The InnoDB transaction system maintains alist of transactions that have index records delete-marked byUPDATE orDELETE operations. The lengthof this list represents thepurge_lag value. Whenpurge_lag exceedsinnodb_max_purge_lag eachINSERTUPDATE andDELETE operation is delayed.To prevent excessive delays in extreme situations wherepurge_lag becomes huge you can puta cap on the amount of delay by setting theinnodb_max_purge_lag_delayconfiguration option. The delay is computed at the beginningof a purge batch.A typical setting for a problematic workload might be 1million assuming that transactions are small only 100 bytesin size and it is permissible to have 100MB of unpurgedInnoDB table rows.The lag value is displayed as the history list length in theTRANSACTIONS section of InnoDB Monitoroutput. For example if the output includes the followinglines the lag value is 20:For general I/O tuning advice seeSection 8.5.8 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"128", + "name":"innodb_rollback_segments", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_rollback_segments", + "vartype":"integer", + "max_value":"128", + "scope":"{Global}", + "id":"1391", + "unit":"NULL", + "description":"Defines how many of therollback segmentsin the systemtablespace are used for InnoDBtransactions. Thissetting while still valid is replaced byinnodb_undo_logs." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"innodb_max_purge_lag_delay", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_max_purge_lag_delay", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"1365", + "unit":"NULL", + "description":"Specifies the maximum delay in milliseconds for the delayimposed by theinnodb_max_purge_lagconfiguration option. Any non-zero value represents an upperlimit on the delay period computed from the formula based onthe value of innodb_max_purge_lag. Thedefault of zero means that there is no upper limit imposed onthe delay interval.For general I/O tuning advice seeSection 8.5.8 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1073741824", + "name":"innodb_max_undo_log_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"10485760", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_max_undo_log_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"1366", + "unit":"NULL", + "description":"innodb_max_undo_log_size defines athreshold size for undo tablespaces. If an undo tablespaceexceeds the threshold it can be marked for truncation wheninnodb_undo_log_truncate isenabled. The default value is 1024 MiB (1073741824 bytes).For more information seeSection 14.5.8 Truncating Undo Logs That Reside in Undo Tablespaces." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"50", + "name":"innodb_merge_threshold_set_all_debug", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_merge_threshold_set_all_debug", + "vartype":"integer", + "max_value":"50", + "scope":"{Global}", + "id":"1367", + "unit":"NULL", + "description":"Overrides the current MERGE_THRESHOLDsetting with the specified value for all indexes that arecurrently in the dictionary cache. This option is onlyavailable if debugging support is compiled in using theWITH_DEBUGCMake option. For related information seeSection 14.4.12 Configuring the Merge Threshold for Index Pages." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"innodb_monitor_disable", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_monitor_disable", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"1368", + "unit":"NULL", + "description":"Turns off one or morecounters in theINFORMATION_SCHEMA.INNODB_METRICStable. For usage information seeSection 21.31.20 The INFORMATION_SCHEMA INNODB_METRICS Table.As of MySQL 5.7.8innodb_monitor_disable='latch' disablesstatistics collection forSHOW ENGINEINNODB MUTEX. For more information seeSection 13.7.5.15 SHOW ENGINE Syntax." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"innodb_monitor_enable", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_monitor_enable", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"1369", + "unit":"NULL", + "description":"Turns on one or morecounters in theINFORMATION_SCHEMA.INNODB_METRICStable. For usage information seeSection 21.31.20 The INFORMATION_SCHEMA INNODB_METRICS Table.As of MySQL 5.7.8innodb_monitor_enable='latch' enablesstatistics collection forSHOW ENGINEINNODB MUTEX. For more information seeSection 13.7.5.15 SHOW ENGINE Syntax." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"innodb_monitor_reset", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_monitor_reset", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"1370", + "unit":"NULL", + "description":"Resets to zero the count value for one or morecounters in theINFORMATION_SCHEMA.INNODB_METRICStable. For usage information seeSection 21.31.20 The INFORMATION_SCHEMA INNODB_METRICS Table.As of MySQL 5.7.8innodb_monitor_reset='latch' resetsstatistics reported bySHOW ENGINEINNODB MUTEX. For more information seeSection 13.7.5.15 SHOW ENGINE Syntax." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"EMPTY", + "name":"innodb_monitor_reset_all", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_monitor_reset_all", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"1371", + "unit":"NULL", + "description":"Resets all values (minimum maximum and so on) for one ormore counters in theINFORMATION_SCHEMA.INNODB_METRICStable. For usage information seeSection 21.31.20 The INFORMATION_SCHEMA INNODB_METRICS Table." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_numa_interleave", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_numa_interleave", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1372", + "unit":"NULL", + "description":"Enables the NUMA interleave memory policy for allocation ofthe InnoDB buffer pool. Wheninnodb_numa_interleave is enabled the NUMAmemory policy is set to MPOL_INTERLEAVE forthe mysqld process. After theInnoDB buffer pool is allocated the NUMAmemory policy is set back to MPOL_DEFAULT.For the innodb_numa_interleave option to beavailable MySQL must be compiled on a NUMA-enabled system." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"37", + "name":"innodb_old_blocks_pct", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"5", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_old_blocks_pct", + "vartype":"integer", + "max_value":"95", + "scope":"{Global}", + "id":"1373", + "unit":"NULL", + "description":"Specifies the approximate percentage of theInnoDBbuffer pool used forthe old block sublist. Therange of values is 5 to 95. The default value is 37 (that is3/8 of the pool). Often used in combination withinnodb_old_blocks_time. SeeSection 14.4.3.3 Making the Buffer Pool Scan Resistant formore information. See Section 8.10.1 The InnoDB Buffer Pool forinformation about buffer pool management such as theLRU algorithm andeviction policies." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1000", + "name":"innodb_old_blocks_time", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_old_blocks_time", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{Global}", + "id":"1374", + "unit":"NULL", + "description":"Non-zero values protect against thebuffer pool beingfilled up by data that is referenced only for a brief periodsuch as during a fulltable scan. Increasing this value offers moreprotection against full table scans interfering with datacached in the buffer pool.Specifies how long in milliseconds (ms) a block inserted intothe old sublist must staythere after its first access before it can be moved to the newsublist. If the value is 0 a block inserted into the oldsublist moves immediately to the new sublist the first time itis accessed no matter how soon after insertion the accessoccurs. If the value is greater than 0 blocks remain in theold sublist until an access occurs at least that many ms afterthe first access. For example a value of 1000 causes blocksto stay in the old sublist for 1 second after the first accessbefore they become eligible to move to the new sublist.The default value is 1000.This variable is often used in combination withinnodb_old_blocks_pct. SeeSection 14.4.3.3 Making the Buffer Pool Scan Resistant formore information. See Section 8.10.1 The InnoDB Buffer Pool forinformation about buffer pool management such as theLRU algorithm andeviction policies." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"134217728", + "name":"innodb_online_alter_log_max_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"65536", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_online_alter_log_max_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"1375", + "unit":"NULL", + "description":"Specifies an upper limit on the size of the temporary logfiles used during onlineDDL operations for InnoDB tables.There is one such log file for each index being created ortable being altered. This log file stores data insertedupdated or deleted in the table during the DDL operation. Thetemporary log file is extended when needed by the value ofinnodb_sort_buffer_size upto the maximum specified byinnodb_online_alter_log_max_size. If anytemporary log file exceeds the upper size limit theALTER TABLE operation fails andall uncommitted concurrent DML operations are rolled back.Thus a large value for this option allows more DML to happenduring an online DDL operation but also causes a longerperiod at the end of the DDL operation when the table islocked to apply the data from the log." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"-1", + "name":"innodb_open_files", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"10", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_open_files", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{Global}", + "id":"1376", + "unit":"NULL", + "description":"This variable is relevant only if you use multipleInnoDBtablespaces. Itspecifies the maximum number of.ibdfiles that MySQL can keep open at one time. The minimumvalue is 10. The default value is 300 ifinnodb_file_per_table is notenabled and the higher of 300 andtable_open_cache otherwise.The file descriptors used for .ibd filesare for InnoDB tables only. They areindependent of those specified by the--open-files-limit serveroption and do not affect the operation of the table cache.For general I/O tuning advice seeSection 8.5.8 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_optimize_fulltext_only", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_optimize_fulltext_only", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1377", + "unit":"NULL", + "description":"Changes the way the OPTIMIZETABLE statement operates onInnoDB tables. Intended to be enabledtemporarily during maintenance operations forInnoDB tables withFULLTEXT indexes.By default OPTIMIZE TABLE reorganizes thedata in the clusteredindex of the table. When this option is enabledOPTIMIZE TABLE skips this reorganization ofthe table data and instead processes the newly addeddeleted and updated token data for aFULLTEXT index SeeSection 14.2.6.3 InnoDB FULLTEXT Indexes for more informationabout FULLTEXT indexes forInnoDB tables." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_optimize_point_storage", + "deprecated":"t", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_optimize_point_storage", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Session}", + "id":"1378", + "unit":"NULL", + "description":"Enable this variable before creating a column of typePOINT to store the POINTdata type internally as variable-lengthBLOB data.This variable was removed in MySQL 5.7.6." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1", + "name":"innodb_page_cleaners", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_page_cleaners", + "vartype":"integer", + "max_value":"64", + "scope":"{Global}", + "id":"1379", + "unit":"NULL", + "description":"The number of page cleaner threads that flush dirty pages frombuffer pool instances. The page cleaner threads perform flushlist and LRU flushing. A single page cleaner thread wasintroduced in MySQL 5.6.2 to offload buffer pool flushing workfrom the InnoDB master thread. As of MySQL5.7.4 InnoDB provides support for multiplepage cleaner threads. A value of 1 maintains the pre-MySQL5.7.4 configuration in which there is a single page cleanerthread. When there are multiple page cleaner threads bufferpool flushing tasks for each buffer pool instance aredispatched to idle page cleaner threads. Theinnodb_page_cleaners default value waschanged from 1 to 4 in MySQL 5.7.8. If the number of pagecleaner threads exceeds the number of buffer pool instancesinnodb_page_cleaners is automatically setto the same value asinnodb_buffer_pool_instances.If your workload is write-IO bound (when flushing dirty pagesfrom buffer pool instances to data files) and if your systemhardware has available capacity increasing the number of pagecleaner threads may help improve write-IO throughput.Multi-threaded page cleaner support is extended to shutdownand recovery phases in MySQL 5.7.5.As of MySQL 5.7.6 the setpriority() systemcall is used on Linux platforms (where it is supported andwhere the mysqld execution user isauthorized) to give page_cleaner threadspriority over other MySQL/InnoDB threads to help page flushingkeep pace with the current workload. mysqldexecution user authorization can be configured in/etc/security/limits.conf. For exampleif mysqld is run under themysql user you might authorize themysql user by adding lines similar to thefollowing to /etc/security/limits.conf:Refer to your Linux operating system documentation for moreinformation." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"16384", + "name":"innodb_page_size", + "deprecated":"f", + "valid_vals":"4k,8k,16k,4096,8192,16384", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_page_size", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"1380", + "unit":"NULL", + "description":"Specifies the page sizefor all InnoDBtablespaces in a MySQLinstance. This value isset when the instance is created and remains constantafterwards. You can specify page size using the values 64k32k 16k (the default)8k or 4k.Alternatively you can specify page size in bytes (6553632768163848192 4096).The default page size of 16KB and larger is appropriate for awide range of workloadsparticularly for queries involving table scans and DMLoperations involving bulk updates. Smaller page sizes might bemore efficient for OLTPworkloads involving many small writes where contention can bean issue when a single page contains many rows. Smaller pagesmight also be efficient withSSD storage devices whichtypically use small block sizes. Keeping theInnoDB page size close to the storagedevice block size minimizes the amount of unchanged data thatis rewritten to disk.The minimum file size for the first system tablespace datafile (ibdata1) differs depending on theinnodb_page_size value. Seethe innodb_data_file_pathoption description for more information.For general I/O tuning advice seeSection 8.5.8 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"innodb_saved_page_number_debug", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_saved_page_number_debug", + "vartype":"integer", + "max_value":"8388607", + "scope":"{Global}", + "id":"1392", + "unit":"NULL", + "description":"Saves a page number. Setting theinnodb_fil_make_page_dirty_debugoption dirties the page defined byinnodb_saved_page_number_debug. Theinnodb_saved_page_number_debug option isonly available if debugging support is compiled in using theWITH_DEBUGCMake option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"ON", + "name":"innodb_use_sys_malloc", + "deprecated":"t", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_use_sys_malloc", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1421", + "unit":"NULL", + "description":"Whether InnoDB uses the operating systemmemory allocator (ON) or its own(OFF). The default value isON. SeeSection 14.4.4 Configuring the Memory Allocator for InnoDB for moreinformation.innodb_use_sys_malloc wasdeprecated in MySQL 5.6.3 and removed in MySQL 5.7.4." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_print_all_deadlocks", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_print_all_deadlocks", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1381", + "unit":"NULL", + "description":"When this option is enabled information about alldeadlocks inInnoDB user transactions is recorded in themysqld errorlog. Otherwise you see information about only the lastdeadlock using the SHOW ENGINE INNODBSTATUS command. An occasionalInnoDB deadlock is not necessarily anissue because InnoDB detects the conditionimmediately and rolls back one of the transactionsautomatically. You might use this option to troubleshoot whydeadlocks are happening if an application does not haveappropriate error-handling logic to detect the rollback andretry its operation. A large number of deadlocks mightindicate the need to restructure transactions that issueDML or SELECT ... FORUPDATE statements for multiple tables so that eachtransaction accesses the tables in the same order thusavoiding the deadlock condition." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"300", + "name":"innodb_purge_batch_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_purge_batch_size", + "vartype":"integer", + "max_value":"5000", + "scope":"{Global}", + "id":"1382", + "unit":"NULL", + "description":"The granularity of changes expressed in units ofredo log records thattrigger a purge operationflushing the changed bufferpool blocks to disk. This option is intended for tuningperformance in combination with the settinginnodb_purge_threads=nand typical users do not need to modify it." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1", + "name":"innodb_purge_threads", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_purge_threads", + "vartype":"integer", + "max_value":"32", + "scope":"{Global}", + "id":"1383", + "unit":"NULL", + "description":"The number of background threads devoted to the InnoDBpurge operation. A minimumvalue of 1 signifies that the purge operation is alwaysperformed by background threads never as part of themaster thread.Running the purge operation in one or more background threadshelps reduce internal contention within InnoDB improvingscalability. Increasing the value to greater than 1 createsthat many separate purge threads which can improve efficiencyon systems where DMLoperations are performed on multiple tables. The maximum is32The innodb_purge_threads default value waschanged from 1 to 4 in MySQL 5.7.8." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"128", + "name":"innodb_purge_rseg_truncate_frequency", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_purge_rseg_truncate_frequency", + "vartype":"integer", + "max_value":"128", + "scope":"{Global}", + "id":"1384", + "unit":"NULL", + "description":"innodb_purge_rseg_truncate_frequencydefines the frequency with which the purge system freesrollback segments. An undo tablespace cannot be truncateduntil its rollback segments are freed. Normally the purgesystem frees rollback segments once every 128 times that purgeis invoked. Reducing theinnodb_purge_rseg_truncate_frequency valueincreases the frequency with which the purge thread freesrollback segments. The default value is 128.innodb_purge_rseg_truncate_frequency isintended for use withinnodb_undo_log_truncate. Formore information seeSection 14.5.8 Truncating Undo Logs That Reside in Undo Tablespaces." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_random_read_ahead", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_random_read_ahead", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1385", + "unit":"NULL", + "description":"Enables the randomread-ahead techniquefor optimizing InnoDB I/O.See Section 14.4.3.1 Configuring InnoDB Buffer Pool Prefetching (Read-Ahead) fordetails about the performance considerations for the differenttypes of read-ahead requests. For general I/O tuning advicesee Section 8.5.8 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"56", + "name":"innodb_read_ahead_threshold", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_read_ahead_threshold", + "vartype":"integer", + "max_value":"64", + "scope":"{Global}", + "id":"1386", + "unit":"NULL", + "description":"Controls the sensitivity of linearread-ahead thatInnoDB uses to prefetch pages into thebuffer pool. IfInnoDB reads at leastinnodb_read_ahead_threshold pagessequentially from an extent(64 pages) it initiates an asynchronous read for the entirefollowing extent. The permissible range of values is 0 to 64.A value of 0 disables read-ahead. For the default of 56InnoDB must read at least 56 pagessequentially from an extent to initiate an asynchronous readfor the following extent.Knowing how many pages are read through this read-aheadmechanism and how many of them are evicted from the bufferpool without ever being accessed can be useful to helpfine-tune theinnodb_read_ahead_thresholdparameter. As of MySQL 5.5SHOW ENGINEINNODB STATUS output displays counter informationfrom theInnodb_buffer_pool_read_aheadandInnodb_buffer_pool_read_ahead_evictedglobal status variables. These variables indicate the numberof pages brought into thebuffer pool byread-ahead requests and the number of such pagesevicted from the bufferpool without ever being accessed respectively. These countersprovide global values since the last server restart.SHOW ENGINE INNODB STATUS also shows therate at which the read-ahead pages are read in and the rate atwhich such pages are evicted without being accessed. Theper-second averages are based on the statistics collectedsince the last invocation of SHOW ENGINE INNODBSTATUS and are displayed in the BUFFER POOLAND MEMORY section of the output.See Section 14.4.3.1 Configuring InnoDB Buffer Pool Prefetching (Read-Ahead) for moreinformation. For general I/O tuning advice seeSection 8.5.8 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"4", + "name":"innodb_read_io_threads", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_read_io_threads", + "vartype":"integer", + "max_value":"64", + "scope":"{Global}", + "id":"1387", + "unit":"NULL", + "description":"The number of I/O threads for read operations inInnoDB. The default value is 4. Itscounterpart for write threads isinnodb_write_io_threads. SeeSection 14.4.7 Configuring the Number of Background InnoDB I/O Threads formore information. For general I/O tuning advice seeSection 8.5.8 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_read_only", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_read_only", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1388", + "unit":"NULL", + "description":"Starts the server in read-only mode. For distributing databaseapplications or data sets on read-only media. Can also be usedin data warehouses to share the same data directory betweenmultiple instances. SeeSection 14.4.2 Configuring InnoDB for Read-Only Operation for usageinstructions." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"innodb_replication_delay", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_replication_delay", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{Global}", + "id":"1389", + "unit":"NULL", + "description":"The replication thread delay (in ms) on a slave server ifinnodb_thread_concurrency isreached." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_rollback_on_timeout", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_rollback_on_timeout", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1390", + "unit":"NULL", + "description":"In MySQL 5.7 InnoDBrolls back only the laststatement on a transaction timeout by default. If--innodb_rollback_on_timeout isspecified a transaction timeout causesInnoDB to abort and roll back the entiretransaction." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1048576", + "name":"innodb_sort_buffer_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"65536", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_sort_buffer_size", + "vartype":"integer", + "max_value":"67108864", + "scope":"{Global}", + "id":"1393", + "unit":"NULL", + "description":"Specifies the size of sort buffers used for sorting dataduring creation of an InnoDB index. Thesize specified defines the amount of data filled in memory foran internal sort and written out to disk which can bereferred to as a run. During the merge phasepairs of buffers of the specified size are readin and merged. The larger the setting the fewerruns and merges there are which is importantto understand from a tuning perspective.This sort area is only used for merge sorts during indexcreation not during later index maintenance operations.Buffers are deallocated when index creation completes.The value of this option also controls the amount by which thetemporary log file is extended to record concurrent DMLduring online DDLoperations.Before this setting was made configurable the size washardcoded to 1048576 bytes (1MB) and that value remains thedefault.During an ALTER TABLE orCREATE TABLE statement thatcreates an index 3 buffers are allocated each with a sizedefined by this option. Additionally auxiliary pointers areallocated to rows in the sort buffer so that the sort can runon pointers (as opposed to moving rows during the sortoperation).For a typical sort operation a formula such as this can beused to estimate memory consumption:@@global.innodb_sort_buffer_size/dict_index_get_min_size(index)indicates the maximum tuples held. 2 *(@@global.innodb_sort_buffer_size/*dict_index_get_min_size(index)*/)* 8 /*64-bit size of *buf->tuples*/indicates auxiliary pointers allocated.For parallel sorts on a full-text index multiply by theinnodb_ft_sort_pll_degreesetting:" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"6", + "name":"innodb_spin_wait_delay", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_spin_wait_delay", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{Global}", + "id":"1394", + "unit":"NULL", + "description":"The maximum delay between polls for aspin lock. The low-levelimplementation of this mechanism varies depending on thecombination of hardware and operating system so the delaydoes not correspond to a fixed time interval. The defaultvalue is 6. SeeSection 14.4.9 Configuring Spin Lock Polling formore information." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"ON", + "name":"innodb_stats_auto_recalc", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_stats_auto_recalc", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1395", + "unit":"NULL", + "description":"Causes InnoDB to automatically recalculatepersistentstatistics after the data in a table is changedsubstantially. The threshold value is currently 10% of therows in the table. This setting applies to tables created whenthe innodb_stats_persistentoption is enabled or where the clauseSTATS_PERSISTENT=1 is enabled by aCREATE TABLE orALTER TABLE statement. Theamount of data sampled to produce the statistics is controlledby theinnodb_stats_persistent_sample_pagesconfiguration option.For additional information aboutinnodb_stats_auto_recalc seeSection 14.4.11.1 Configuring Persistent Optimizer Statistics Parameters." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"nulls_equal", + "name":"innodb_stats_method", + "deprecated":"f", + "valid_vals":"nulls_equal,nulls_unequal,nulls_ignored", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_stats_method", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{Global}", + "id":"1396", + "unit":"NULL", + "description":"How the server treats NULL values whencollecting statisticsabout the distribution of index values forInnoDB tables. This variable has threepossible values nulls_equalnulls_unequal andnulls_ignored. Fornulls_equal all NULLindex values are considered equal and form a single valuegroup that has a size equal to the number ofNULL values. Fornulls_unequal NULLvalues are considered unequal and eachNULL forms a distinct value group of size1. For nulls_ignoredNULL values are ignored.The method that is used for generating table statisticsinfluences how the optimizer chooses indexes for queryexecution as described in Section 8.3.7 InnoDB and MyISAM Index Statistics Collection." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_stats_on_metadata", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_stats_on_metadata", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1397", + "unit":"NULL", + "description":"When this variable is enabled InnoDBupdates statistics whenmetadata statements such as SHOW TABLESTATUS or when accessing theINFORMATION_SCHEMA.TABLES orINFORMATION_SCHEMA.STATISTICStables. (These updates are similar to what happens forANALYZE TABLE.) When disabledInnoDB does not update statistics duringthese operations. Leaving this setting disabled can improveaccess speed for schemas that have a large number of tables orindexes. It can also improve the stability ofexecutionplans for queries that involveInnoDB tables.To change the setting issue the statement SET GLOBALinnodb_stats_on_metadata=modewhere mode iseither ON or OFF (or1 or 0). Changing thissetting requires the SUPER privilege andimmediately affects the operation of all connections.This variable is disabled by default." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"ON", + "name":"innodb_stats_persistent", + "deprecated":"f", + "valid_vals":"OFF,ON,0,1", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_stats_persistent", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1398", + "unit":"NULL", + "description":"Specifies whether InnoDB index statisticsare persisted to disk. Otherwise statistics may berecalculated frequently which can lead to variations inquery executionplans. This setting is stored with each table when thetable is created. You can setinnodb_stats_persistent at the global levelbefore creating a table or use theSTATS_PERSISTENT clause of theCREATE TABLE andALTER TABLE statements tooverride the system-wide setting and configure persistentstatistics for individual tables.For more information about this option seeSection 14.4.11.1 Configuring Persistent Optimizer Statistics Parameters." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"20", + "name":"innodb_stats_persistent_sample_pages", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_stats_persistent_sample_pages", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"1399", + "unit":"NULL", + "description":"The number of index pages tosample when estimatingcardinality and otherstatistics for anindexed column such as those calculated byANALYZE TABLE. Increasing thevalue improves the accuracy of index statistics which canimprove the queryexecution plan at the expense of increased I/O duringthe execution of ANALYZE TABLEfor an InnoDB table. For additionalinformation see Section 14.4.11.1 Configuring Persistent Optimizer Statistics Parameters.This option only applies when theinnodb_stats_persistentsetting is turned on for a table; when that option is turnedoff for a table theinnodb_stats_transient_sample_pagessetting applies instead." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"", + "dangerous":"NO", + "default_val":"0.1", + "name":"cursor_tuple_fraction", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the planner's estimate of the fraction of a cursor's rows that will be retrieved.", + "vartype":"real", + "max_value":"1", + "scope":"{GlobalSession}", + "id":"1495", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"8", + "name":"innodb_stats_transient_sample_pages", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_stats_transient_sample_pages", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"1401", + "unit":"NULL", + "description":"The number of index pages tosample when estimatingcardinality and otherstatistics for anindexed column such as those calculated byANALYZE TABLE. The defaultvalue is 8. Increasing the value improves the accuracy ofindex statistics which can improve thequery executionplan at the expense of increased I/O when opening anInnoDB table or recalculating statistics.For additional information seeSection 14.4.11.2 Configuring Non-Persistent Optimizer Statistics Parameters.This option only applies when theinnodb_stats_persistentsetting is turned off for a table; when this option is turnedon for a table theinnodb_stats_persistent_sample_pagessetting applies instead. Takes the place of theinnodb_stats_sample_pages option. SeeSection 14.4.11.2 Configuring Non-Persistent Optimizer Statistics Parameters for moreinformation." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_status_output", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_status_output", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1402", + "unit":"NULL", + "description":"Enables or disables periodic output for the standardInnoDB Monitor. Also used in combinationwithinnodb_status_output_locks toenable or disable periodic output for theInnoDB Lock Monitor. SeeSection 14.15 InnoDB Monitors for additional information." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_status_output_locks", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_status_output_locks", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1403", + "unit":"NULL", + "description":"Enables or disables the InnoDB LockMonitor. When enabled the InnoDB LockMonitor prints additional information about locks inSHOW ENGINE INNODB STATUS output and inperiodic output printed to the MySQL error log. Periodicoutput for the InnoDB Lock Monitor isprinted as part of the standard InnoDBMonitor output. The standard InnoDB Monitormust therefore be enabled for the InnoDBLock Monitor to print data to the MySQL error logperiodically. See Section 14.15 InnoDB Monitors for moreinformation." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_strict_mode", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_strict_mode", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1404", + "unit":"NULL", + "description":"When innodb_strict_mode isON InnoDB returnserrors rather than warnings for certain conditions. As ofMySQL 5.7.7 the default value is ON.Strict mode helpsguard against ignored typos and syntax errors in SQL or otherunintended consequences of various combinations of operationalmodes and SQL statements. Wheninnodb_strict_mode isON InnoDB raises errorconditions in certain cases rather than issuing a warning andprocessing the specified statement (perhaps with unintendedbehavior). This is analogous tosql_mode inMySQL which controls what SQL syntax MySQL accepts anddetermines whether it silently ignores errors or validatesinput syntax and data values.The innodb_strict_mode setting affects thehandling of syntax errors for CREATETABLE ALTER TABLECREATE INDEX andOPTIMIZE TABLE statements.innodb_strict_mode also enables a recordsize check so that an INSERT orUPDATE never fails due to the record beingtoo large for the selected page size.Oracle recommends enablinginnodb_strict_mode when usingROW_FORMAT andKEY_BLOCK_SIZE clauses onCREATE TABLEALTER TABLE andCREATE INDEX statements. Wheninnodb_strict_mode isOFF InnoDB ignoresconflicting clauses and creates the table or index with onlya warning in the message log. The resulting table might havedifferent behavior than you intended such as having nocompression when you tried to create a compressed table. Wheninnodb_strict_mode isON such problems generate an immediateerror and the table or index is not created avoiding atroubleshooting session later.You can turn innodb_strict_modeON or OFF on the commandline when you start mysqld or in theconfigurationfile my.cnf ormy.ini. You can also enable or disableinnodb_strict_mode at runtime with thestatement SET [GLOBAL|SESSION]innodb_strict_mode=modewhere mode iseither ON or OFF.Changing the GLOBAL setting requires theSUPER privilege and affects the operationof all clients that subsequently connect. Any client canchange the SESSION setting forinnodb_strict_mode and the setting affectsonly that client.innodb_strict_mode is notapplicable to general tablespaces. Tablespace management rulesfor general tablespaces are strictly enforced independently ofinnodb_strict_mode. For moreinformation see Section 13.1.19 CREATE TABLESPACE Syntax." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"TRUE", + "name":"innodb_support_xa", + "deprecated":"t", + "valid_vals":"TRUE,FALSE", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_support_xa", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1405", + "unit":"NULL", + "description":"Enables InnoDB support for two-phase commitin XA transactions causing anextra disk flush for transaction preparation. This setting isthe default. The XA mechanism is used internally and isessential for any server that has its binary log turned on andis accepting changes to its data from more than one thread. Ifyou turn it off transactions can be written to the binary login a different order from the one in which the live databaseis committing them. This can produce different data when thebinary log is replayed in disaster recovery or on areplication slave. Do not turn it off on a replication masterserver unless you have an unusual setup where only one threadis able to change data.innodb_support_xa is deprecated and will beremoved in a future MySQL release. InnoDBsupport for two-phase commit in XA transactions is alwaysenabled as of MySQL 5.7.10. Disablinginnodb_support_xa is nolonger permitted as it makes replication unsafe and preventsperformance gains associated with binary log group commit." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"1", + "name":"innodb_sync_array_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_sync_array_size", + "vartype":"integer", + "max_value":"1024", + "scope":"{Global}", + "id":"1406", + "unit":"NULL", + "description":"Splits an internal data structure used to coordinate threadsfor higher concurrency in workloads with large numbers ofwaiting threads. This setting must be configured when theMySQL instance is starting up and cannot be changedafterward. Increasing this option value is recommended forworkloads that frequently produce a large number of waitingthreads typically greater than 768." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"30", + "name":"innodb_sync_spin_loops", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_sync_spin_loops", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{Global}", + "id":"1407", + "unit":"NULL", + "description":"The number of times a thread waits for anInnoDB mutex to be freed before the threadis suspended. The default value is 30." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"innodb_sync_debug", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_sync_debug", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1408", + "unit":"NULL", + "description":"Enables sync debug checking for the InnoDBstorage engine. This option is only available if debuggingsupport is compiled in using theWITH_DEBUGCMake option.Prior to MySQL 5.7.8 enabling InnoDB syncdebug checking required that the Debug Sync facility beenabled using theENABLE_DEBUG_SYNCCMake option. This requirement was removedin MYSQL 5.7.8 with the introduction of theinnodb_sync_debug configuration option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"TRUE", + "name":"innodb_table_locks", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_table_locks", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1409", + "unit":"NULL", + "description":"If autocommit = 0InnoDB honors LOCKTABLES; MySQL does not return from LOCKTABLES ... WRITE until all other threads havereleased all their locks to the table. The default value ofinnodb_table_locks is 1which means that LOCK TABLEScauses InnoDB to lock a table internally ifautocommit = 0.In MySQL 5.7innodb_table_locks = 0 has noeffect for tables locked explicitly withLOCK TABLES ...WRITE. It does have an effect for tables locked forread or write byLOCK TABLES ...WRITE implicitly (for example through triggers) orby LOCK TABLES... READ." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ibtmp1:12M:autoextend", + "name":"innodb_temp_data_file_path", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_temp_data_file_path", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"1410", + "unit":"NULL", + "description":"Specifies the path file name and file size forInnoDB temporary table tablespace datafiles. The full directory path for a file is formed byconcatenatinginnodb_data_home_dir to thepath specified byinnodb_temp_data_file_path. File size isspecified in KB MB or GB (1024MB) by appendingK M orG to the size value. The sum of the sizesof the files must be slightly larger than 12MB. If you do notspecify innodb_temp_data_file_path thedefault behavior is to create a single auto-extendingtemporary table tablespace data file slightly larger than12MB named ibtmp1. The size limit ofindividual files is determined by your operating system. Youcan set the file size to more than 4GB on operating systemsthat support big files. Use of raw disk partitions fortemporary table tablespace data files is not supported.The name of a InnoDB temporary tabletablespace data file cannot be the same as the name of aInnoDB data file. Any inability or errorcreating a temporary table tablespace data file is treated asfatal and server startup will be refused. The temporary tabletablespace has a dynamically generated space ID which canchange on each server restart.The InnoDB temporary table tablespace isshared by all non-compressed InnoDBtemporary tables. Compressed InnoDBtemporary tables reside in per-table tablespace files whichare located in the temporary file directory defined bytmpdir.Metadata about active InnoDB temporarytables if found in theINFORMATION_SCHEMA.INNODB_TEMP_TABLE_INFO." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"NULL", + "name":"innodb_tmpdir", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_tmpdir", + "vartype":"directory name", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1411", + "unit":"NULL", + "description":"The innodb_tmpdir option is used to definean alternate directory for temporary sort files created duringonline ALTER TABLE operationsthat rebuild the table.Online ALTER TABLE operationsthat rebuild a table also create anintermediate table file in the samedirectory as the original table. Theinnodb_tmpdir option is not applicable tointermediate table files.A valid value is any directory path other than the MySQL datadirectory path. If the value is NULL (the default) temporaryfiles are created MySQL temporary directory(TMPDIR on Unix %TEMP%on Windows or the directory specified by the--tmpdir configurationoption). If an innodb_tmpdir directory isspecified existence of the directory and permissions are onlychecked when innodb_tmpdir is configuredusing aSETstatement. If a symlink is provided in a directory string thesymlink is resolved and stored as an absolute path. The pathshould not exceed 512 bytes. An onlineALTER TABLE operation reportsan error if innodb_tmpdir is set to aninvalid directory. innodb_tmpdir overridesthe MySQL tmpdir setting butonly for online ALTER TABLEoperations.The FILE privilege is required to configureinnodb_tmpdir.The innodb_tmpdir option was introduced tohelp avoid overflowing a temporary file directory located on atmpfs file system. Such overflows couldoccur as a result of large temporary sort files created duringonline ALTER TABLE operationsthat rebuild the table.In replication environments only consider replicating aninnodb_tmpdir setting if all servers havethe same operating system environment. Otherwise replicatingan innodb_tmpdir setting could result in areplication failure when running onlineALTER TABLE operations thatrebuild the table. If server operating environments differ itis recommended that you configureinnodb_tmpdir on each server individually.For related information seeWhere InnoDB Stores Temporary Files." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"innodb_thread_concurrency", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_thread_concurrency", + "vartype":"integer", + "max_value":"1000", + "scope":"{Global}", + "id":"1412", + "unit":"NULL", + "description":"InnoDB tries to keep the number ofoperating system threads concurrently insideInnoDB less than or equal to the limitgiven by this variable (InnoDB usesoperating system threads to process user transactions). Oncethe number of threads reaches this limit additional threadsare placed into a wait state within a First In FirstOut (FIFO) queue for execution. Threads waiting forlocks are not counted in the number of concurrently executingthreads.The range of this variable is 0 to 1000. A value of 0 (thedefault) is interpreted as infinite concurrency (noconcurrency checking). Disabling thread concurrency checkingenables InnoDB to create as many threads asit needs. A value of 0 also disables the queriesinside InnoDB and queries in queuecounters in the ROW OPERATIONSsection of SHOW ENGINE INNODB STATUSoutput.Consider setting this variable if your MySQL instance sharesCPU resources with other applications or if your workload ornumber of concurrent users is growing. The correct settingdepends on workload computing environment and the version ofMySQL that you are running. You will need to test a range ofvalues to determine the setting that provides the bestperformance. innodb_thread_concurrency is adynamic variable which allows you to experiment withdifferent settings on a live test system. If a particularsetting performs poorly you can quickly setinnodb_thread_concurrency back to 0.Use the following guidelines to help find and maintain anappropriate setting:For related information seeSection 14.4.6 Configuring Thread Concurrency for InnoDB." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"innodb_trx_purge_view_update_only_debug", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_trx_purge_view_update_only_debug", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1413", + "unit":"NULL", + "description":"Pauses purging of delete-marked records while allowing thepurge view to be updated. This option artificially creates asituation in which the purge view is updated but purges havenot yet been performed. This option is only available ifdebugging support is compiled in using theWITH_DEBUGCMake option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"innodb_trx_rseg_n_slots_debug", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_trx_rseg_n_slots_debug", + "vartype":"integer", + "max_value":"1024", + "scope":"{Global}", + "id":"1414", + "unit":"NULL", + "description":"Sets a debug flag that limitsTRX_RSEG_N_SLOTS to a given value for thetrx_rsegf_undo_find_free function whichlooks for a free slot for an undo log segment. This option isonly available if debugging support is compiled in using theWITH_DEBUGCMake option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"10000", + "name":"innodb_thread_sleep_delay", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_thread_sleep_delay", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"1415", + "unit":"NULL", + "description":"How long InnoDB threads sleep beforejoining the InnoDB queue in microseconds.The default value is 10000. A value of 0 disables sleep. InMySQL 5.6.3 and higher you can set the configuration optioninnodb_adaptive_max_sleep_delayto the highest value you would allow forinnodb_thread_sleep_delay and InnoDBautomatically adjustsinnodb_thread_sleep_delay up or downdepending on the current thread-scheduling activity. Thisdynamic adjustment helps the thread scheduling mechanism towork smoothly during times when the system is lightly loadedand when it is operating near full capacity.For more information seeSection 14.4.6 Configuring Thread Concurrency for InnoDB." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"USERDEFINED", + "name":"innodb_version", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"NULL", + "vartype":"string", + "max_value":"NULL", + "scope":"{NA}", + "id":"1422", + "unit":"NULL", + "description":"The InnoDB version number. In 5.7 theseparate numbering for InnoDB does notapply and this value is the same as for theversion variable." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"off", + "name":"data_checksums", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"f", + "rank":"-1", + "summary":"Shows whether data checksums are turned on for this cluster.", + "vartype":"bool", + "max_value":"", + "scope":"{NA}", + "id":"1496", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":".", + "name":"innodb_undo_directory", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_undo_directory", + "vartype":"directory name", + "max_value":"NULL", + "scope":"{Global}", + "id":"1416", + "unit":"NULL", + "description":"The path where InnoDB creates separatetablespaces for the undo logs. Typically used to place undologs on a different storage device. Used in conjunction withinnodb_undo_logs andinnodb_undo_tablespaceswhich determine the disk layout of the undo logs outside thesystemtablespace.Prior to MySQL 5.7.8 theinnodb_undo_directory default value is. which represents thesame directory where InnoDB creates itsother log files by default. As of MySQL 5.7.8 there is nodefault value (it is NULL). If a path is not specified undotablespaces are created in the MySQL data directory asdefined by datadir.For more information about configuring separate tablespacesfor undo logs see Section 14.5.7 Storing InnoDB Undo Logs in Separate Tablespaces." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"OFF", + "name":"innodb_undo_log_truncate", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_undo_log_truncate", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1417", + "unit":"NULL", + "description":"When you enable innodb_undo_log_truncateundo tablespaces that exceed the threshold value defined byinnodb_max_undo_log_size aremarked for truncation. Only undo logs that reside in undotablespaces can be truncated. Truncation of undo logs thatreside in the system tablespace is not supported. Fortruncation to occur there must be at least two undotablespaces and two redo-enabled undo logs configured to usethe undo tablespaces. This means thatinnodb_undo_tablespaces mustbe set to a value equal to or greater than 2 andinnodb_undo_logs must set toa value equal to or greater than 35.Theinnodb_purge_rseg_truncate_frequencyconfiguration option can be used to expedite truncation ofundo tablepaces.For more information seeSection 14.5.8 Truncating Undo Logs That Reside in Undo Tablespaces." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"128", + "name":"innodb_undo_logs", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for innodb_undo_logs", + "vartype":"integer", + "max_value":"128", + "scope":"{Global}", + "id":"1418", + "unit":"NULL", + "description":"Defines the number of undo logs (otherwise referred to asrollbacksegments) used by InnoDB. Theinnodb_undo_logs optionreplacesinnodb_rollback_segments.As of MySQL 5.7.2 32 undo logs are reserved for use bytemporary tables and are hosted in the temporary tabletablespace (ibtmp1). To allocateadditional undo logs for data-modifying transactions thatgenerate undo records innodb_undo_logsmust be set to a value greater than 32 if undo logs are storedin the system tablespace only. If you have configured separateundo tablespaces innodb_undo_logs must beset to a value greater than 33 to allocate additional undologs for data-modifying transactions. Each undo log can hostup to a maximum of 1024 transactions.Although you can increase or decrease the number of undo logsused by InnoDB the number of undo logsphysically present in the system never decreases. Thus youmight start with a low value for this parameter and graduallyincrease it to avoid allocating undo logs that are notrequired. If innodb_undo_logsis not set it defaults to the maximum value of 128. For thetotal number of available undo logs rather than the number ofactive ones see theInnodb_available_undo_logsstatus variable.For more information about undo logs seeSection 14.2.2 InnoDB Multi-Versioning. For informationabout configuring separate tablespaces for undo logs seeSection 14.5.7 Storing InnoDB Undo Logs in Separate Tablespaces." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"0", + "name":"innodb_undo_tablespaces", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_undo_tablespaces", + "vartype":"integer", + "max_value":"126", + "scope":"{Global}", + "id":"1419", + "unit":"NULL", + "description":"The number oftablespace files thatthe undo logs are dividedbetween. By default all undo logs are part of thesystemtablespace and the system tablespace always containsone undo tablespace in addition to those configured byinnodb_undo_tablespaces.Because undo logs can become large during long-runningtransactions having undo logs in multiple tablespaces reducesthe maximum size of any one tablespace. The undo tablespacefiles are created in the location defined byinnodb_undo_directory withnames in the form ofundoN whereN is a sequential series ofintegers (including leading zeros). The default size of anundo tablespace file is 10M. The number ofinnodb_undo_tablespaces mustbe set prior to initializing InnoDB.Attempting to restart InnoDB with a greaternumber of undo tablespaces than you specified when you firstcreated the MySQL instance will result in a failed start andan error stating that InnoDB did not findthe expected number of undo tablespaces.As MySQL 5.7.2 32 of 128 undo logs were reserved fortemporary tables as described inSection 14.2.5 InnoDB Temporary Table Undo Logs. One undolog is always allocated to the system tablespace which leaves95 undo logs available for undo tablepaces. This changeeffectively reduced theinnodb_undo_tablespacesmaximum limit from 126 to 95 and in MySQL 5.7.8 theinnodb_undo_tablespacesmaximum value was officially reduced to 95.For information about configuring separate tablespaces forundo logs see Section 14.5.7 Storing InnoDB Undo Logs in Separate Tablespaces." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"ON", + "name":"innodb_use_native_aio", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_use_native_aio", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1420", + "unit":"NULL", + "description":"Specifies whether to use the Linux asynchronous I/O subsystem.This variable applies to Linux systems only and cannot bechanged while the server is running. Normally you do not needto touch this option because it is enabled by default.As of MySQL 5.5 theasynchronous I/Ocapability that InnoDB has on Windowssystems is available on Linux systems. (Other Unix-likesystems continue to use synchronous I/O calls.) This featureimproves the scalability of heavily I/O-bound systems whichtypically show many pending reads/writes in the output of thecommand SHOW ENGINE INNODB STATUSG.Running with a large number of InnoDB I/Othreads and especially running multiple such instances on thesame server machine can exceed capacity limits on Linuxsystems. In this case you may receive the following error:You can typically address this error by writing a higher limitto /proc/sys/fs/aio-max-nr.However if a problem with the asynchronous I/O subsystem inthe OS prevents InnoDB from starting youcan start the server withinnodb_use_native_aio=0disabled (useinnodb_use_native_aio=0 inthe option file). This option may also be turned offautomatically during startup if InnoDBdetects a potential problem such as a combination oftmpdir location tmpfsfilesystem and Linux kernel that does not support AIO ontmpfs." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"/var/lib/postgresql/9.3/main", + "name":"data_directory", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"f", + "rank":"-1", + "summary":"Sets the server's data directory.", + "vartype":"string", + "max_value":"", + "scope":"{Global}", + "id":"1497", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"ISO MDY", + "name":"DateStyle", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the display format for date and time values.", + "vartype":"string", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1498", + "unit":"", + "description":"Also controls interpretation of ambiguous date inputs." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"{NULL}", + "dangerous":"NO", + "default_val":"4", + "name":"innodb_write_io_threads", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"f", + "rank":"-1", + "summary":"Options for innodb_write_io_threads", + "vartype":"integer", + "max_value":"64", + "scope":"{Global}", + "id":"1423", + "unit":"NULL", + "description":"The number of I/O threads for write operations inInnoDB. The default value is 4. Itscounterpart for read threads isinnodb_read_io_threads. SeeSection 14.4.7 Configuring the Number of Background InnoDB I/O Threads formore information. For general I/O tuning advice seeSection 8.5.8 Optimizing InnoDB Disk I/O.You should also take into consideration the value ofsync_binlog which controlssynchronization of the binary log to disk.For general I/O tuning advice seeSection 8.5.8 Optimizing InnoDB Disk I/O." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"auto_increment_increment", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for auto_increment_increment", + "vartype":"integer", + "max_value":"65535", + "scope":"{GlobalSession}", + "id":"1424", + "unit":"NULL", + "description":"auto_increment_incrementand auto_increment_offsetare intended for use with master-to-master replication andcan be used to control the operation ofAUTO_INCREMENT columns. Both variableshave global and session values and each can assume aninteger value between 1 and 65535 inclusive. Setting thevalue of either of these two variables to 0 causes its valueto be set to 1 instead. Attempting to set the value ofeither of these two variables to an integer greater than65535 or less than 0 causes its value to be set to 65535instead. Attempting to set the value ofauto_increment_increment orauto_increment_offset to anoninteger value produces an error and the actual value ofthe variable remains unchanged.These two variables affect AUTO_INCREMENTcolumn behavior as follows:If either of these variables is changed and then new rowsinserted into a table containing anAUTO_INCREMENT column the results mayseem counterintuitive because the series ofAUTO_INCREMENT values is calculatedwithout regard to any values already present in the columnand the next value inserted is the least value in the seriesthat is greater than the maximum existing value in theAUTO_INCREMENT column. The series iscalculated like this:auto_increment_offset +N auto_increment_incrementwhere N is a positive integervalue in the series [123 ...]. For example:The values shown forauto_increment_incrementand auto_increment_offsetgenerate the series 5 + N 10 that is [515253545 ...]. The highest valuepresent in the col column prior to theINSERT is 31 and the nextavailable value in the AUTO_INCREMENTseries is 35 so the inserted values forcol begin at that point and the resultsare as shown for the SELECTquery.It is not possible to restrict the effects of these twovariables to a single table; these variables control thebehavior of all AUTO_INCREMENT columns inall tables on the MySQL server. If theglobal value of either variable is set its effects persistuntil the global value is changed or overridden by settingthe session value or until mysqld isrestarted. If the local value is set the new value affectsAUTO_INCREMENT columns for all tablesinto which new rows are inserted by the current user for theduration of the session unless the values are changedduring that session.The default value ofauto_increment_increment is1. SeeSection 17.4.1.1 Replication and AUTO_INCREMENT." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"auto_increment_offset", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Options for auto_increment_offset", + "vartype":"integer", + "max_value":"65535", + "scope":"{Global,Session}", + "id":"1425", + "unit":"NULL", + "description":"This variable has a default value of 1. For moreinformation see the description forauto_increment_increment." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"NULL", + "name":"version_tokens_session", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for version_tokens_session", + "vartype":"string", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1426", + "unit":"NULL", + "description":"The session value of this variable specifies the clientversion token list and indicates the tokens that theclient session requires the server version token list tohave.If theversion_tokens_sessionvariable is NULL (the default) or hasan empty value any server version token list matches.(In effect an empty value disables matchingrequirements.)If theversion_tokens_sessionvariable has a nonempty value any mismatch between itsvalue and the server version token list results in anerror for any statement the session sends to the server.A mismatch occurs under these conditions:It is not a mismatch for the server version token listto include a token not named in theversion_tokens_sessionvalue.Suppose that a management application has set the servertoken list as follows:A client registers the tokens it requires the server tomatch by setting itsversion_tokens_sessionvalue. Then for each subsequent statement sent by theclient the server checks its token list against theclientversion_tokens_sessionvalue and produces an error if there is a mismatch:The first SELECT succeedsbecause the client tokens tok1 andtok2 are present in the server tokenlist and each token has the same value in the serverlist. The second SELECTfails because although tok1 ispresent in the server token list it has a differentvalue than specified by the client.At this point any statement sent by the client failsunless the server token list changes such that itmatches again. Suppose that the management applicationchanges the server token list as follows:Now the clientversion_tokens_sessionvalue matches the server token list and the client canonce again successfully execute statements:This variable was added in MySQL 5.7.8." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"version_tokens_session_number", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for version_tokens_session_number", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global,Session}", + "id":"1427", + "unit":"NULL", + "description":"This variable is for internal use.This variable was added in MySQL 5.7.8." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"rewriter_enabled", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for rewriter_enabled", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1428", + "unit":"NULL", + "description":"Whether the Rewriter query rewriteplugin is enabled." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"INTERNAL", + "name":"rewriter_verbose", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for rewriter_verbose", + "vartype":"integer", + "max_value":"NULL", + "scope":"{Global}", + "id":"1429", + "unit":"NULL", + "description":"For internal use." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"log-bin", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for log-bin", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"1430", + "unit":"NULL", + "description":"Enable binary logging. The server logs all statements thatchange data to the binary log which is used for backup andreplication. See Section 5.4.4 The Binary Log.The option value if given is the base name for the logsequence. The server creates binary log files in sequence byadding a numeric suffix to the base name. It is recommendedthat you specify a base name (see Section B.5.7 Known Issues in MySQLfor the reason). Otherwise MySQL useshost_name-binas the base name.When the server reads an entry from the index file itchecks whether the entry contains a relative path and if itdoes the relative part of the path in replaced with theabsolute path set using the --log-binoption. An absolute path remains unchanged; in such a casethe index must be edited manually to enable the new path orpaths to be used. (In older versions of MySQL manualintervention was required whenever relocating the binary logor relay log files.) (Bug #11745230 Bug #12133)Setting this option causes thelog_bin system variable tobe set to ON (or 1)and not to the base name. The binary log file name (withpath) is available as thelog_bin_basename systemvariable.In MySQL 5.7.3 and later if you specify this option withoutalso specifying a--server-id the server isnot allowed to start. (Bug #11763963 Bug #56739)" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"IGNORE_ERROR", + "name":"binlogging_impossible_mode", + "deprecated":"t", + "valid_vals":"IGNORE_ERROR,ABORT_SERVER", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for binlogging_impossible_mode", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1438", + "unit":"NULL", + "description":"This option is deprecated and will be removed in a futureMySQL release. Use the renamedbinlog_error_action tocontrol what happens when the server cannot write to thebinary log." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"off", + "name":"db_user_namespace", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Enables per-database user names.", + "vartype":"bool", + "max_value":"", + "scope":"{Global}", + "id":"1499", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"1000", + "name":"deadlock_timeout", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the time to wait on a lock before checking for deadlock.", + "vartype":"integer", + "max_value":"2147483647", + "scope":"{GlobalSession}", + "id":"1500", + "unit":"ms", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"32768", + "name":"binlog_cache_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"4096", + "dynamic":"t", + "rank":"-1", + "summary":"Options for binlog_cache_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"1431", + "unit":"NULL", + "description":"The size of the cache to hold changes to the binary logduring a transaction. A binary log cache is allocated foreach client if the server supports any transactional storageengines and if the server has the binary log enabled(--log-bin option). If youoften use large transactions you can increase this cachesize to get better performance. TheBinlog_cache_use andBinlog_cache_disk_usestatus variables can be useful for tuning the size of thisvariable. See Section 5.4.4 The Binary Log.binlog_cache_size sets the size for thetransaction cache only; the size of the statement cache isgoverned by thebinlog_stmt_cache_sizesystem variable." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"CRC32", + "name":"binlog_checksum", + "deprecated":"f", + "valid_vals":"NONE,CRC32", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for binlog_checksum", + "vartype":"string", + "max_value":"NULL", + "scope":"{Global}", + "id":"1432", + "unit":"NULL", + "description":"When enabled this variable causes the master to write achecksum for each event in the binary log.binlog_checksum supports the valuesNONE (disabled) andCRC32. The default isCRC32.When binlog_checksum is disabled (valueNONE) the server verifies that it iswriting only complete events to the binary log by writingand checking the event length (rather than a checksum) foreach event.Changing the value of this variable causes the binary log tobe rotated; checksums are always written to an entire binarylog file and never to only part of one.Setting this variable on the master to a value unrecognizedby the slave causes the slave to set its ownbinlog_checksum value toNONE and to stop replication with anerror. (Bug #13553750 Bug #61096) If backward compatibilitywith older slaves is a concern you may want to set thevalue explicitly to NONE." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"binlog_direct_non_transactional_updates", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for binlog_direct_non_transactional_updates", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1433", + "unit":"NULL", + "description":"Due to concurrency issues a slave can become inconsistentwhen a transaction contains updates to both transactionaland nontransactional tables. MySQL tries to preservecausality among these statements by writing nontransactionalstatements to the transaction cache which is flushed uponcommit. However problems arise when modifications done tonontransactional tables on behalf of a transaction becomeimmediately visible to other connections because thesechanges may not be written immediately into the binary log.Thebinlog_direct_non_transactional_updatesvariable offers one possible workaround to this issue. Bydefault this variable is disabled. Enablingbinlog_direct_non_transactional_updatescauses updates to nontransactional tables to be writtendirectly to the binary log rather than to the transactioncache.binlog_direct_non_transactional_updatesworks only for statements that are replicated using thestatement-based binary logging format; that isit works only when the value ofbinlog_format isSTATEMENT or whenbinlog_format isMIXED and a given statement is beingreplicated using the statement-based format. This variablehas no effect when the binary log format isROW or whenbinlog_format is set toMIXED and a given statement is replicatedusing the row-based format.In MySQL 5.7 this variable has no effect whenthe binary log format is ROW orMIXED. (Bug #51291)" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ABORT_SERVER", + "name":"binlog_error_action", + "deprecated":"f", + "valid_vals":"IGNORE_ERROR,ABORT_SERVER", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for binlog_error_action", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1434", + "unit":"NULL", + "description":"Controls what happens when the server encounters an errorsuch as not being able to write to flush or synchronize thebinary log which can cause the master's log to becomeinconsistent and replication slaves to lose synchronization.In MySQL 5.7.7 and later this variable defaults toABORT_SERVER which makes the server haltlogging and shut down whenever it encounters such an errorwith the binary log. Upon server restart all of thepreviously prepared and binary logged transactions arecommitted while any transactions which were prepared butnot binary logged due to the error are aborted.When binlog_error_action is set toIGNORE_ERROR if the server encounterssuch an error it continues the ongoing transaction logs theerror then halts logging and continues performing updates.To resume binary logginglog_bin must be enabledagain. This provides backward compatibility with olderversions of MySQL.In previous releases this variable was namedbinlogging_impossible_mode." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"STATEMENT", + "name":"binlog_format", + "deprecated":"f", + "valid_vals":"ROW,STATEMENT,MIXED", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for binlog-format", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1435", + "unit":"NULL", + "description":"This variable sets the binary logging format and can be anyone of STATEMENT ROWor MIXED. SeeSection 17.2.1 Replication Formats.binlog_format is set by the--binlog-format option atstartup or by thebinlog_format variable atruntime.Prior to MySQL 5.7.7 the default format wasSTATEMENT. In MySQL 5.7.7 and later thedefault is ROW.Exception: In MySQL Cluster thedefault is MIXED; statement-basedreplication is not supported for MySQL Cluster.You must have the SUPERprivilege to set either the global or sessionbinlog_format value.The rules governing when changes to this variable takeeffect and how long the effect lasts are the same as forother MySQL server system variables. SeeSection 13.7.4 SET Syntax for more information.When MIXED is specified statement-basedreplication is used except for cases where only row-basedreplication is guaranteed to lead to proper results. Forexample this happens when statements contain user-definedfunctions (UDF) or the UUID()function. An exception to this rule is thatMIXED always uses statement-basedreplication for stored functions and triggers.There are exceptions when you cannot switch the replicationformat at runtime:Trying to switch the format in those cases results in anerror.The binary log format affects the behavior of the followingserver options:These effects are discussed in detail in the descriptions ofthe individual options." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"binlog_group_commit_sync_delay", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for binlog_group_commit_sync_delay", + "vartype":"integer", + "max_value":"1000000", + "scope":"{Global}", + "id":"1436", + "unit":"NULL", + "description":"Controls how many microseconds the binary log commit waitsbefore synchronizing the binary log file to disk. By defaultbinlog-group-commit-sync-delayis set to 0 meaning that there is no delay. Settingbinlog-group-commit-sync-delayto a microsecond delay enables more transactions to besynchronized together to disk at once reducing the overalltime to commit a group of transactions because the largergroups require fewer time units per group. With the correcttuning this can increase slave performance withoutcompromising the master's throughput." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"binlog_group_commit_sync_no_delay_count", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for binlog_group_commit_sync_no_delay_count", + "vartype":"integer", + "max_value":"1000000", + "scope":"{Global}", + "id":"1437", + "unit":"NULL", + "description":"The maximum number of transactions to wait for beforeaborting the current delay as specified bybinlog-group-commit-sync-delay. Ifbinlog-group-commit-sync-delay is set to0 then this option has no effect." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"binlog_max_flush_queue_time", + "deprecated":"t", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for binlog_max_flush_queue_time", + "vartype":"integer", + "max_value":"100000", + "scope":"{Global}", + "id":"1439", + "unit":"NULL", + "description":"Formerly this controlled the time in microseconds tocontinue reading transactions from the flush queue beforeproceeding with group commit. In MySQL 5.7this variable no longer has any effect.binlog_max_flush_queue_time is deprecatedas of MySQL 5.7.9 and is marked for eventual removal in afuture MySQL release." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"binlog_order_commits", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for binlog_order_commits", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1440", + "unit":"NULL", + "description":"When this variable is enabled on a master (the default)transactions are externalized in the same order as they arewritten to the binary log. If disabled transactions may becommitted in parallel. In some cases disabling thisvariable might produce a performance increment." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"full", + "name":"binlog_row_image", + "deprecated":"f", + "valid_vals":"full, (Log all columns),minimal, (Log only changed columns, and columns needed to identify rows),noblob, (Log all columns, except for unneeded BLOB and TEXT columns)", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for binlog_row_image", + "vartype":"enumeration", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1441", + "unit":"NULL", + "description":"In MySQL row-based replication each row change eventcontains two images a before image whosecolumns are matched against when searching for the row to beupdated and an after image containing thechanges. Normally MySQL logs full rows (that is allcolumns) for both the before and after images. However itis not strictly necessary to include every column in bothimages and we can often save disk memory and networkusage by logging only those columns which are actuallyrequired.For the before image it is necessary only that the minimumset of columns required to uniquely identify rows is logged.If the table containing the row has a primary key then onlythe primary key column or columns are written to the binarylog. Otherwise if the table has a unique key all of whosecolumns are NOT NULL then only thecolumns in the unique key need be logged. (If the table hasneither a primary key nor a unique key without anyNULL columns then all columns must beused in the before image and logged.) In the after imageit is necessary to log only the columns which have actuallychanged.You can cause the server to log full or minimal rows usingthe binlog_row_image system variable.This variable actually takes one of three possible valuesas shown in the following list:The default value is full.In MySQL 5.5 and earlier full row images are always usedfor both before images and after images. If you need toreplicate from a newer master to a slave running MySQL 5.5or earlier the master should always use this value.When using minimal ornoblob deletes and updates areguaranteed to work correctly for a given table if and onlyif the following conditions are true for both the source anddestination tables:(In other words the tables must be identical with thepossible exception of indexes that are not part of thetables' primary keys.)If these conditions are not met it is possible that theprimary key column values in the destination table may proveinsufficient to provide a unique match for a delete orupdate. In this event no warning or error is issued; themaster and slave silently diverge thus breakingconsistency.Setting this variable has no effect when the binary loggingformat is STATEMENT. Whenbinlog_format isMIXED the setting forbinlog_row_image is applied to changesthat are logged using row-based format but this setting noeffect on changes logged as statements.Setting binlog_row_image on either theglobal or session level does not cause an implicit commit;this means that this variable can be changed while atransaction is in progress without affecting thetransaction." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"FALSE", + "name":"binlog_rows_query_log_events", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for binlog_rows_query_log_events", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{GlobalSession}", + "id":"1442", + "unit":"NULL", + "description":"Thebinlog_rows_query_log_eventssystem variable affects row-based logging only. Whenenabled it causes the MySQL Server to write informationallog events such as row query log events into its binary log.This information can be used for debugging and relatedpurposes; such as obtaining the original query issued on themaster when it cannot be reconstructed from the row updates.These events are normally ignored by MySQL programs readingthe binary log and so cause no issues when replicating orrestoring from backup." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"32768", + "name":"binlog_stmt_cache_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"4096", + "dynamic":"t", + "rank":"-1", + "summary":"Options for binlog_stmt_cache_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"1443", + "unit":"NULL", + "description":"This variable determines the size of the cache for thebinary log to hold nontransactional statements issued duringa transaction. Separate binary log transaction and statementcaches are allocated for each client if the server supportsany transactional storage engines and if the server has thebinary log enabled (--log-binoption). If you often use large nontransactional statementsduring transactions you can increase this cache size to getbetter performance. TheBinlog_stmt_cache_use andBinlog_stmt_cache_disk_usestatus variables can be useful for tuning the size of thisvariable. See Section 5.4.4 The Binary Log.The binlog_cache_sizesystem variable sets the size for the transaction cache." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"log_bin", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for log_bin", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"1444", + "unit":"NULL", + "description":"Whether the binary log is enabled. If the--log-bin option is usedthen the value of this variable is ON;otherwise it is OFF. This variablereports only on the status of binary logging (enabled ordisabled); it does not actually report the value to which--log-bin is set.See Section 5.4.4 The Binary Log." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"datadir + '/' + hostname + '-bin'", + "name":"log_bin_basename", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for log_bin_basename", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"1445", + "unit":"NULL", + "description":"Holds the name and complete path to the binary log file.Unlike the log_bin systemvariable log_bin_basenamereflects the name set with the--log-bin server option." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"PATH", + "name":"log_bin_index", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for log_bin_index", + "vartype":"file name", + "max_value":"NULL", + "scope":"{Global}", + "id":"1446", + "unit":"NULL", + "description":"The index file for binary log file names." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"0", + "name":"log_bin_use_v1_row_events", + "deprecated":"f", + "valid_vals":"1,0", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for log_bin_use_v1_row_events", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1447", + "unit":"NULL", + "description":"Shows whether Version 2 binary logging is in use. A value of1 shows that the server is writing the binary log usingVersion 1 logging events (the only version of binary logevents used in previous releases) and thus producing abinary log that can be read by older slaves. 0 indicatesthat Version 2 binary log events are in use.This variable is read-only. To switch between Version 1 andVersion 2 binary event binary logging it is necessary torestart mysqld with the--log-bin-use-v1-row-eventsoption.Other than when performing upgrades of MySQL ClusterReplication --log-bin-use-v1-events ischiefly of interest when setting up replication conflictdetection and resolution usingNDB,EPOCH_TRANS()EPOCH_TRANS() which requires Version2 binary row event logging. Thus this option and--ndb-log-transaction-id arenot compatible.For more information seeSection 18.6.11 MySQL Cluster Replication Conflict Resolution." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"FALSE", + "name":"log_slave_updates", + "deprecated":"f", + "valid_vals":"TRUE,FALSE", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"f", + "rank":"-1", + "summary":"Options for log_slave_updates", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1448", + "unit":"NULL", + "description":"Whether updates received by a slave server from a masterserver should be logged to the slave's own binary log.Binary logging must be enabled on the slave for thisvariable to have any effect. SeeSection 17.1.6 Replication and Binary Logging Options and Variables." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"ON", + "name":"log_statements_unsafe_for_binlog", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for log_statements_unsafe_for_binlog", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1449", + "unit":"NULL", + "description":"If error 1592 is encountered controls whether the generatedwarnings are added to the error log or not." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"20", + "name":"autovacuum_vacuum_cost_delay", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"-1", + "dynamic":"t", + "rank":"-1", + "summary":"Vacuum cost delay in milliseconds for autovacuum.", + "vartype":"integer", + "max_value":"100", + "scope":"{Global}", + "id":"1469", + "unit":"ms", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"-1", + "name":"autovacuum_vacuum_cost_limit", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"-1", + "dynamic":"t", + "rank":"-1", + "summary":"Vacuum cost amount available before napping for autovacuum.", + "vartype":"integer", + "max_value":"10000", + "scope":"{Global}", + "id":"1470", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"OFF", + "name":"master_verify_checksum", + "deprecated":"f", + "valid_vals":"ON,OFF", + "dbms_id":"4", + "min_value":"NULL", + "dynamic":"t", + "rank":"-1", + "summary":"Options for master_verify_checksum", + "vartype":"boolean", + "max_value":"NULL", + "scope":"{Global}", + "id":"1450", + "unit":"NULL", + "description":"Enabling this variable causes the master to examinechecksums when reading from the binary log.master_verify_checksum is disabled bydefault; in this case the master uses the event length fromthe binary log to verify events so that only completeevents are read from the binary log." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"18446744073709551615", + "name":"max_binlog_cache_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"4096", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_binlog_cache_size", + "vartype":"integer", + "max_value":"18446744073709551615", + "scope":"{Global}", + "id":"1451", + "unit":"NULL", + "description":"If a transaction requires more than this many bytes ofmemory the server generates a Multi-statementtransaction required more than 'max_binlog_cache_size' bytesof storage error. The minimum value is 4096. Themaximum possible value is 16EB (exabytes). The maximumrecommended value is 4GB; this is due to the fact that MySQLcurrently cannot work with binary log positions greater than4GB.max_binlog_cache_size sets the size forthe transaction cache only; the upper limit for thestatement cache is governed by themax_binlog_stmt_cache_sizesystem variable.In MySQL 5.7 the visibility to sessions ofmax_binlog_cache_size matches that of thebinlog_cache_size systemvariable; in other words changing its value effects onlynew sessions that are started after the value is changed." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1073741824", + "name":"max_binlog_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"4096", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_binlog_size", + "vartype":"integer", + "max_value":"1073741824", + "scope":"{Global}", + "id":"1452", + "unit":"NULL", + "description":"If a write to the binary log causes the current log filesize to exceed the value of this variable the serverrotates the binary logs (closes the current file and opensthe next one). The minimum value is 4096 bytes. The maximumand default value is 1GB.A transaction is written in one chunk to the binary log soit is never split between several binary logs. Therefore ifyou have big transactions you might see binary log fileslarger thanmax_binlog_size.If max_relay_log_size is 0the value ofmax_binlog_size applies torelay logs as well." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"18446744073709547520", + "name":"max_binlog_stmt_cache_size", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"4096", + "dynamic":"t", + "rank":"-1", + "summary":"Options for max_binlog_stmt_cache_size", + "vartype":"integer", + "max_value":"18446744073709547520", + "scope":"{Global}", + "id":"1453", + "unit":"NULL", + "description":"If nontransactional statements within a transaction requiremore than this many bytes of memory the server generates anerror. The minimum value is 4096. The maximum and defaultvalues are 4GB on 32-bit platforms and 16EB (exabytes) on64-bit platforms.max_binlog_stmt_cache_size sets the sizefor the statement cache only; the upper limit for thetransaction cache is governed exclusively by themax_binlog_cache_sizesystem variable." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"{NULL}", + "dangerous":"NA", + "default_val":"1", + "name":"sync_binlog", + "deprecated":"f", + "valid_vals":"NULL", + "dbms_id":"4", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Options for sync_binlog", + "vartype":"integer", + "max_value":"4294967295", + "scope":"{Global}", + "id":"1454", + "unit":"NULL", + "description":"Controls the number of binary log commit groups to collectbefore synchronizing the binary log to disk. Whensync_binlog=0 the binarylog is never synchronized to disk and whensync_binlog is set to avalue greater than 0 this number of binary log commit groupsis periodically synchronized to disk. Whensync_binlog=1 alltransactions are synchronized to the binary log before theyare committed. Therefore even in the event of an unexpectedrestart any transactions that are missing from the binarylog are only in prepared state. This causes theserver's automatic recovery routine to rollback thosetransactions. This guarantees that no transaction is lostfrom the binary log and is the safest option. However thiscan have a negative impact on performance because of anincreased number of disk writes. Using a higher valueimproves performance but with the increased risk of dataloss.When sync_binlog=0 orsync_binlog is greater than1 transactions are committed without having beensynchronized to disk. Therefore in the event of a powerfailure or operating system crash it is possible that theserver has committed some transactions that have not beensynchronized to the binary log. Therefore it is impossiblefor the recovery routine to recover these transactions andthey will be lost from the binary log.Prior to MySQL 5.7.7 the default value ofsync_binlog was 0 whichconfigures no synchronizing to diskin this case theserver relies on the operating system to flush the binarylog's contents from time to time as for any other file.MySQL 5.7.7 and later use a default value of 1 which is thesafest choice but as noted above can impact performance." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"off", + "name":"allow_system_table_mods", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"f", + "rank":"-1", + "summary":"Allows modifications of the structure of system tables.", + "vartype":"bool", + "max_value":"", + "scope":"{Global}", + "id":"1455", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"psql", + "name":"application_name", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the application name to be reported in statistics and logs.", + "vartype":"string", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1456", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"", + "dangerous":"NO", + "default_val":"(disabled)", + "name":"archive_command", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the shell command that will be called to archive a WAL file.", + "vartype":"string", + "max_value":"", + "scope":"{Global}", + "id":"1457", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"", + "dangerous":"NO", + "default_val":"off", + "name":"archive_mode", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"f", + "rank":"-1", + "summary":"Allows archiving of WAL files using archive_command.", + "vartype":"bool", + "max_value":"", + "scope":"{Global}", + "id":"1458", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"", + "dangerous":"NO", + "default_val":"0", + "name":"archive_timeout", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Forces a switch to the next xlog file if a new file has not been started within N seconds.", + "vartype":"integer", + "max_value":"1073741823", + "scope":"{Global}", + "id":"1459", + "unit":"s", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"on", + "name":"array_nulls", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Enable input of NULL elements in arrays.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1460", + "unit":"", + "description":"When turned on unquoted NULL in an array input value means a null value; otherwise it is taken literally." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"60", + "name":"authentication_timeout", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the maximum allowed time to complete client authentication.", + "vartype":"integer", + "max_value":"600", + "scope":"{Global}", + "id":"1461", + "unit":"s", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"on", + "name":"autovacuum", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Starts the autovacuum subprocess.", + "vartype":"bool", + "max_value":"", + "scope":"{Global}", + "id":"1462", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"0.1", + "name":"autovacuum_analyze_scale_factor", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Number of tuple inserts updates or deletes prior to analyze as a fraction of reltuples.", + "vartype":"real", + "max_value":"100", + "scope":"{Global}", + "id":"1463", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"50", + "name":"autovacuum_analyze_threshold", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Minimum number of tuple inserts updates or deletes prior to analyze.", + "vartype":"integer", + "max_value":"2147483647", + "scope":"{Global}", + "id":"1464", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"200000000", + "name":"autovacuum_freeze_max_age", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"100000", + "dynamic":"f", + "rank":"-1", + "summary":"Age at which to autovacuum a table to prevent transaction ID wraparound.", + "vartype":"integer", + "max_value":"2000000000", + "scope":"{Global}", + "id":"1465", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"3", + "name":"autovacuum_max_workers", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"1", + "dynamic":"f", + "rank":"-1", + "summary":"Sets the maximum number of simultaneously running autovacuum worker processes.", + "vartype":"integer", + "max_value":"8388607", + "scope":"{Global}", + "id":"1466", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"400000000", + "name":"autovacuum_multixact_freeze_max_age", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"10000", + "dynamic":"f", + "rank":"-1", + "summary":"Multixact age at which to autovacuum a table to prevent multixact wraparound.", + "vartype":"integer", + "max_value":"2000000000", + "scope":"{Global}", + "id":"1467", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"60", + "name":"autovacuum_naptime", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Time to sleep between autovacuum runs.", + "vartype":"integer", + "max_value":"2147483", + "scope":"{Global}", + "id":"1468", + "unit":"s", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"", + "name":"default_tablespace", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the default tablespace to create tables and indexes in.", + "vartype":"string", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1507", + "unit":"", + "description":"An empty string selects the database's default tablespace." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"pg_catalog.english", + "name":"default_text_search_config", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Sets default text search configuration.", + "vartype":"string", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1508", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"off", + "name":"default_transaction_deferrable", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the default deferrable status of new transactions.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1509", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"read committed", + "name":"default_transaction_isolation", + "deprecated":"f", + "valid_vals":"serializable,repeatable read,read committed,read uncommitted", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the transaction isolation level of each new transaction.", + "vartype":"enum", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1510", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"off", + "name":"default_transaction_read_only", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the default read-only status of new transactions.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1511", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"off", + "name":"default_with_oids", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Create new tables with OIDs by default.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1512", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"libdir", + "name":"dynamic_library_path", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the path for dynamically loadable modules.", + "vartype":"string", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1513", + "unit":"", + "description":"If a dynamically loadable module needs to be opened and the specified name does not have a directory component (i.e. the name does not contain a slash) the system will search this path for the specified file." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"16384", + "name":"effective_cache_size", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the planner's assumption about the size of the disk cache.", + "vartype":"integer", + "max_value":"2147483647", + "scope":"{GlobalSession}", + "id":"1514", + "unit":"8kB", + "description":"That is the portion of the kernel's disk cache that will be used for PostgreSQL data files. This is measured in disk pages which are normally 8 kB each." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"1", + "name":"effective_io_concurrency", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Number of simultaneous requests that can be handled efficiently by the disk subsystem.", + "vartype":"integer", + "max_value":"1000", + "scope":"{GlobalSession}", + "id":"1515", + "unit":"", + "description":"For RAID arrays this should be approximately the number of drive spindles in the array." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"", + "dangerous":"NO", + "default_val":"on", + "name":"enable_bitmapscan", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Enables the planner's use of bitmap-scan plans.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1516", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"", + "dangerous":"NO", + "default_val":"on", + "name":"enable_hashagg", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Enables the planner's use of hashed aggregation plans.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1517", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"", + "dangerous":"NO", + "default_val":"on", + "name":"enable_hashjoin", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Enables the planner's use of hash join plans.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1518", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"", + "dangerous":"NO", + "default_val":"on", + "name":"enable_indexonlyscan", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Enables the planner's use of index-only-scan plans.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1519", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"", + "dangerous":"NO", + "default_val":"on", + "name":"enable_indexscan", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Enables the planner's use of index-scan plans.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1520", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"", + "dangerous":"NO", + "default_val":"on", + "name":"enable_material", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Enables the planner's use of materialization.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1521", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"", + "dangerous":"NO", + "default_val":"on", + "name":"enable_mergejoin", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Enables the planner's use of merge join plans.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1522", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"", + "dangerous":"NO", + "default_val":"on", + "name":"enable_nestloop", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Enables the planner's use of nested-loop join plans.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1523", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"", + "dangerous":"NO", + "default_val":"on", + "name":"enable_seqscan", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Enables the planner's use of sequential-scan plans.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1524", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"", + "dangerous":"NO", + "default_val":"on", + "name":"enable_sort", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Enables the planner's use of explicit sort steps.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1525", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"", + "dangerous":"NO", + "default_val":"on", + "name":"enable_tidscan", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Enables the planner's use of TID scan plans.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1526", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"on", + "name":"escape_string_warning", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Warn about backslash escapes in ordinary string literals.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1527", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"PostgreSQL", + "name":"event_source", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"f", + "rank":"-1", + "summary":"Sets the application name used to identify PostgreSQL messages in the event log.", + "vartype":"string", + "max_value":"", + "scope":"{Global}", + "id":"1528", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"off", + "name":"exit_on_error", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Terminate session on any error.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1529", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"/var/run/postgresql/9.3-main.pid", + "name":"external_pid_file", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"f", + "rank":"-1", + "summary":"Writes the postmaster PID to the specified file.", + "vartype":"string", + "max_value":"", + "scope":"{Global}", + "id":"1530", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"0", + "name":"extra_float_digits", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"-15", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the number of digits displayed for floating-point values.", + "vartype":"integer", + "max_value":"3", + "scope":"{GlobalSession}", + "id":"1531", + "unit":"", + "description":"This affects real double precision and geometric data types. The parameter value is added to the standard number of digits (FLT_DIG or DBL_DIG as appropriate)." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"", + "dangerous":"NO", + "default_val":"8", + "name":"from_collapse_limit", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the FROM-list size beyond which subqueries are not collapsed.", + "vartype":"integer", + "max_value":"2147483647", + "scope":"{GlobalSession}", + "id":"1532", + "unit":"", + "description":"The planner will merge subqueries into upper queries if the resulting FROM list would have no more than this many items." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"YES", + "default_val":"on", + "name":"fsync", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Forces synchronization of updates to disk.", + "vartype":"bool", + "max_value":"", + "scope":"{Global}", + "id":"1533", + "unit":"", + "description":"The server will use the fsync() system call in several places to make sure that updates are physically written to disk. This insures that a database cluster will recover to a consistent state after an operating system or hardware crash." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"YES", + "default_val":"on", + "name":"full_page_writes", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Writes full pages to WAL when first modified after a checkpoint.", + "vartype":"bool", + "max_value":"", + "scope":"{Global}", + "id":"1534", + "unit":"", + "description":"A page write in process during an operating system crash might be only partially written to disk.During recovery the row changes stored in WAL are not enough to recover.This option writes pages when first modified after a checkpoint to WAL so full recovery is possible." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"", + "dangerous":"NO", + "default_val":"on", + "name":"geqo", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Enables genetic query optimization.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1535", + "unit":"", + "description":"This algorithm attempts to do planning without exhaustive searching." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"", + "dangerous":"NO", + "default_val":"5", + "name":"geqo_effort", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"GEQO: effort is used to set the default for other GEQO parameters.", + "vartype":"integer", + "max_value":"10", + "scope":"{GlobalSession}", + "id":"1536", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"32", + "name":"wal_buffers", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"-1", + "dynamic":"f", + "rank":"-1", + "summary":"Sets the number of disk-page buffers in shared memory for WAL.", + "vartype":"integer", + "max_value":"262143", + "scope":"{Global}", + "id":"1673", + "unit":"8kB", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"", + "dangerous":"NO", + "default_val":"0", + "name":"geqo_generations", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"GEQO: number of iterations of the algorithm.", + "vartype":"integer", + "max_value":"2147483647", + "scope":"{GlobalSession}", + "id":"1537", + "unit":"", + "description":"Zero selects a suitable default value." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"", + "dangerous":"NO", + "default_val":"0", + "name":"geqo_pool_size", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"GEQO: number of individuals in the population.", + "vartype":"integer", + "max_value":"2147483647", + "scope":"{GlobalSession}", + "id":"1538", + "unit":"", + "description":"Zero selects a suitable default value." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"", + "dangerous":"NO", + "default_val":"0", + "name":"geqo_seed", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"GEQO: seed for random path selection.", + "vartype":"real", + "max_value":"1", + "scope":"{GlobalSession}", + "id":"1539", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"", + "dangerous":"NO", + "default_val":"2", + "name":"geqo_selection_bias", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"1.5", + "dynamic":"t", + "rank":"-1", + "summary":"GEQO: selective pressure within the population.", + "vartype":"real", + "max_value":"2", + "scope":"{GlobalSession}", + "id":"1540", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"", + "dangerous":"NO", + "default_val":"12", + "name":"geqo_threshold", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"2", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the threshold of FROM items beyond which GEQO is used.", + "vartype":"integer", + "max_value":"2147483647", + "scope":"{GlobalSession}", + "id":"1541", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"0", + "name":"gin_fuzzy_search_limit", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the maximum allowed result for exact search by GIN.", + "vartype":"integer", + "max_value":"2147483647", + "scope":"{GlobalSession}", + "id":"1542", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"/etc/postgresql/9.3/main/pg_hba.conf", + "name":"hba_file", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"f", + "rank":"-1", + "summary":"Sets the server's hba configuration file.", + "vartype":"string", + "max_value":"", + "scope":"{Global}", + "id":"1543", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"", + "dangerous":"NO", + "default_val":"off", + "name":"hot_standby", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"f", + "rank":"-1", + "summary":"Allows connections and queries during recovery.", + "vartype":"bool", + "max_value":"", + "scope":"{Global}", + "id":"1544", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"", + "dangerous":"NO", + "default_val":"off", + "name":"hot_standby_feedback", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Allows feedback from a hot standby to the primary that will avoid query conflicts.", + "vartype":"bool", + "max_value":"", + "scope":"{Global}", + "id":"1545", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"/etc/postgresql/9.3/main/pg_ident.conf", + "name":"ident_file", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"f", + "rank":"-1", + "summary":"Sets the server's ident configuration file.", + "vartype":"string", + "max_value":"", + "scope":"{Global}", + "id":"1546", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"off", + "name":"ignore_checksum_failure", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Continues processing after a checksum failure.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1547", + "unit":"", + "description":"Detection of a checksum failure normally causes PostgreSQL to report an error aborting the current transaction. Setting ignore_checksum_failure to true causes the system to ignore the failure (but still report a warning) and continue processing. This behavior could cause crashes or other serious problems. Only has an effect if checksums are enabled." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"off", + "name":"ignore_system_indexes", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Disables reading from system indexes.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1548", + "unit":"", + "description":"It does not prevent updating the indexes so it is safe to use.The worst consequence is slowness." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"on", + "name":"integer_datetimes", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"f", + "rank":"-1", + "summary":"Datetimes are integer based.", + "vartype":"bool", + "max_value":"", + "scope":"{NA}", + "id":"1549", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"postgres", + "name":"IntervalStyle", + "deprecated":"f", + "valid_vals":"postgres,postgres_verbose,sql_standard,iso_8601", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the display format for interval values.", + "vartype":"enum", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1550", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"", + "dangerous":"NO", + "default_val":"8", + "name":"join_collapse_limit", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the FROM-list size beyond which JOIN constructs are not flattened.", + "vartype":"integer", + "max_value":"2147483647", + "scope":"{GlobalSession}", + "id":"1551", + "unit":"", + "description":"The planner will flatten explicit JOIN constructs into lists of FROM items whenever a list of no more than this many items would result." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"off", + "name":"krb_caseins_users", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Sets whether Kerberos and GSSAPI user names should be treated as case-insensitive.", + "vartype":"bool", + "max_value":"", + "scope":"{Global}", + "id":"1552", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"FILE:/etc/postgresql-common/krb5.keytab", + "name":"krb_server_keyfile", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the location of the Kerberos server key file.", + "vartype":"string", + "max_value":"", + "scope":"{Global}", + "id":"1553", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"postgres", + "name":"krb_srvname", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the name of the Kerberos service.", + "vartype":"string", + "max_value":"", + "scope":"{Global}", + "id":"1554", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"en_US.UTF-8", + "name":"lc_collate", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"f", + "rank":"-1", + "summary":"Shows the collation order locale.", + "vartype":"string", + "max_value":"", + "scope":"{NA}", + "id":"1555", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"en_US.UTF-8", + "name":"lc_ctype", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"f", + "rank":"-1", + "summary":"Shows the character classification and case conversion locale.", + "vartype":"string", + "max_value":"", + "scope":"{NA}", + "id":"1556", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"en_US.UTF-8", + "name":"lc_messages", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the language in which messages are displayed.", + "vartype":"string", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1557", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"en_US.UTF-8", + "name":"lc_monetary", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the locale for formatting monetary amounts.", + "vartype":"string", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1558", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"en_US.UTF-8", + "name":"lc_numeric", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the locale for formatting numbers.", + "vartype":"string", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1559", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"en_US.UTF-8", + "name":"lc_time", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the locale for formatting date and time values.", + "vartype":"string", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1560", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"gs14445.sp.cs.cmu.edu", + "name":"listen_addresses", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"f", + "rank":"-1", + "summary":"Sets the host name or IP address(es) to listen to.", + "vartype":"string", + "max_value":"", + "scope":"{Global}", + "id":"1561", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"off", + "name":"lo_compat_privileges", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Enables backward compatibility mode for privilege checks on large objects.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1562", + "unit":"", + "description":"Skips privilege checks when reading or modifying large objects for compatibility with PostgreSQL releases prior to 9.0." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"", + "name":"local_preload_libraries", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Lists shared libraries to preload into each backend.", + "vartype":"string", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1563", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"0", + "name":"lock_timeout", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the maximum allowed duration of any wait for a lock.", + "vartype":"integer", + "max_value":"2147483647", + "scope":"{GlobalSession}", + "id":"1564", + "unit":"ms", + "description":"A value of 0 turns off the timeout." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"-1", + "name":"log_autovacuum_min_duration", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"-1", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the minimum execution time above which autovacuum actions will be logged.", + "vartype":"integer", + "max_value":"2147483647", + "scope":"{Global}", + "id":"1565", + "unit":"ms", + "description":"Zero prints all actions. -1 turns autovacuum logging off." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"off", + "name":"log_checkpoints", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Logs each checkpoint.", + "vartype":"bool", + "max_value":"", + "scope":"{Global}", + "id":"1566", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"off", + "name":"log_connections", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Logs each successful connection.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1567", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"stderr", + "name":"log_destination", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the destination for server log output.", + "vartype":"string", + "max_value":"", + "scope":"{Global}", + "id":"1568", + "unit":"", + "description":"Valid values are combinations of stderr syslog csvlog and eventlog depending on the platform." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"pg_log", + "name":"log_directory", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the destination directory for log files.", + "vartype":"string", + "max_value":"", + "scope":"{Global}", + "id":"1569", + "unit":"", + "description":"Can be specified as relative to the data directory or as absolute path." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"off", + "name":"log_disconnections", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Logs end of a session including duration.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1570", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"off", + "name":"log_duration", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Logs the duration of each completed SQL statement.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1571", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"default", + "name":"log_error_verbosity", + "deprecated":"f", + "valid_vals":"terse,default,verbose", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the verbosity of logged messages.", + "vartype":"enum", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1572", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"off", + "name":"log_executor_stats", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Writes executor performance statistics to the server log.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1573", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"0600", + "name":"log_file_mode", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the file permissions for log files.", + "vartype":"integer", + "max_value":"511", + "scope":"{Global}", + "id":"1574", + "unit":"", + "description":"The parameter value is expected to be a numeric mode specification in the form accepted by the chmod and umask system calls. (To use the customary octal format the number must start with a 0 (zero).)" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"postgresql-%Y-%m-%d_%H%M%S.log", + "name":"log_filename", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the file name pattern for log files.", + "vartype":"string", + "max_value":"", + "scope":"{Global}", + "id":"1575", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"off", + "name":"log_hostname", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Logs the host name in the connection logs.", + "vartype":"bool", + "max_value":"", + "scope":"{Global}", + "id":"1576", + "unit":"", + "description":"By default connection logs only show the IP address of the connecting host. If you want them to show the host name you can turn this on but depending on your host name resolution setup it might impose a non-negligible performance penalty." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"", + "name":"log_line_prefix", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Controls information prefixed to each log line.", + "vartype":"string", + "max_value":"", + "scope":"{Global}", + "id":"1577", + "unit":"", + "description":"If blank no prefix is used." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"off", + "name":"log_lock_waits", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Logs long lock waits.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1578", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"-1", + "name":"log_min_duration_statement", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"-1", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the minimum execution time above which statements will be logged.", + "vartype":"integer", + "max_value":"2147483647", + "scope":"{GlobalSession}", + "id":"1579", + "unit":"ms", + "description":"Zero prints all queries. -1 turns this feature off." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"error", + "name":"log_min_error_statement", + "deprecated":"f", + "valid_vals":"debug5,debug4,debug3,debug2,debug1,info,notice,warning,error,log,fatal,panic", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Causes all statements generating error at or above this level to be logged.", + "vartype":"enum", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1580", + "unit":"", + "description":"Each level includes all the levels that follow it. The later the level the fewer messages are sent." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"warning", + "name":"log_min_messages", + "deprecated":"f", + "valid_vals":"debug5,debug4,debug3,debug2,debug1,info,notice,warning,error,log,fatal,panic", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the message levels that are logged.", + "vartype":"enum", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1581", + "unit":"", + "description":"Each level includes all the levels that follow it. The later the level the fewer messages are sent." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"off", + "name":"log_parser_stats", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Writes parser performance statistics to the server log.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1582", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"off", + "name":"log_planner_stats", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Writes planner performance statistics to the server log.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1583", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"1440", + "name":"log_rotation_age", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Automatic log file rotation will occur after N minutes.", + "vartype":"integer", + "max_value":"35791394", + "scope":"{Global}", + "id":"1584", + "unit":"min", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"10240", + "name":"log_rotation_size", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Automatic log file rotation will occur after N kilobytes.", + "vartype":"integer", + "max_value":"2097151", + "scope":"{Global}", + "id":"1585", + "unit":"kB", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"none", + "name":"log_statement", + "deprecated":"f", + "valid_vals":"none,ddl,mod,all", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the type of statements logged.", + "vartype":"enum", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1586", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"off", + "name":"log_statement_stats", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Writes cumulative performance statistics to the server log.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1587", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"-1", + "name":"log_temp_files", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"-1", + "dynamic":"t", + "rank":"-1", + "summary":"Log the use of temporary files larger than this number of kilobytes.", + "vartype":"integer", + "max_value":"2147483647", + "scope":"{GlobalSession}", + "id":"1588", + "unit":"kB", + "description":"Zero logs all files. The default is -1 (turning this feature off)." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"GMT", + "name":"log_timezone", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the time zone to use in log messages.", + "vartype":"string", + "max_value":"", + "scope":"{Global}", + "id":"1589", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"off", + "name":"log_truncate_on_rotation", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Truncate existing log files of same name during log rotation.", + "vartype":"bool", + "max_value":"", + "scope":"{Global}", + "id":"1590", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"off", + "name":"logging_collector", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"f", + "rank":"-1", + "summary":"Start a subprocess to capture stderr output and/or csvlogs into log files.", + "vartype":"bool", + "max_value":"", + "scope":"{Global}", + "id":"1591", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"16384", + "name":"maintenance_work_mem", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"1024", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the maximum memory to be used for maintenance operations.", + "vartype":"integer", + "max_value":"2147483647", + "scope":"{GlobalSession}", + "id":"1592", + "unit":"kB", + "description":"This includes operations such as VACUUM and CREATE INDEX." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"100", + "name":"max_connections", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"1", + "dynamic":"f", + "rank":"-1", + "summary":"Sets the maximum number of concurrent connections.", + "vartype":"integer", + "max_value":"8388607", + "scope":"{Global}", + "id":"1593", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"1000", + "name":"max_files_per_process", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"25", + "dynamic":"f", + "rank":"-1", + "summary":"Sets the maximum number of simultaneously open files for each server process.", + "vartype":"integer", + "max_value":"2147483647", + "scope":"{Global}", + "id":"1594", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"100", + "name":"max_function_args", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"100", + "dynamic":"f", + "rank":"-1", + "summary":"Shows the maximum number of function arguments.", + "vartype":"integer", + "max_value":"100", + "scope":"{NA}", + "id":"1595", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"63", + "name":"max_identifier_length", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"63", + "dynamic":"f", + "rank":"-1", + "summary":"Shows the maximum identifier length.", + "vartype":"integer", + "max_value":"63", + "scope":"{NA}", + "id":"1596", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"32", + "name":"max_index_keys", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"32", + "dynamic":"f", + "rank":"-1", + "summary":"Shows the maximum number of index keys.", + "vartype":"integer", + "max_value":"32", + "scope":"{NA}", + "id":"1597", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"64", + "name":"max_locks_per_transaction", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"10", + "dynamic":"f", + "rank":"-1", + "summary":"Sets the maximum number of locks per transaction.", + "vartype":"integer", + "max_value":"2147483647", + "scope":"{Global}", + "id":"1598", + "unit":"", + "description":"The shared lock table is sized on the assumption that at most max_locks_per_transaction * max_connections distinct objects will need to be locked at any one time." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"64", + "name":"max_pred_locks_per_transaction", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"10", + "dynamic":"f", + "rank":"-1", + "summary":"Sets the maximum number of predicate locks per transaction.", + "vartype":"integer", + "max_value":"2147483647", + "scope":"{Global}", + "id":"1599", + "unit":"", + "description":"The shared predicate lock table is sized on the assumption that at most max_pred_locks_per_transaction * max_connections distinct objects will need to be locked at any one time." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"0", + "name":"max_prepared_transactions", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"Sets the maximum number of simultaneously prepared transactions.", + "vartype":"integer", + "max_value":"8388607", + "scope":"{Global}", + "id":"1600", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"2048", + "name":"max_stack_depth", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"100", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the maximum stack depth in kilobytes.", + "vartype":"integer", + "max_value":"2147483647", + "scope":"{GlobalSession}", + "id":"1601", + "unit":"kB", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"", + "dangerous":"NO", + "default_val":"30000", + "name":"max_standby_archive_delay", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"-1", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the maximum delay before canceling queries when a hot standby server is processing archived WAL data.", + "vartype":"integer", + "max_value":"2147483647", + "scope":"{Global}", + "id":"1602", + "unit":"ms", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"", + "dangerous":"NO", + "default_val":"0", + "name":"wal_keep_segments", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the number of WAL files held for standby servers.", + "vartype":"integer", + "max_value":"2147483647", + "scope":"{Global}", + "id":"1674", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"", + "dangerous":"NO", + "default_val":"30000", + "name":"max_standby_streaming_delay", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"-1", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the maximum delay before canceling queries when a hot standby server is processing streamed WAL data.", + "vartype":"integer", + "max_value":"2147483647", + "scope":"{Global}", + "id":"1603", + "unit":"ms", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"", + "dangerous":"NO", + "default_val":"0", + "name":"max_wal_senders", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"Sets the maximum number of simultaneously running WAL sender processes.", + "vartype":"integer", + "max_value":"8388607", + "scope":"{Global}", + "id":"1604", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"on", + "name":"password_encryption", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Encrypt passwords.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1605", + "unit":"", + "description":"When a password is specified in CREATE USER or ALTER USER without writing either ENCRYPTED or UNENCRYPTED this parameter determines whether the password is to be encrypted." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"5432", + "name":"port", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"1", + "dynamic":"f", + "rank":"-1", + "summary":"Sets the TCP port the server listens on.", + "vartype":"integer", + "max_value":"65535", + "scope":"{Global}", + "id":"1606", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"0", + "name":"post_auth_delay", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Waits N seconds on connection startup after authentication.", + "vartype":"integer", + "max_value":"2147", + "scope":"{GlobalSession}", + "id":"1607", + "unit":"s", + "description":"This allows attaching a debugger to the process." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"0", + "name":"pre_auth_delay", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Waits N seconds on connection startup before authentication.", + "vartype":"integer", + "max_value":"60", + "scope":"{Global}", + "id":"1608", + "unit":"s", + "description":"This allows attaching a debugger to the process." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"off", + "name":"quote_all_identifiers", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"When generating SQL fragments quote all identifiers.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1609", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"4", + "name":"random_page_cost", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the planner's estimate of the cost of a nonsequentially fetched disk page.", + "vartype":"real", + "max_value":"1.79769e+308", + "scope":"{GlobalSession}", + "id":"1610", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"on", + "name":"restart_after_crash", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Reinitialize server after backend crash.", + "vartype":"bool", + "max_value":"", + "scope":"{Global}", + "id":"1611", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"userpublic", + "name":"search_path", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the schema search order for names that are not schema-qualified.", + "vartype":"string", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1612", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"131072", + "name":"segment_size", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"131072", + "dynamic":"f", + "rank":"-1", + "summary":"Shows the number of pages per disk file.", + "vartype":"integer", + "max_value":"131072", + "scope":"{NA}", + "id":"1613", + "unit":"8kB", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"1", + "name":"seq_page_cost", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the planner's estimate of the cost of a sequentially fetched disk page.", + "vartype":"real", + "max_value":"1.79769e+308", + "scope":"{GlobalSession}", + "id":"1614", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"UTF8", + "name":"server_encoding", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"f", + "rank":"-1", + "summary":"Sets the server (database) character set encoding.", + "vartype":"string", + "max_value":"", + "scope":"{NA}", + "id":"1615", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"9.3.11", + "name":"server_version", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"f", + "rank":"-1", + "summary":"Shows the server version.", + "vartype":"string", + "max_value":"", + "scope":"{NA}", + "id":"1616", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"90311", + "name":"server_version_num", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"90311", + "dynamic":"f", + "rank":"-1", + "summary":"Shows the server version as an integer.", + "vartype":"integer", + "max_value":"90311", + "scope":"{NA}", + "id":"1617", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"origin", + "name":"session_replication_role", + "deprecated":"f", + "valid_vals":"origin,replica,local", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the session's behavior for triggers and rewrite rules.", + "vartype":"enum", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1618", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"1024", + "name":"shared_buffers", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"16", + "dynamic":"f", + "rank":"-1", + "summary":"Sets the number of shared memory buffers used by the server.", + "vartype":"integer", + "max_value":"1073741823", + "scope":"{Global}", + "id":"1619", + "unit":"8kB", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"", + "name":"shared_preload_libraries", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"f", + "rank":"-1", + "summary":"Lists shared libraries to preload into server.", + "vartype":"string", + "max_value":"", + "scope":"{Global}", + "id":"1620", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"on", + "name":"sql_inheritance", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Causes subtables to be included by default in various commands.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1621", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"on", + "name":"ssl", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"f", + "rank":"-1", + "summary":"Enables SSL connections.", + "vartype":"bool", + "max_value":"", + "scope":"{Global}", + "id":"1622", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"", + "name":"ssl_ca_file", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"f", + "rank":"-1", + "summary":"Location of the SSL certificate authority file.", + "vartype":"string", + "max_value":"", + "scope":"{Global}", + "id":"1623", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"/etc/ssl/certs/ssl-cert-snakeoil.pem", + "name":"ssl_cert_file", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"f", + "rank":"-1", + "summary":"Location of the SSL server certificate file.", + "vartype":"string", + "max_value":"", + "scope":"{Global}", + "id":"1624", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"DEFAULT:!LOW:!EXP:!MD5:@STRENGTH", + "name":"ssl_ciphers", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"f", + "rank":"-1", + "summary":"Sets the list of allowed SSL ciphers.", + "vartype":"string", + "max_value":"", + "scope":"{Global}", + "id":"1625", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"", + "name":"ssl_crl_file", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"f", + "rank":"-1", + "summary":"Location of the SSL certificate revocation list file.", + "vartype":"string", + "max_value":"", + "scope":"{Global}", + "id":"1626", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"/etc/ssl/private/ssl-cert-snakeoil.key", + "name":"ssl_key_file", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"f", + "rank":"-1", + "summary":"Location of the SSL server private key file.", + "vartype":"string", + "max_value":"", + "scope":"{Global}", + "id":"1627", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"0", + "name":"ssl_renegotiation_limit", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Set the amount of traffic to send and receive before renegotiating the encryption keys.", + "vartype":"integer", + "max_value":"2147483647", + "scope":"{GlobalSession}", + "id":"1628", + "unit":"kB", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"on", + "name":"standard_conforming_strings", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Causes '...' strings to treat backslashes literally.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1629", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"0", + "name":"statement_timeout", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the maximum allowed duration of any statement.", + "vartype":"integer", + "max_value":"2147483647", + "scope":"{GlobalSession}", + "id":"1630", + "unit":"ms", + "description":"A value of 0 turns off the timeout." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"pg_stat_tmp", + "name":"stats_temp_directory", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Writes temporary statistics files to the specified directory.", + "vartype":"string", + "max_value":"", + "scope":"{Global}", + "id":"1631", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"3", + "name":"superuser_reserved_connections", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"Sets the number of connection slots reserved for superusers.", + "vartype":"integer", + "max_value":"8388607", + "scope":"{Global}", + "id":"1632", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"on", + "name":"synchronize_seqscans", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Enable synchronized sequential scans.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1633", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"YES", + "default_val":"on", + "name":"synchronous_commit", + "deprecated":"f", + "valid_vals":"local,remote_write,on,off", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the current transaction's synchronization level.", + "vartype":"enum", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1634", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"", + "dangerous":"NO", + "default_val":"", + "name":"synchronous_standby_names", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"List of names of potential synchronous standbys.", + "vartype":"string", + "max_value":"", + "scope":"{Global}", + "id":"1635", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"local0", + "name":"syslog_facility", + "deprecated":"f", + "valid_vals":"local0,local1,local2,local3,local4,local5,local6,local7", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the syslog facility to be used when syslog enabled.", + "vartype":"enum", + "max_value":"", + "scope":"{Global}", + "id":"1636", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"postgres", + "name":"syslog_ident", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the program name used to identify PostgreSQL messages in syslog.", + "vartype":"string", + "max_value":"", + "scope":"{Global}", + "id":"1637", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"0", + "name":"tcp_keepalives_count", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Maximum number of TCP keepalive retransmits.", + "vartype":"integer", + "max_value":"2147483647", + "scope":"{GlobalSession}", + "id":"1638", + "unit":"", + "description":"This controls the number of consecutive keepalive retransmits that can be lost before a connection is considered dead. A value of 0 uses the system default." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"0", + "name":"tcp_keepalives_idle", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Time between issuing TCP keepalives.", + "vartype":"integer", + "max_value":"2147483647", + "scope":"{GlobalSession}", + "id":"1639", + "unit":"s", + "description":"A value of 0 uses the system default." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"0", + "name":"tcp_keepalives_interval", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Time between TCP keepalive retransmits.", + "vartype":"integer", + "max_value":"2147483647", + "scope":"{GlobalSession}", + "id":"1640", + "unit":"s", + "description":"A value of 0 uses the system default." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"1024", + "name":"temp_buffers", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"100", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the maximum number of temporary buffers used by each session.", + "vartype":"integer", + "max_value":"1073741823", + "scope":"{GlobalSession}", + "id":"1641", + "unit":"8kB", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"-1", + "name":"temp_file_limit", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"-1", + "dynamic":"t", + "rank":"-1", + "summary":"Limits the total size of all temporary files used by each session.", + "vartype":"integer", + "max_value":"2147483647", + "scope":"{GlobalSession}", + "id":"1642", + "unit":"kB", + "description":"-1 means no limit." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"", + "name":"temp_tablespaces", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the tablespace(s) to use for temporary tables and sort files.", + "vartype":"string", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1643", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"GMT", + "name":"TimeZone", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the time zone for displaying and interpreting time stamps.", + "vartype":"string", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1644", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"Default", + "name":"timezone_abbreviations", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Selects a file of time zone abbreviations.", + "vartype":"string", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1645", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"off", + "name":"trace_notify", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Generates debugging output for LISTEN and NOTIFY.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1646", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"log", + "name":"trace_recovery_messages", + "deprecated":"f", + "valid_vals":"debug5,debug4,debug3,debug2,debug1,log,notice,warning,error", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Enables logging of recovery-related debugging information.", + "vartype":"enum", + "max_value":"", + "scope":"{Global}", + "id":"1647", + "unit":"", + "description":"Each level includes all the levels that follow it. The later the level the fewer messages are sent." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"off", + "name":"trace_sort", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Emit information about resource usage in sorting.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1648", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"on", + "name":"track_activities", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Collects information about executing commands.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1649", + "unit":"", + "description":"Enables the collection of information on the currently executing command of each session along with the time at which that command began execution." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"1024", + "name":"track_activity_query_size", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"100", + "dynamic":"f", + "rank":"-1", + "summary":"Sets the size reserved for pg_stat_activity.query in bytes.", + "vartype":"integer", + "max_value":"102400", + "scope":"{Global}", + "id":"1650", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"on", + "name":"track_counts", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Collects statistics on database activity.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1651", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"none", + "name":"track_functions", + "deprecated":"f", + "valid_vals":"none,pl,all", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Collects function-level statistics on database activity.", + "vartype":"enum", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1652", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"off", + "name":"track_io_timing", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Collects timing statistics for database I/O activity.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1653", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"off", + "name":"transaction_deferrable", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Whether to defer a read-only serializable transaction until it can be executed with no possible serialization failures.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1654", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"read committed", + "name":"transaction_isolation", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the current transaction's isolation level.", + "vartype":"string", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1655", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"off", + "name":"transaction_read_only", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the current transaction's read-only status.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1656", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"off", + "name":"transform_null_equals", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Treats expr=NULL as expr IS NULL.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1657", + "unit":"", + "description":"When turned on expressions of the form expr = NULL (or NULL = expr) are treated as expr IS NULL that is they return true if expr evaluates to the null value and false otherwise. The correct behavior of expr = NULL is to always return null (unknown)." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"/var/run/postgresql", + "name":"unix_socket_directories", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"f", + "rank":"-1", + "summary":"Sets the directories where Unix-domain sockets will be created.", + "vartype":"string", + "max_value":"", + "scope":"{Global}", + "id":"1658", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"", + "name":"unix_socket_group", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"", + "dynamic":"f", + "rank":"-1", + "summary":"Sets the owning group of the Unix-domain socket.", + "vartype":"string", + "max_value":"", + "scope":"{Global}", + "id":"1659", + "unit":"", + "description":"The owning user of the socket is always the user that starts the server." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"0777", + "name":"unix_socket_permissions", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"f", + "rank":"-1", + "summary":"Sets the access permissions of the Unix-domain socket.", + "vartype":"integer", + "max_value":"511", + "scope":"{Global}", + "id":"1660", + "unit":"", + "description":"Unix-domain sockets use the usual Unix file system permission set. The parameter value is expected to be a numeric mode specification in the form accepted by the chmod and umask system calls. (To use the customary octal format the number must start with a 0 (zero).)" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"on", + "name":"update_process_title", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Updates the process title to show the active SQL command.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1661", + "unit":"", + "description":"Enables updating of the process title every time a new SQL command is received by the server." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"0", + "name":"vacuum_cost_delay", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Vacuum cost delay in milliseconds.", + "vartype":"integer", + "max_value":"100", + "scope":"{GlobalSession}", + "id":"1662", + "unit":"ms", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"200", + "name":"vacuum_cost_limit", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"Vacuum cost amount available before napping.", + "vartype":"integer", + "max_value":"10000", + "scope":"{GlobalSession}", + "id":"1663", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"20", + "name":"vacuum_cost_page_dirty", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Vacuum cost for a page dirtied by vacuum.", + "vartype":"integer", + "max_value":"10000", + "scope":"{GlobalSession}", + "id":"1664", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"1", + "name":"vacuum_cost_page_hit", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Vacuum cost for a page found in the buffer cache.", + "vartype":"integer", + "max_value":"10000", + "scope":"{GlobalSession}", + "id":"1665", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"10", + "name":"vacuum_cost_page_miss", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Vacuum cost for a page not found in the buffer cache.", + "vartype":"integer", + "max_value":"10000", + "scope":"{GlobalSession}", + "id":"1666", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"", + "dangerous":"NO", + "default_val":"0", + "name":"vacuum_defer_cleanup_age", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Number of transactions by which VACUUM and HOT cleanup should be deferred if any.", + "vartype":"integer", + "max_value":"1000000", + "scope":"{Global}", + "id":"1667", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"50000000", + "name":"vacuum_freeze_min_age", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Minimum age at which VACUUM should freeze a table row.", + "vartype":"integer", + "max_value":"1000000000", + "scope":"{GlobalSession}", + "id":"1668", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"150000000", + "name":"vacuum_freeze_table_age", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Age at which VACUUM should scan whole table to freeze tuples.", + "vartype":"integer", + "max_value":"2000000000", + "scope":"{GlobalSession}", + "id":"1669", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"5000000", + "name":"vacuum_multixact_freeze_min_age", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Minimum age at which VACUUM should freeze a MultiXactId in a table row.", + "vartype":"integer", + "max_value":"1000000000", + "scope":"{GlobalSession}", + "id":"1670", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"150000000", + "name":"vacuum_multixact_freeze_table_age", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Multixact age at which VACUUM should scan whole table to freeze tuples.", + "vartype":"integer", + "max_value":"2000000000", + "scope":"{GlobalSession}", + "id":"1671", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"8192", + "name":"wal_block_size", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"8192", + "dynamic":"f", + "rank":"-1", + "summary":"Shows the block size in the write ahead log.", + "vartype":"integer", + "max_value":"8192", + "scope":"{NA}", + "id":"1672", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"YES", + "default_val":"minimal", + "name":"wal_level", + "deprecated":"f", + "valid_vals":"minimal,archive,hot_standby", + "dbms_id":"1", + "min_value":"", + "dynamic":"f", + "rank":"-1", + "summary":"Set the level of information written to the WAL.", + "vartype":"enum", + "max_value":"", + "scope":"{Global}", + "id":"1675", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"", + "dangerous":"NO", + "default_val":"10", + "name":"wal_receiver_status_interval", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the maximum interval between WAL receiver status reports to the primary.", + "vartype":"integer", + "max_value":"2147483", + "scope":"{Global}", + "id":"1676", + "unit":"s", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"", + "dangerous":"NO", + "default_val":"60000", + "name":"wal_receiver_timeout", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the maximum wait time to receive data from the primary.", + "vartype":"integer", + "max_value":"2147483647", + "scope":"{Global}", + "id":"1677", + "unit":"ms", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"2048", + "name":"wal_segment_size", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"2048", + "dynamic":"f", + "rank":"-1", + "summary":"Shows the number of pages per write ahead log segment.", + "vartype":"integer", + "max_value":"2048", + "scope":"{NA}", + "id":"1678", + "unit":"8kB", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"OTHER", + "safe_vals":"", + "dangerous":"NO", + "default_val":"60000", + "name":"wal_sender_timeout", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"0", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the maximum time to wait for WAL replication.", + "vartype":"integer", + "max_value":"2147483647", + "scope":"{Global}", + "id":"1679", + "unit":"ms", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"fdatasync", + "name":"wal_sync_method", + "deprecated":"f", + "valid_vals":"fsync,fdatasync,open_sync,open_datasync", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Selects the method used for forcing WAL updates to disk.", + "vartype":"enum", + "max_value":"", + "scope":"{Global}", + "id":"1680", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"200", + "name":"wal_writer_delay", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"1", + "dynamic":"t", + "rank":"-1", + "summary":"WAL writer sleep time between WAL flushes.", + "vartype":"integer", + "max_value":"10000", + "scope":"{Global}", + "id":"1681", + "unit":"ms", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"SYSTEM", + "safe_vals":"", + "dangerous":"NO", + "default_val":"1024", + "name":"work_mem", + "deprecated":"f", + "valid_vals":"", + "dbms_id":"1", + "min_value":"64", + "dynamic":"t", + "rank":"-1", + "summary":"Sets the maximum memory to be used for query workspaces.", + "vartype":"integer", + "max_value":"2147483647", + "scope":"{GlobalSession}", + "id":"1682", + "unit":"kB", + "description":"This much memory can be used by each internal sort operation and hash table before switching to temporary disk files." + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"base64", + "name":"xmlbinary", + "deprecated":"f", + "valid_vals":"base64,hex", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Sets how binary values are to be encoded in XML.", + "vartype":"enum", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1683", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"content", + "name":"xmloption", + "deprecated":"f", + "valid_vals":"content,document", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Sets whether XML data in implicit parsing and serialization operations is to be considered as documents or content fragments.", + "vartype":"enum", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1684", + "unit":"", + "description":"" + } + }, + { + "model":"website.Knob_catalog", + "fields":{ + "category":"NA", + "safe_vals":"", + "dangerous":"NO", + "default_val":"off", + "name":"zero_damaged_pages", + "deprecated":"f", + "valid_vals":"off,on", + "dbms_id":"1", + "min_value":"", + "dynamic":"t", + "rank":"-1", + "summary":"Continues processing past damaged page headers.", + "vartype":"bool", + "max_value":"", + "scope":"{GlobalSession}", + "id":"1685", + "unit":"", + "description":"Detection of a damaged page header normally causes PostgreSQL to report an error aborting the current transaction. Setting zero_damaged_pages to true causes the system to instead report a warning zero out the damaged page and continue processing. This behavior will destroy data namely all the rows on the damaged page." + } + } +] diff --git a/preload/metrics.json b/preload/metrics.json new file mode 100644 index 0000000..e321d51 --- /dev/null +++ b/preload/metrics.json @@ -0,0 +1,5332 @@ +[ + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Aborted_clientsThe number of connections that were aborted because the clientdied without closing the connection properly. SeeSection B.5.2.11 Communication Errors and Aborted Connections.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"1", + "name":"Aborted_clients" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Aborted_connectsThe number of failed attempts to connect to the MySQL server.See Section B.5.2.11 Communication Errors and Aborted Connections.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"2", + "name":"Aborted_connects" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Binlog_cache_disk_useThe number of transactions that used the binary log cache butthat exceeded the value ofbinlog_cache_size and used atemporary file to store changes from the transaction.In MySQL versions 5.5.3 through 5.5.8 this variable alsoincluded the number of nontransactional statements that causedthe binary log transaction cache to be written to disk.Beginning with MySQL 5.5.9 the number of suchnontransactional statements is tracked separately in theBinlog_stmt_cache_disk_usestatus variable.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"3", + "name":"Binlog_cache_disk_use" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Binlog_cache_useThe number of transactions that used the binary log cache.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"4", + "name":"Binlog_cache_use" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Binlog_stmt_cache_disk_useThe number of nontransaction statements that used the binarylog statement cache but that exceeded the value ofbinlog_stmt_cache_size andused a temporary file to store those statements.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"5", + "name":"Binlog_stmt_cache_disk_use" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Binlog_stmt_cache_useThe number of nontransactional statements that used the binarylog statement cache.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"6", + "name":"Binlog_stmt_cache_use" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Bytes_receivedThe number of bytes received from all clients.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"7", + "name":"Bytes_received" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Bytes_sentThe number of bytes sent to all clients.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"8", + "name":"Bytes_sent" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"9", + "name":"Com_admin_commands" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"10", + "name":"Com_alter_db" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"11", + "name":"Com_alter_db_upgrade" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"12", + "name":"Com_alter_event" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"13", + "name":"Com_alter_function" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"14", + "name":"Com_alter_procedure" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"15", + "name":"Com_alter_server" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"16", + "name":"Com_alter_table" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"17", + "name":"Com_alter_tablespace" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"18", + "name":"Com_analyze" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"19", + "name":"Com_assign_to_keycache" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"20", + "name":"Com_begin" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"21", + "name":"Com_binlog" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"22", + "name":"Com_call_procedure" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"23", + "name":"Com_change_db" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"24", + "name":"Com_change_master" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"25", + "name":"Com_check" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"26", + "name":"Com_checksum" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"27", + "name":"Com_commit" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"28", + "name":"Com_create_db" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"29", + "name":"Com_create_event" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"30", + "name":"Com_create_function" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"31", + "name":"Com_create_index" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"32", + "name":"Com_create_procedure" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"33", + "name":"Com_create_server" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"34", + "name":"Com_create_table" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"35", + "name":"Com_create_trigger" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"36", + "name":"Com_create_udf" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"37", + "name":"Com_create_user" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"38", + "name":"Com_create_view" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"39", + "name":"Com_dealloc_sql" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"40", + "name":"Com_delete" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"41", + "name":"Com_delete_multi" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"42", + "name":"Com_do" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"43", + "name":"Com_drop_db" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"44", + "name":"Com_drop_event" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"45", + "name":"Com_drop_function" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"46", + "name":"Com_drop_index" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"47", + "name":"Com_drop_procedure" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"48", + "name":"Com_drop_server" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"49", + "name":"Com_drop_table" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"50", + "name":"Com_drop_trigger" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"51", + "name":"Com_drop_user" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"52", + "name":"Com_drop_view" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"53", + "name":"Com_empty_query" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"54", + "name":"Com_execute_sql" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"55", + "name":"Com_flush" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"56", + "name":"Com_grant" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"57", + "name":"Com_ha_close" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"58", + "name":"Com_ha_open" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"59", + "name":"Com_ha_read" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"60", + "name":"Com_help" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"61", + "name":"Com_insert" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"62", + "name":"Com_insert_select" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"63", + "name":"Com_install_plugin" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"64", + "name":"Com_kill" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"65", + "name":"Com_load" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"66", + "name":"Com_lock_tables" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"67", + "name":"Com_optimize" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"68", + "name":"Com_preload_keys" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"69", + "name":"Com_prepare_sql" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"70", + "name":"Com_purge" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"71", + "name":"Com_purge_before_date" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"72", + "name":"Com_release_savepoint" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"73", + "name":"Com_rename_table" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"74", + "name":"Com_rename_user" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"75", + "name":"Com_repair" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"76", + "name":"Com_replace" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"77", + "name":"Com_replace_select" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"78", + "name":"Com_reset" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"79", + "name":"Com_resignal" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"80", + "name":"Com_revoke" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"81", + "name":"Com_revoke_all" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"82", + "name":"Com_rollback" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"83", + "name":"Com_rollback_to_savepoint" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"84", + "name":"Com_savepoint" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"85", + "name":"Com_select" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"86", + "name":"Com_set_option" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"87", + "name":"Com_show_authors" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"88", + "name":"Com_show_binlog_events" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"89", + "name":"Com_show_binlogs" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"90", + "name":"Com_show_charsets" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"91", + "name":"Com_show_collations" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"92", + "name":"Com_show_contributors" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"93", + "name":"Com_show_create_db" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"94", + "name":"Com_show_create_event" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"95", + "name":"Com_show_create_func" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"96", + "name":"Com_show_create_proc" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"97", + "name":"Com_show_create_table" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"98", + "name":"Com_show_create_trigger" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"99", + "name":"Com_show_databases" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"100", + "name":"Com_show_engine_logs" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"101", + "name":"Com_show_engine_mutex" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"102", + "name":"Com_show_engine_status" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"103", + "name":"Com_show_errors" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"104", + "name":"Com_show_events" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"105", + "name":"Com_show_fields" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"106", + "name":"Com_show_function_code" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"107", + "name":"Com_show_function_status" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"108", + "name":"Com_show_grants" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"109", + "name":"Com_show_keys" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"110", + "name":"Com_show_master_status" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"111", + "name":"Com_show_ndb_status" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"112", + "name":"Com_show_new_master" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"113", + "name":"Com_show_open_tables" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"114", + "name":"Com_show_plugins" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"115", + "name":"Com_show_privileges" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"116", + "name":"Com_show_procedure_code" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"117", + "name":"Com_show_procedure_status" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"118", + "name":"Com_show_processlist" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"119", + "name":"Com_show_profile" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"120", + "name":"Com_show_profiles" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"121", + "name":"Com_show_relaylog_events" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"122", + "name":"Com_show_slave_hosts" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"123", + "name":"Com_show_slave_status" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"124", + "name":"Com_show_status" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"125", + "name":"Com_show_storage_engines" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"126", + "name":"Com_show_table_status" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"127", + "name":"Com_show_tables" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"128", + "name":"Com_show_triggers" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"129", + "name":"Com_show_variables" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"130", + "name":"Com_show_warnings" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"131", + "name":"Com_signal" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"132", + "name":"Com_slave_start" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"133", + "name":"Com_slave_stop" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"134", + "name":"Com_stmt_close" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"135", + "name":"Com_stmt_execute" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"136", + "name":"Com_stmt_fetch" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"137", + "name":"Com_stmt_prepare" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"138", + "name":"Com_stmt_reprepare" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"139", + "name":"Com_stmt_reset" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"140", + "name":"Com_stmt_send_long_data" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"141", + "name":"Com_truncate" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"142", + "name":"Com_uninstall_plugin" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"143", + "name":"Com_unlock_tables" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"144", + "name":"Com_update" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"145", + "name":"Com_update_multi" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"146", + "name":"Com_xa_commit" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"147", + "name":"Com_xa_end" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"148", + "name":"Com_xa_prepare" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"149", + "name":"Com_xa_recover" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"150", + "name":"Com_xa_rollback" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"151", + "name":"Com_xa_start" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"CompressionWhether the client connection uses compression in theclient/server protocol.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{SESSION}", + "id":"152", + "name":"Compression" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"ConnectionsThe number of connection attempts (successful or not) to theMySQL server.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"153", + "name":"Connections" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Created_tmp_disk_tablesThe number of internal on-disk temporary tables created by theserver while executing statements.If an internal temporary table is created initially as anin-memory table but becomes too large MySQL automaticallyconverts it to an on-disk table. The maximum size forin-memory temporary tables is the minimum of thetmp_table_size andmax_heap_table_size values.If Created_tmp_disk_tablesis large you may want to increase thetmp_table_size ormax_heap_table_size value tolessen the likelihood that internal temporary tables in memorywill be converted to on-disk tables.You can compare the number of internal on-disk temporarytables created to the total number of internal temporarytables created by comparing the values of theCreated_tmp_disk_tables andCreated_tmp_tablesvariables.See also Section 8.4.4 Internal Temporary Table Use in MySQL.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"154", + "name":"Created_tmp_disk_tables" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Created_tmp_filesHow many temporary files mysqld hascreated.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"155", + "name":"Created_tmp_files" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Created_tmp_tablesThe number of internal temporary tables created by the serverwhile executing statements.You can compare the number of internal on-disk temporarytables created to the total number of internal temporarytables created by comparing the values of theCreated_tmp_disk_tables andCreated_tmp_tablesvariables.See also Section 8.4.4 Internal Temporary Table Use in MySQL.Each invocation of the SHOWSTATUS statement uses an internal temporary tableand increments the globalCreated_tmp_tables value.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"156", + "name":"Created_tmp_tables" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Delayed_errorsThe number of rows written with INSERTDELAYED for which some error occurred (probablyduplicate key).", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"157", + "name":"Delayed_errors" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Delayed_insert_threadsThe number of INSERT DELAYEDhandler threads in use.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"158", + "name":"Delayed_insert_threads" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Delayed_writesThe number of INSERT DELAYEDrows written.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"159", + "name":"Delayed_writes" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Flush_commandsThe number of times the server flushes tables whether becausea user executed a FLUSHTABLES statement or due to internal serveroperation. It is also incremented by receipt of aCOM_REFRESH packet. This is in contrast toCom_flushwhich indicates how many FLUSH statementshave been executed whetherFLUSH TABLESFLUSH LOGSand so forth.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"160", + "name":"Flush_commands" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Handler_commitThe number of internal COMMITstatements.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"161", + "name":"Handler_commit" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Handler_deleteThe number of times that rows have been deleted from tables.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"162", + "name":"Handler_delete" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"163", + "name":"Handler_discover" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Handler_prepareA counter for the prepare phase of two-phase commitoperations.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"164", + "name":"Handler_prepare" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Handler_read_firstThe number of times the first entry in an index was read. Ifthis value is high it suggests that the server is doing a lotof full index scans; for example SELECT col1 FROMfoo assuming that col1 isindexed.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"165", + "name":"Handler_read_first" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Handler_read_keyThe number of requests to read a row based on a key. If thisvalue is high it is a good indication that your tables areproperly indexed for your queries.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"166", + "name":"Handler_read_key" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Handler_read_lastThe number of requests to read the last key in an index. WithORDER BY the server will issue a first-keyrequest followed by several next-key requests whereas withORDER BY DESC the server will issue alast-key request followed by several previous-key requests.This variable was added in MySQL 5.5.7.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"167", + "name":"Handler_read_last" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"271", + "name":"Ndb_api_trans_commit_count_slave" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Handler_read_nextThe number of requests to read the next row in key order. Thisvalue is incremented if you are querying an index column witha range constraint or if you are doing an index scan.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"168", + "name":"Handler_read_next" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Handler_read_prevThe number of requests to read the previous row in key order.This read method is mainly used to optimize ORDER BY... DESC.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"169", + "name":"Handler_read_prev" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Handler_read_rndThe number of requests to read a row based on a fixedposition. This value is high if you are doing a lot of queriesthat require sorting of the result. You probably have a lot ofqueries that require MySQL to scan entire tables or you havejoins that do not use keys properly.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"170", + "name":"Handler_read_rnd" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Handler_read_rnd_nextThe number of requests to read the next row in the data file.This value is high if you are doing a lot of table scans.Generally this suggests that your tables are not properlyindexed or that your queries are not written to take advantageof the indexes you have.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"171", + "name":"Handler_read_rnd_next" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Handler_rollbackThe number of requests for a storage engine to perform arollback operation.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"172", + "name":"Handler_rollback" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Handler_savepointThe number of requests for a storage engine to place asavepoint.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"173", + "name":"Handler_savepoint" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Handler_savepoint_rollbackThe number of requests for a storage engine to roll back to asavepoint.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"174", + "name":"Handler_savepoint_rollback" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Handler_updateThe number of requests to update a row in a table.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"175", + "name":"Handler_update" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Handler_writeThe number of requests to insert a row in a table.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"176", + "name":"Handler_write" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_buffer_pool_bytes_dataThe total number of bytes in the InnoDBbuffer pool containingdata. The number includes bothdirty and clean pages.For more accurate memory usage calculations than withInnodb_buffer_pool_pages_datawhen compressed tablescause the buffer pool to hold pages of different sizes.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"177", + "name":"Innodb_buffer_pool_bytes_data" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_buffer_pool_bytes_dirtyThe total current number of bytes held indirty pages in theInnoDBbuffer pool. For moreaccurate memory usage calculations than withInnodb_buffer_pool_pages_dirtywhen compressed tablescause the buffer pool to hold pages of different sizes.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"178", + "name":"Innodb_buffer_pool_bytes_dirty" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_buffer_pool_pages_dataThe number of pages in theInnoDBbuffer pool containingdata. The number includes bothdirty and clean pages.When using compressedtables the reportedInnodb_buffer_pool_pages_datavalue may be larger thanInnodb_buffer_pool_pages_total(Bug #59550).", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"179", + "name":"Innodb_buffer_pool_pages_data" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_buffer_pool_pages_dirtyThe number of pages currently dirty.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"180", + "name":"Innodb_buffer_pool_pages_dirty" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_buffer_pool_pages_flushedThe number of buffer pool page-flush requests.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"181", + "name":"Innodb_buffer_pool_pages_flushed" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_buffer_pool_pages_freeThe number of free pages.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"182", + "name":"Innodb_buffer_pool_pages_free" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_buffer_pool_pages_latchedThe number of latched pages in InnoDBbuffer pool. These are pages currently being read or writtenor that cannot be flushed or removed for some other reason.Calculation of this variable is expensive so it is availableonly when the UNIV_DEBUG system is definedat server build time.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"183", + "name":"Innodb_buffer_pool_pages_latched" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_buffer_pool_pages_miscThe number of pages that are busy because they have beenallocated for administrative overhead such as row locks or theadaptive hash index. This value can also be calculated asInnodb_buffer_pool_pages_totalInnodb_buffer_pool_pages_freeInnodb_buffer_pool_pages_data.When using compressedtablesInnodb_buffer_pool_pages_miscmay report an out-of-bounds value (Bug #59550).", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"184", + "name":"Innodb_buffer_pool_pages_misc" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_buffer_pool_pages_totalThe total size of the InnoDBbuffer pool inpages. When usingcompressedtables the reportedInnodb_buffer_pool_pages_datavalue may be larger thanInnodb_buffer_pool_pages_total(Bug #59550)", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"185", + "name":"Innodb_buffer_pool_pages_total" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_buffer_pool_read_aheadThe number of pages read into the InnoDBbuffer pool by the read-ahead background thread.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"186", + "name":"Innodb_buffer_pool_read_ahead" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_buffer_pool_read_ahead_evictedThe number of pages read into the InnoDBbuffer pool by the read-ahead background thread that weresubsequently evicted without having been accessed by queries.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"187", + "name":"Innodb_buffer_pool_read_ahead_evicted" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_buffer_pool_read_requestsThe number of logical read requests.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"188", + "name":"Innodb_buffer_pool_read_requests" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_buffer_pool_readsThe number of logical reads that InnoDBcould not satisfy from the buffer pool and had to readdirectly from the disk.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"189", + "name":"Innodb_buffer_pool_reads" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"272", + "name":"Ndb_api_trans_local_read_row_count" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_buffer_pool_wait_freeNormally writes to the InnoDB buffer poolhappen in the background. However if it is necessary to reador create a page and no clean pages are available it is alsonecessary to wait for pages to be flushed first. This countercounts instances of these waits. If the buffer pool size hasbeen set properly this value should be small.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"190", + "name":"Innodb_buffer_pool_wait_free" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_buffer_pool_write_requestsThe number writes done to the InnoDB bufferpool.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"191", + "name":"Innodb_buffer_pool_write_requests" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_data_fsyncsThe number of fsync() operations so far.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"192", + "name":"Innodb_data_fsyncs" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_data_pending_fsyncsThe current number of pending fsync()operations.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"193", + "name":"Innodb_data_pending_fsyncs" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_data_pending_readsThe current number of pending reads.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"194", + "name":"Innodb_data_pending_reads" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_data_pending_writesThe current number of pending writes.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"195", + "name":"Innodb_data_pending_writes" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_data_readThe amount of data read since the server was started.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"196", + "name":"Innodb_data_read" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_data_readsThe total number of data reads.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"197", + "name":"Innodb_data_reads" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_data_writesThe total number of data writes.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"198", + "name":"Innodb_data_writes" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_data_writtenThe amount of data written so far in bytes.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"199", + "name":"Innodb_data_written" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_dblwr_pages_writtenThe number of pages that have been written for doublewriteoperations. See Section 14.13.1 InnoDB Disk I/O.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"200", + "name":"Innodb_dblwr_pages_written" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_dblwr_writesThe number of doublewrite operations that have been performed.See Section 14.13.1 InnoDB Disk I/O.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"201", + "name":"Innodb_dblwr_writes" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_have_atomic_builtinsIndicates whether the server was built with atomicinstructions.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"202", + "name":"Innodb_have_atomic_builtins" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_log_waitsThe number of times that the log buffer was too small and await was required for it to be flushed before continuing.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"203", + "name":"Innodb_log_waits" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_log_write_requestsThe number of log write requests.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"204", + "name":"Innodb_log_write_requests" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_log_writesThe number of physical writes to the log file.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"205", + "name":"Innodb_log_writes" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_os_log_fsyncsThe number of fsync() writes done to thelog file.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"206", + "name":"Innodb_os_log_fsyncs" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_os_log_pending_fsyncsThe number of pending log file fsync()operations.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"207", + "name":"Innodb_os_log_pending_fsyncs" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_os_log_pending_writesThe number of pending log file writes.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"208", + "name":"Innodb_os_log_pending_writes" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_os_log_writtenThe number of bytes written to the log file.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"209", + "name":"Innodb_os_log_written" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_page_sizeThe compiled-in InnoDB page size (default16KB). Many values are counted in pages; the page size enablesthem to be easily converted to bytes.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"210", + "name":"Innodb_page_size" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_pages_createdThe number of pages created.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"211", + "name":"Innodb_pages_created" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_pages_readThe number of pages read.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"212", + "name":"Innodb_pages_read" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_pages_writtenThe number of pages written.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"213", + "name":"Innodb_pages_written" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_row_lock_current_waitsThe number of row locks currently being waited for.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"214", + "name":"Innodb_row_lock_current_waits" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_row_lock_timeThe total time spent in acquiring row locks in milliseconds.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"215", + "name":"Innodb_row_lock_time" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_row_lock_time_avgThe average time to acquire a row lock in milliseconds.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"216", + "name":"Innodb_row_lock_time_avg" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_row_lock_time_maxThe maximum time to acquire a row lock in milliseconds.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"217", + "name":"Innodb_row_lock_time_max" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_row_lock_waitsThe number of times a row lock had to be waited for.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"218", + "name":"Innodb_row_lock_waits" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_rows_deletedThe number of rows deleted from InnoDBtables.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"219", + "name":"Innodb_rows_deleted" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_rows_insertedThe number of rows inserted into InnoDBtables.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"220", + "name":"Innodb_rows_inserted" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_rows_readThe number of rows read from InnoDB tables.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"221", + "name":"Innodb_rows_read" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_rows_updatedThe number of rows updated in InnoDBtables.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"222", + "name":"Innodb_rows_updated" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{SESSION}", + "id":"273", + "name":"Ndb_api_trans_local_read_row_count_session" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"274", + "name":"Ndb_api_trans_local_read_row_count_slave" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Innodb_truncated_status_writesThe number of times output from the SHOW ENGINEINNODB STATUS is truncated. Monitoring applicationsthat parse the output from this command can test this valuebefore and after issuing the SHOW ENGINEcommand to confirm if the output is complete or not.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"223", + "name":"Innodb_truncated_status_writes" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Key_blocks_not_flushedThe number of key blocks in the key cache that have changedbut have not yet been flushed to disk.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"224", + "name":"Key_blocks_not_flushed" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Key_blocks_unusedThe number of unused blocks in the key cache. You can use thisvalue to determine how much of the key cache is in use; seethe discussion ofkey_buffer_size inSection 5.1.4 Server System Variables.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"225", + "name":"Key_blocks_unused" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Key_blocks_usedThe number of used blocks in the key cache. This value is ahigh-water mark that indicates the maximum number of blocksthat have ever been in use at one time.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"226", + "name":"Key_blocks_used" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Key_read_requestsThe number of requests to read a key block from the cache.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"227", + "name":"Key_read_requests" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Key_readsThe number of physical reads of a key block from disk. IfKey_reads is large thenyour key_buffer_size value isprobably too small. The cache miss rate can be calculated asKey_reads/Key_read_requests.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"228", + "name":"Key_reads" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Key_write_requestsThe number of requests to write a key block to the cache.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"229", + "name":"Key_write_requests" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Key_writesThe number of physical writes of a key block to disk.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"230", + "name":"Key_writes" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Last_query_costThe total cost of the last compiled query as computed by thequery optimizer. This is useful for comparing the cost ofdifferent query plans for the same query. The default value of0 means that no query has been compiled yet. The default valueis 0. Last_query_cost hassession scope.The Last_query_cost valuecan be computed accurately only for simple flatqueries not complex queries such as those with subqueries orUNION. For the latter thevalue is set to 0.", + "dbms_id":"2", + "featured":"f", + "vartype":"numeric", + "scope":"{SESSION}", + "id":"231", + "name":"Last_query_cost" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Max_used_connectionsThe maximum number of connections that have been in usesimultaneously since the server started.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"232", + "name":"Max_used_connections" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"233", + "name":"Ndb_api_bytes_received_count" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{SESSION}", + "id":"234", + "name":"Ndb_api_bytes_received_count_session" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"235", + "name":"Ndb_api_bytes_received_count_slave" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"236", + "name":"Ndb_api_bytes_sent_count" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{SESSION}", + "id":"237", + "name":"Ndb_api_bytes_sent_count_session" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"238", + "name":"Ndb_api_bytes_sent_count_slave" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"239", + "name":"Ndb_api_event_bytes_count" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"240", + "name":"Ndb_api_event_bytes_count_injector" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"241", + "name":"Ndb_api_event_data_count" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"242", + "name":"Ndb_api_event_data_count_injector" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"243", + "name":"Ndb_api_event_nondata_count" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"244", + "name":"Ndb_api_event_nondata_count_injector" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"245", + "name":"Ndb_api_pk_op_count" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{SESSION}", + "id":"246", + "name":"Ndb_api_pk_op_count_session" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"247", + "name":"Ndb_api_pk_op_count_slave" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"248", + "name":"Ndb_api_pruned_scan_count" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{SESSION}", + "id":"249", + "name":"Ndb_api_pruned_scan_count_session" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"250", + "name":"Ndb_api_pruned_scan_count_slave" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"251", + "name":"Ndb_api_range_scan_count" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{SESSION}", + "id":"252", + "name":"Ndb_api_range_scan_count_session" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"253", + "name":"Ndb_api_range_scan_count_slave" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"254", + "name":"Ndb_api_read_row_count" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{SESSION}", + "id":"255", + "name":"Ndb_api_read_row_count_session" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"256", + "name":"Ndb_api_read_row_count_slave" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"257", + "name":"Ndb_api_scan_batch_count" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{SESSION}", + "id":"258", + "name":"Ndb_api_scan_batch_count_session" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"259", + "name":"Ndb_api_scan_batch_count_slave" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"260", + "name":"Ndb_api_table_scan_count" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{SESSION}", + "id":"261", + "name":"Ndb_api_table_scan_count_session" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"262", + "name":"Ndb_api_table_scan_count_slave" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"263", + "name":"Ndb_api_trans_abort_count" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{SESSION}", + "id":"264", + "name":"Ndb_api_trans_abort_count_session" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"265", + "name":"Ndb_api_trans_abort_count_slave" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"266", + "name":"Ndb_api_trans_close_count" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{SESSION}", + "id":"267", + "name":"Ndb_api_trans_close_count_session" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"268", + "name":"Ndb_api_trans_close_count_slave" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"269", + "name":"Ndb_api_trans_commit_count" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{SESSION}", + "id":"270", + "name":"Ndb_api_trans_commit_count_session" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"275", + "name":"Ndb_api_trans_start_count" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{SESSION}", + "id":"276", + "name":"Ndb_api_trans_start_count_session" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"277", + "name":"Ndb_api_trans_start_count_slave" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"278", + "name":"Ndb_api_uk_op_count" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{SESSION}", + "id":"279", + "name":"Ndb_api_uk_op_count_session" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"280", + "name":"Ndb_api_uk_op_count_slave" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"281", + "name":"Ndb_api_wait_exec_complete_count" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{SESSION}", + "id":"282", + "name":"Ndb_api_wait_exec_complete_count_session" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"283", + "name":"Ndb_api_wait_exec_complete_count_slave" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"284", + "name":"Ndb_api_wait_meta_request_count" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{SESSION}", + "id":"285", + "name":"Ndb_api_wait_meta_request_count_session" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"286", + "name":"Ndb_api_wait_meta_request_count_slave" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"287", + "name":"Ndb_api_wait_nanos_count" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{SESSION}", + "id":"288", + "name":"Ndb_api_wait_nanos_count_session" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"289", + "name":"Ndb_api_wait_nanos_count_slave" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"290", + "name":"Ndb_api_wait_scan_result_count" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{SESSION}", + "id":"291", + "name":"Ndb_api_wait_scan_result_count_session" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"292", + "name":"Ndb_api_wait_scan_result_count_slave" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"293", + "name":"Ndb_cluster_node_id" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"294", + "name":"Ndb_config_from_host" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"295", + "name":"Ndb_config_from_port" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"296", + "name":"Ndb_conflict_fn_epoch" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"297", + "name":"Ndb_conflict_fn_epoch_trans" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"298", + "name":"Ndb_conflict_fn_max" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"299", + "name":"Ndb_conflict_fn_old" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"300", + "name":"Ndb_conflict_trans_conflict_commit_count" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"301", + "name":"Ndb_conflict_trans_detect_iter_count" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"302", + "name":"Ndb_conflict_trans_reject_count" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"303", + "name":"Ndb_conflict_trans_row_reject_count" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"304", + "name":"Ndb_execute_count" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"305", + "name":"Ndb_number_of_data_nodes" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"306", + "name":"Ndb_pruned_scan_count" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"307", + "name":"Ndb_pushed_queries_defined" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"308", + "name":"Ndb_pushed_queries_dropped" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"309", + "name":"Ndb_pushed_queries_executed" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"310", + "name":"Ndb_pushed_reads" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"311", + "name":"Ndb_scan_count" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Not_flushed_delayed_rowsThe number of rows waiting to be written inINSERT DELAYED queues.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"312", + "name":"Not_flushed_delayed_rows" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Open_filesThe number of files that are open. This count includes regularfiles opened by the server. It does not include other types offiles such as sockets or pipes. Also the count does notinclude files that storage engines open using their owninternal functions rather than asking the server level to doso.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"313", + "name":"Open_files" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Open_streamsThe number of streams that are open (used mainly for logging).", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"314", + "name":"Open_streams" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Open_table_definitionsThe number of cached .frm files.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"315", + "name":"Open_table_definitions" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Open_tablesThe number of tables that are open.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"316", + "name":"Open_tables" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Opened_filesThe number of files that have been opened withmy_open() (a mysyslibrary function). Parts of the server that open files withoutusing this function do not increment the count.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"317", + "name":"Opened_files" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Opened_table_definitionsThe number of .frm files that have beencached.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"318", + "name":"Opened_table_definitions" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Opened_tablesThe number of tables that have been opened. IfOpened_tables is big yourtable_open_cache value isprobably too small.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"319", + "name":"Opened_tables" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"320", + "name":"Performance_schema_cond_classes_lost" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"321", + "name":"Performance_schema_cond_instances_lost" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"322", + "name":"Performance_schema_file_classes_lost" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"323", + "name":"Performance_schema_file_handles_lost" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"324", + "name":"Performance_schema_file_instances_lost" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"325", + "name":"Performance_schema_locker_lost" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"326", + "name":"Performance_schema_mutex_classes_lost" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"327", + "name":"Performance_schema_mutex_instances_lost" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"328", + "name":"Performance_schema_rwlock_classes_lost" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"329", + "name":"Performance_schema_rwlock_instances_lost" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"330", + "name":"Performance_schema_table_handles_lost" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"331", + "name":"Performance_schema_table_instances_lost" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"332", + "name":"Performance_schema_thread_classes_lost" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"NULL", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"333", + "name":"Performance_schema_thread_instances_lost" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Prepared_stmt_countThe current number of prepared statements. (The maximum numberof statements is given by themax_prepared_stmt_countsystem variable.)", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"334", + "name":"Prepared_stmt_count" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Qcache_free_blocksThe number of free memory blocks in the query cache.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"335", + "name":"Qcache_free_blocks" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Qcache_free_memoryThe amount of free memory for the query cache.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"336", + "name":"Qcache_free_memory" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Qcache_hitsThe number of query cache hits.The discussion at the beginning of this section indicates howto relate this statement-counting status variable to othersuch variables.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"337", + "name":"Qcache_hits" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Qcache_insertsThe number of queries added to the query cache.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"338", + "name":"Qcache_inserts" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Qcache_lowmem_prunesThe number of queries that were deleted from the query cachebecause of low memory.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"339", + "name":"Qcache_lowmem_prunes" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Qcache_not_cachedThe number of noncached queries (not cacheable or not cacheddue to the query_cache_typesetting).", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"340", + "name":"Qcache_not_cached" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Qcache_queries_in_cacheThe number of queries registered in the query cache.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"341", + "name":"Qcache_queries_in_cache" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Qcache_total_blocksThe total number of blocks in the query cache.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"342", + "name":"Qcache_total_blocks" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"QueriesThe number of statements executed by the server. This variableincludes statements executed within stored programs unlikethe Questions variable. Itdoes not count COM_PING orCOM_STATISTICS commands.The discussion at the beginning of this section indicates howto relate this statement-counting status variable to othersuch variables.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"343", + "name":"Queries" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"QuestionsThe number of statements executed by the server. This includesonly statements sent to the server by clients and notstatements executed within stored programs unlike theQueries variable. Thisvariable does not count COM_PINGCOM_STATISTICSCOM_STMT_PREPARECOM_STMT_CLOSE orCOM_STMT_RESET commands.The discussion at the beginning of this section indicates howto relate this statement-counting status variable to othersuch variables.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"344", + "name":"Questions" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Rpl_semi_sync_master_clientsThe number of semisynchronous slaves.This variable is available only if the master-sidesemisynchronous replication plugin is installed.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"345", + "name":"Rpl_semi_sync_master_clients" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Rpl_semi_sync_master_net_avg_wait_timeThe average time in microseconds the master waited for a slavereply.This variable is available only if the master-sidesemisynchronous replication plugin is installed.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"346", + "name":"Rpl_semi_sync_master_net_avg_wait_time" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Rpl_semi_sync_master_net_wait_timeThe total time in microseconds the master waited for slavereplies.This variable is available only if the master-sidesemisynchronous replication plugin is installed.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"347", + "name":"Rpl_semi_sync_master_net_wait_time" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Rpl_semi_sync_master_net_waitsThe total number of times the master waited for slave replies.This variable is available only if the master-sidesemisynchronous replication plugin is installed.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"348", + "name":"Rpl_semi_sync_master_net_waits" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Rpl_semi_sync_master_no_timesThe number of times the master turned off semisynchronousreplication.This variable is available only if the master-sidesemisynchronous replication plugin is installed.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"349", + "name":"Rpl_semi_sync_master_no_times" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Rpl_semi_sync_master_no_txThe number of commits that were not acknowledged successfullyby a slave.This variable is available only if the master-sidesemisynchronous replication plugin is installed.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"350", + "name":"Rpl_semi_sync_master_no_tx" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Rpl_semi_sync_master_statusWhether semisynchronous replication currently is operationalon the master. The value is ON if theplugin has been enabled and a commit acknowledgment hasoccurred. It is OFF if the plugin is notenabled or the master has fallen back to asynchronousreplication due to commit acknowledgment timeout.This variable is available only if the master-sidesemisynchronous replication plugin is installed.", + "dbms_id":"2", + "featured":"f", + "vartype":"boolean", + "scope":"{GLOBAL}", + "id":"351", + "name":"Rpl_semi_sync_master_status" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Rpl_semi_sync_master_timefunc_failuresThe number of times the master failed when calling timefunctions such as gettimeofday().This variable is available only if the master-sidesemisynchronous replication plugin is installed.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"352", + "name":"Rpl_semi_sync_master_timefunc_failures" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Rpl_semi_sync_master_tx_avg_wait_timeThe average time in microseconds the master waited for eachtransaction.This variable is available only if the master-sidesemisynchronous replication plugin is installed.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"353", + "name":"Rpl_semi_sync_master_tx_avg_wait_time" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Rpl_semi_sync_master_tx_wait_timeThe total time in microseconds the master waited fortransactions.This variable is available only if the master-sidesemisynchronous replication plugin is installed.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"354", + "name":"Rpl_semi_sync_master_tx_wait_time" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Rpl_semi_sync_master_tx_waitsThe total number of times the master waited for transactions.This variable is available only if the master-sidesemisynchronous replication plugin is installed.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"355", + "name":"Rpl_semi_sync_master_tx_waits" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Rpl_semi_sync_master_wait_pos_backtraverseThe total number of times the master waited for an event withbinary coordinates lower than events waited for previously.This can occur when the order in which transactions startwaiting for a reply is different from the order in which theirbinary log events are written.This variable is available only if the master-sidesemisynchronous replication plugin is installed.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"356", + "name":"Rpl_semi_sync_master_wait_pos_backtraverse" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Rpl_semi_sync_master_wait_sessionsThe number of sessions currently waiting for slave replies.This variable is available only if the master-sidesemisynchronous replication plugin is installed.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"357", + "name":"Rpl_semi_sync_master_wait_sessions" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Rpl_semi_sync_master_yes_txThe number of commits that were acknowledged successfully by aslave.This variable is available only if the master-sidesemisynchronous replication plugin is installed.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"358", + "name":"Rpl_semi_sync_master_yes_tx" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Rpl_semi_sync_slave_statusWhether semisynchronous replication currently is operationalon the slave. This is ON if the plugin hasbeen enabled and the slave I/O thread is runningOFF otherwise.This variable is available only if the slave-sidesemisynchronous replication plugin is installed.", + "dbms_id":"2", + "featured":"f", + "vartype":"boolean", + "scope":"{GLOBAL}", + "id":"359", + "name":"Rpl_semi_sync_slave_status" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Rpl_statusThe status of fail-safe replication (not implemented). Thisvariable is unused and is removed in MySQL 5.6.", + "dbms_id":"2", + "featured":"f", + "vartype":"string", + "scope":"{GLOBAL}", + "id":"360", + "name":"Rpl_status" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Select_full_joinThe number of joins that perform table scans because they donot use indexes. If this value is not 0 you should carefullycheck the indexes of your tables.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"361", + "name":"Select_full_join" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Select_full_range_joinThe number of joins that used a range search on a referencetable.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"362", + "name":"Select_full_range_join" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Select_rangeThe number of joins that used ranges on the first table. Thisis normally not a critical issue even if the value is quitelarge.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"363", + "name":"Select_range" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Select_range_checkThe number of joins without keys that check for key usageafter each row. If this is not 0 you should carefully checkthe indexes of your tables.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"364", + "name":"Select_range_check" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Select_scanThe number of joins that did a full scan of the first table.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"365", + "name":"Select_scan" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Slave_heartbeat_periodShows the replication heartbeat interval (in seconds) on areplication slave.", + "dbms_id":"2", + "featured":"f", + "vartype":"numeric", + "scope":"{GLOBAL}", + "id":"366", + "name":"Slave_heartbeat_period" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Slave_open_temp_tablesThe number of temporary tables that the slave SQL threadcurrently has open. If the value is greater than zero it isnot safe to shut down the slave; seeSection 17.4.1.24 Replication and Temporary Tables.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"367", + "name":"Slave_open_temp_tables" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Slave_received_heartbeatsThis counter increments with each replication heartbeatreceived by a replication slave since the last time that theslave was restarted or reset or a CHANGEMASTER TO statement was issued.", + "dbms_id":"2", + "featured":"f", + "vartype":"", + "scope":"{GLOBAL}", + "id":"368", + "name":"Slave_received_heartbeats" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Slave_retried_transactionsThe total number of times since startup that the replicationslave SQL thread has retried transactions.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"369", + "name":"Slave_retried_transactions" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Slave_runningThis is ON if this server is a replicationslave that is connected to a replication master and both theI/O and SQL threads are running; otherwise it isOFF.", + "dbms_id":"2", + "featured":"f", + "vartype":"boolean", + "scope":"{GLOBAL}", + "id":"370", + "name":"Slave_running" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Slow_launch_threadsThe number of threads that have taken more thanslow_launch_time seconds tocreate.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"371", + "name":"Slow_launch_threads" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Slow_queriesThe number of queries that have taken more thanlong_query_time seconds. Thiscounter increments regardless of whether the slow query log isenabled. For information about that log seeSection 5.4.5 The Slow Query Log.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"372", + "name":"Slow_queries" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Sort_merge_passesThe number of merge passes that the sort algorithm has had todo. If this value is large you should consider increasing thevalue of the sort_buffer_sizesystem variable.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"373", + "name":"Sort_merge_passes" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Sort_rangeThe number of sorts that were done using ranges.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"374", + "name":"Sort_range" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Sort_rowsThe number of sorted rows.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"375", + "name":"Sort_rows" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Sort_scanThe number of sorts that were done by scanning the table.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"376", + "name":"Sort_scan" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Threads_cachedThe number of threads in the thread cache.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"405", + "name":"Threads_cached" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Ssl_accept_renegotiatesThe number of negotiates needed to establish the connection.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"377", + "name":"Ssl_accept_renegotiates" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Ssl_acceptsThe number of accepted SSL connections.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"378", + "name":"Ssl_accepts" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Ssl_callback_cache_hitsThe number of callback cache hits.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"379", + "name":"Ssl_callback_cache_hits" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Ssl_cipherThe current encryption cipher (empty for unencryptedconnections).", + "dbms_id":"2", + "featured":"f", + "vartype":"string", + "scope":"{GLOBAL}", + "id":"380", + "name":"Ssl_cipher" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Ssl_cipher_listThe list of possible SSL ciphers (empty for non-SSLconnections).", + "dbms_id":"2", + "featured":"f", + "vartype":"string", + "scope":"{GLOBAL}", + "id":"381", + "name":"Ssl_cipher_list" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Ssl_client_connectsThe number of SSL connection attempts to an SSL-enabledmaster.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"382", + "name":"Ssl_client_connects" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Ssl_connect_renegotiatesThe number of negotiates needed to establish the connection toan SSL-enabled master.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"383", + "name":"Ssl_connect_renegotiates" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Ssl_ctx_verify_depthThe SSL context verification depth (how many certificates inthe chain are tested).", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"384", + "name":"Ssl_ctx_verify_depth" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Ssl_ctx_verify_modeThe SSL context verification mode.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"385", + "name":"Ssl_ctx_verify_mode" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Ssl_default_timeoutThe default SSL timeout.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"386", + "name":"Ssl_default_timeout" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Ssl_finished_acceptsThe number of successful SSL connections to the server.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"387", + "name":"Ssl_finished_accepts" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Ssl_finished_connectsThe number of successful slave connections to an SSL-enabledmaster.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"388", + "name":"Ssl_finished_connects" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Ssl_session_cache_hitsThe number of SSL session cache hits.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"389", + "name":"Ssl_session_cache_hits" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Ssl_session_cache_missesThe number of SSL session cache misses.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"390", + "name":"Ssl_session_cache_misses" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Ssl_session_cache_modeThe SSL session cache mode.", + "dbms_id":"2", + "featured":"f", + "vartype":"string", + "scope":"{GLOBAL}", + "id":"391", + "name":"Ssl_session_cache_mode" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Ssl_session_cache_overflowsThe number of SSL session cache overflows.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"392", + "name":"Ssl_session_cache_overflows" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Ssl_session_cache_sizeThe SSL session cache size.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"393", + "name":"Ssl_session_cache_size" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Ssl_session_cache_timeoutsThe number of SSL session cache timeouts.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"394", + "name":"Ssl_session_cache_timeouts" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Ssl_sessions_reusedHow many SSL connections were reused from the cache.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"395", + "name":"Ssl_sessions_reused" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Ssl_used_session_cache_entriesHow many SSL session cache entries were used.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"396", + "name":"Ssl_used_session_cache_entries" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Ssl_verify_depthThe verification depth for replication SSL connections.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"397", + "name":"Ssl_verify_depth" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Ssl_verify_modeThe verification mode for replication SSL connections.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"398", + "name":"Ssl_verify_mode" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Ssl_versionThe SSL protocol version of the connection; for exampleTLSv1. If the connection is not encrypted the value is empty.", + "dbms_id":"2", + "featured":"f", + "vartype":"string", + "scope":"{GLOBAL}", + "id":"399", + "name":"Ssl_version" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Table_locks_immediateThe number of times that a request for a table lock could begranted immediately.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"400", + "name":"Table_locks_immediate" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Table_locks_waitedThe number of times that a request for a table lock could notbe granted immediately and a wait was needed. If this is highand you have performance problems you should first optimizeyour queries and then either split your table or tables oruse replication.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"401", + "name":"Table_locks_waited" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Tc_log_max_pages_usedFor the memory-mapped implementation of the log that is usedby mysqld when it acts as the transactioncoordinator for recovery of internal XA transactions thisvariable indicates the largest number of pages used for thelog since the server started. If the product ofTc_log_max_pages_used andTc_log_page_size is alwayssignificantly less than the log size the size is larger thannecessary and can be reduced. (The size is set by the--log-tc-size option. Thisvariable is unused: It is unneeded for binary log-basedrecovery and the memory-mapped recovery log method is notused unless the number of storage engines that are capable oftwo-phase commit and that support XA transactions is greaterthan one. (InnoDB is the only applicableengine.)", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"402", + "name":"Tc_log_max_pages_used" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Tc_log_page_sizeThe page size used for the memory-mapped implementation of theXA recovery log. The default value is determined usinggetpagesize(). This variable is unused forthe same reasons as described forTc_log_max_pages_used.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"403", + "name":"Tc_log_page_size" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Tc_log_page_waitsFor the memory-mapped implementation of the recovery log thisvariable increments each time the server was not able tocommit a transaction and had to wait for a free page in thelog. If this value is large you might want to increase thelog size (with the--log-tc-size option). Forbinary log-based recovery this variable increments each timethe binary log cannot be closed because there are two-phasecommits in progress. (The close operation waits until all suchtransactions are finished.)", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"404", + "name":"Tc_log_page_waits" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Threads_connectedThe number of currently open connections.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"406", + "name":"Threads_connected" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Threads_createdThe number of threads created to handle connections. IfThreads_created is big youmay want to increase thethread_cache_size value. Thecache miss rate can be calculated asThreads_created/Connections.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"407", + "name":"Threads_created" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Threads_runningThe number of threads that are not sleeping.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"408", + "name":"Threads_running" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"UptimeThe number of seconds that the server has been up.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"409", + "name":"Uptime" + } + }, + { + "model":"website.Metric_catalog", + "fields":{ + "scale":"GLOBAL", + "description":"Uptime_since_flush_statusThe number of seconds since the most recent FLUSHSTATUS statement.", + "dbms_id":"2", + "featured":"f", + "vartype":"integer", + "scope":"{GLOBAL}", + "id":"410", + "name":"Uptime_since_flush_status" + } + } +] \ No newline at end of file diff --git a/preload/mysql_knobs.json b/preload/mysql_knobs.json new file mode 100644 index 0000000..dc173fc --- /dev/null +++ b/preload/mysql_knobs.json @@ -0,0 +1,303 @@ +[ + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"expire_logs_days" + } + }, + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"innodb_adaptive_flushing" + } + }, + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"innodb_adaptive_max_sleep_delay" + } + }, + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"innodb_autoextend_increment" + } + }, + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"innodb_buffer_pool_instances" + } + }, + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"innodb_buffer_pool_size" + } + }, + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"innodb_change_buffer_max_size" + } + }, + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"innodb_change_buffering" + } + }, + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"innodb_commit_concurrency" + } + }, + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"innodb_compression_level" + } + }, + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"innodb_concurrency_tickets" + } + }, + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"innodb_flush_log_at_timeout" + } + }, + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"innodb_flush_method" + } + }, + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"innodb_flush_neighbors" + } + }, + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"innodb_io_capacity" + } + }, + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"innodb_io_capacity_max" + } + }, + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"innodb_lock_wait_timeout" + } + }, + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"innodb_log_buffer_size" + } + }, + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"innodb_log_file_size" + } + }, + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"innodb_log_files_in_group" + } + }, + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"innodb_lru_scan_depth" + } + }, + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"innodb_max_dirty_pages_pct" + } + }, + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"innodb_max_dirty_pages_pct_lwm" + } + }, + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"innodb_old_blocks_pct" + } + }, + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"innodb_old_blocks_time" + } + }, + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"innodb_random_read_ahead" + } + }, + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"innodb_read_ahead_threshold" + } + }, + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"innodb_read_io_threads" + } + }, + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"innodb_sort_buffer_size" + } + }, + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"innodb_spin_wait_delay" + } + }, + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"innodb_stats_transient_sample_pages" + } + }, + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"innodb_sync_array_size" + } + }, + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"innodb_thread_concurrency" + } + }, + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"innodb_thread_sleep_delay" + } + }, + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"innodb_write_io_threads" + } + }, + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"join_buffer_size" + } + }, + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"key_buffer_size" + } + }, + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"max_heap_table_size" + } + }, + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"sort_buffer_size" + } + }, + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"table_open_cache" + } + }, + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"thread_cache_size" + } + }, + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"timed_mutexes" + } + }, + { + "model":"website.KNOB_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"tmp_table_size" + } + } +] \ No newline at end of file diff --git a/preload/pre-data.json b/preload/pre-data.json new file mode 100644 index 0000000..d31e32c --- /dev/null +++ b/preload/pre-data.json @@ -0,0 +1,136 @@ +[ + { + "model":"website.Website_Conf", + "fields":{ + "name":"Time_Limit", + "value":"300" + } + }, + { + "model":"website.LEARNING_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"innodb_buffer_pool_size" + } + }, + { + "model":"website.LEARNING_PARAMS", + "fields": + { + "db_type":"MYSQL", + "params":"innodb_buffer_pool_instances" + } + }, + { + "model":"website.LEARNING_PARAMS", + "fields": + { + "db_type":"MYSQL", + "params":"innodb_log_file_size" + } + }, + { + "model":"website.LEARNING_PARAMS", + "fields": + { + "db_type":"MYSQL", + "params":"innodb_log_buffer_size" + } + }, + { + "model":"website.LEARNING_PARAMS", + "fields": + { + "db_type":"MYSQL", + "params":"innodb_thread_concurrency" + } + }, + + { + "model":"website.FEATURED_PARAMS", + "fields":{ + "db_type":"MYSQL", + "params":"innodb_buffer_pool_size" + } + }, + { + "model":"website.FEATURED_PARAMS", + "fields": + { + "db_type":"MYSQL", + "params":"innodb_buffer_pool_instances" + } + }, + { + "model":"website.FEATURED_PARAMS", + "fields": + { + "db_type":"MYSQL", + "params":"innodb_log_file_size" + } + }, + { + "model":"website.FEATURED_PARAMS", + "fields": + { + "db_type":"MYSQL", + "params":"innodb_log_buffer_size" + } + }, + { + "model":"website.FEATURED_PARAMS", + "fields": + { + "db_type":"MYSQL", + "params":"innodb_flush_log_at_trx_commit" + } + }, + { + "model":"website.FEATURED_PARAMS", + "fields": + { + "db_type":"MYSQL", + "params":"innodb_thread_concurrency" + } + }, + { + "model":"website.FEATURED_PARAMS", + "fields": + { + "db_type":"MYSQL", + "params":"innodb_file_per_table" + } + }, + { + "model":"website.FEATURED_PARAMS", + "fields": + { + "db_type":"MYSQL", + "params":"key_buffer_size" + } + }, + { + "model":"website.FEATURED_PARAMS", + "fields": + { + "db_type":"MYSQL", + "params":"table_cache" + } + }, + { + "model":"website.FEATURED_PARAMS", + "fields": + { + "db_type":"MYSQL", + "params":"thread_cache" + } + }, + { + "model":"website.FEATURED_PARAMS", + "fields": + { + "db_type":"MYSQL", + "params":"query_cache_size" + } + } +] diff --git a/requirements.txt b/requirements.txt new file mode 100644 index 0000000..3072f8a --- /dev/null +++ b/requirements.txt @@ -0,0 +1,5 @@ +celery==3.1.23 +Django==1.10.1 +django-celery==3.1.17 +django-debug-toolbar==1.5 +mysqlclient==1.3.7 diff --git a/scripts/__init__.py b/scripts/__init__.py new file mode 100644 index 0000000..e69de29 diff --git a/scripts/config_nightly_email.py b/scripts/config_nightly_email.py new file mode 100644 index 0000000..5e8da13 --- /dev/null +++ b/scripts/config_nightly_email.py @@ -0,0 +1,16 @@ +# Enter the email-id of all the recepients here +recepients=[] + +# Enter the DB-BENCH pairs that need to be reported. +# All names should be in upper-case. +db_bench_configs = [ + ('PELOTON', 'TPCC'), + ('POSTGRES', 'TPCC') +] + +# Enter all the attributes of Result model that +# need to be reported, paired with units +result_attributes = [ + ('throughput', 'rps'), + ('avg_latency', 'ms') +] diff --git a/scripts/nightly_email.py b/scripts/nightly_email.py new file mode 100644 index 0000000..0f8da51 --- /dev/null +++ b/scripts/nightly_email.py @@ -0,0 +1,79 @@ +import scripts.config_nightly_email as config +from django.core.validators import validate_email +from django.core.exceptions import ValidationError + +from website.models import Result +from tabulate import tabulate + +from django.core.mail import EmailMultiAlternatives + +import sys +import pprint + +EMAIL_SUBJECT = 'Nightly Benchmark Results' +FROM_ADDRESS = 'webmaster@pelotodb.io' + +# Identify attr value has increased or decreased +def evaluate_res(attr, res_list): + status = 'Decreased' + if getattr(res_list[0], attr) > getattr(res_list[1], attr): + status = 'Increased' + return status + ' ' + attr.capitalize() + +def make_report_table_row(res, attr): + return [res.creation_time, getattr(res, attr)] + +# Generate the report for db_bench +def get_db_bench_report(db_bench, res_list): + report = [] + db_bench_str = pprint.pformat(db_bench) + dashes = '='*len(db_bench_str) + report.extend(('\n', dashes, db_bench_str, dashes)) + for (attr,units) in config.result_attributes: + attr_units_str = attr + ' (' + units + ')' + header = evaluate_res(attr, res_list) + report.extend(('\n'+header, '-'*len(header))) + report.append(tabulate( + [['current']+make_report_table_row(res_list[0], attr), + ['previous']+make_report_table_row(res_list[1], attr)], + headers = ['', 'Completion Timestamp', attr_units_str.capitalize()], + tablefmt='psql')) + return report + +def send_email(email_body, recepients): + text_body = "\n".join(email_body) + html_body = "
\n" + text_body + "\n" + print text_body + email = EmailMultiAlternatives( + EMAIL_SUBJECT, + text_body, + FROM_ADDRESS, + to=recepients) + email.attach_alternative(html_body, "text/html") + email.send() + +def main(): + email_body = [] + try: + map(validate_email, config.recepients) + except ValidationError: + print 'Enter valid email_ids in config_nightly_email.py' + sys.exit(1) + for db_bench in config.db_bench_configs: + try: + # retrieve the latest two results + res = Result.objects.filter( + db_conf__db_type=db_bench[0], + benchmark_conf__benchmark_type=db_bench[1] + ).order_by('-creation_time')[:2] + report = get_db_bench_report(db_bench, res) + except: + print 'Insufficient data for ' + str(db_bench) + continue + email_body += report + print '\n' + # send email only if there is a body + if len(email_body) > 0: + send_email(email_body, config.recepients) + +main() diff --git a/tools/mysql_knob.txt b/tools/mysql_knob.txt new file mode 100644 index 0000000..7448e8e --- /dev/null +++ b/tools/mysql_knob.txt @@ -0,0 +1,43 @@ +expire_logs_days +innodb_adaptive_flushing +innodb_adaptive_max_sleep_delay +innodb_autoextend_increment +innodb_buffer_pool_instances +innodb_buffer_pool_size +innodb_change_buffer_max_size +innodb_change_buffering +innodb_commit_concurrency +innodb_compression_level +innodb_concurrency_tickets +innodb_flush_log_at_timeout +innodb_flush_method +innodb_flush_neighbors +innodb_io_capacity +innodb_io_capacity_max +innodb_lock_wait_timeout +innodb_log_buffer_size +innodb_log_file_size +innodb_log_files_in_group +innodb_lru_scan_depth +innodb_max_dirty_pages_pct +innodb_max_dirty_pages_pct_lwm +innodb_old_blocks_pct +innodb_old_blocks_time +innodb_random_read_ahead +innodb_read_ahead_threshold +innodb_read_io_threads +innodb_sort_buffer_size +innodb_spin_wait_delay +innodb_stats_transient_sample_pages +innodb_sync_array_size +innodb_thread_concurrency +innodb_thread_sleep_delay +innodb_write_io_threads +join_buffer_size +key_buffer_size +max_heap_table_size +sort_buffer_size +table_open_cache +thread_cache_size +timed_mutexes +tmp_table_size diff --git a/tools/process_knob.py b/tools/process_knob.py new file mode 100644 index 0000000..beacfe9 --- /dev/null +++ b/tools/process_knob.py @@ -0,0 +1,23 @@ +f = open('mysql_knob.txt','r+') +data = f.readlines() +f.close() + +f = open('mysql_knobs.json','w') + + +f.write("[\n") + +l = 0 +for x in data: + x = x.replace("\n","") + l += 1 + f.write(" {\n \"model\":\"website.KNOB_PARAMS\",\n \"fields\":{\n") + f.write(" \""+"db_type"+ "\":\"" +"MYSQL" + "\",\n") + f.write(" \"params" + "\":\"" + str(x) + "\"\n") + if l == len(data): + f.write(" }\n }\n") + else: + f.write(" }\n },\n") +f.write("]") + +f.close() diff --git a/tools/upload.py b/tools/upload.py new file mode 100644 index 0000000..31de940 --- /dev/null +++ b/tools/upload.py @@ -0,0 +1,30 @@ +from poster.encode import multipart_encode +from poster.streaminghttp import register_openers +import urllib2 + +register_openers() + +db="mysql_" +prefix=3 + +params = { +'summary_data': open(db + str(prefix) + ".summary", "r"), +'db_conf_data':open(db + str(prefix) + ".db.cnf","r"), +'db_status':open(db + str(prefix) + ".db.status",'r'), +'sample_data':open(db + str(prefix)+".res","r"), +'raw_data': open(db + str(prefix)+".res","r"), +'benchmark_conf_data': open(db + str(prefix)+".ben.cnf","r"), +'upload_code': '14414QYEORPR4CE52X20', +'upload_use':'compute', +#'store', +'hardware':'m3.xlarge', +'cluster':'exps_mysql_5.6_m3.xlarge_ycsb_rr_sf18000_tr50_t300_runlimited_w0-0-0-100-0-0_s0.6' #unknown + +} + +datagen, headers = multipart_encode(params) + +#request = urllib2.Request("http://127.0.0.1:8000/new_result/", datagen, headers) +request = urllib2.Request("http://52.26.247.195:8000/new_result/", datagen, headers) + +print urllib2.urlopen(request).read() diff --git a/tools/upload.sh b/tools/upload.sh deleted file mode 100755 index c3c2964..0000000 --- a/tools/upload.sh +++ /dev/null @@ -1,11 +0,0 @@ -HOST=$1 -CODE=$2 -RESULT_BASE=$3 - -curl --form upload_code=$2 \ - --form "sample_data=@"$RESULT_BASE.res \ - --form "raw_data=@"$RESULT_BASE.raw.gz \ - --form "db_conf_data=@"$RESULT_BASE.db.cnf \ - --form "benchmark_conf_data=@"$RESULT_BASE.ben.cnf \ - --form "summary_data=@"$RESULT_BASE.summary \ - $1 diff --git a/tools/upload_batch.py b/tools/upload_batch.py new file mode 100644 index 0000000..697c624 --- /dev/null +++ b/tools/upload_batch.py @@ -0,0 +1,32 @@ +from poster.encode import multipart_encode +from poster.streaminghttp import register_openers +import urllib2 + +register_openers() + +db="mysql_" +Max_index = 50 + +for i in range(Max_index): + prefix = 1 + i + params = { + 'summary_data': open(db + str(prefix) + ".summary", "r"), + 'db_conf_data':open(db + str(prefix) + ".db.cnf","r"), + 'db_status':open(db + str(prefix) + ".db.status",'r'), + 'sample_data':open(db + str(prefix)+".res","r"), + 'raw_data': open(db + str(prefix)+".res","r"), + 'benchmark_conf_data': open(db + str(prefix)+".ben.cnf","r"), + 'upload_code': '14414QYEORPR4CE52X20', + 'upload_use':'store', + 'hardware':'m3.xlarge', + 'cluster':'exps_mysql_5.6_m3.xlarge_ycsb_rr_sf18000_tr50_t300_runlimited_w0-0-0-100-0-0_s0.6' #unknown + +} + + datagen, headers = multipart_encode(params) + +# request = urllib2.Request("http://127.0.0.1:8000/new_result/", datagen, headers) + + request = urllib2.Request("http://52.26.247.195:8000/new_result/", datagen, headers) + + print urllib2.urlopen(request).read() diff --git a/website/__init__.pyc b/website/__init__.pyc new file mode 100644 index 0000000..6de4abc Binary files /dev/null and b/website/__init__.pyc differ diff --git a/website/admin.py b/website/admin.py index 2608413..dcb91af 100644 --- a/website/admin.py +++ b/website/admin.py @@ -1,9 +1,8 @@ from django.contrib import admin -from website.models import Project, Result, ExperimentConf, DBConf - +from website.models import LEARNING_PARAMS, FEATURED_PARAMS, Project, Result, ExperimentConf, DBConf,Statistics class ExperimentConfAdmin(admin.ModelAdmin): - list_display = [ 'name', 'project', 'benchmark_type', 'creation_time' ] + list_display = [ 'name', 'application', 'benchmark_type', 'creation_time' ] list_filter = [ 'creation_time' ] class ProjectAdmin(admin.ModelAdmin): @@ -13,10 +12,20 @@ class ProjectAdmin(admin.ModelAdmin): list_display_links = ('name', 'last_update', 'creation_time') class DBConfAdmin(admin.ModelAdmin): - list_display = [ 'name', 'project', 'creation_time', 'db_type' ] + list_display = [ 'name', 'application', 'creation_time', 'db_type' ] + +class FEATURED_PARAMSAdmin(admin.ModelAdmin): + list_display = [ 'db_type', 'params'] + +class LEARNING_PARAMSAdmin(admin.ModelAdmin): + list_display = [ 'db_type', 'params'] + admin.site.register(Project, ProjectAdmin) admin.site.register(ExperimentConf, ExperimentConfAdmin) admin.site.register(DBConf, DBConfAdmin) +admin.site.register(FEATURED_PARAMS,FEATURED_PARAMSAdmin) +admin.site.register(LEARNING_PARAMS, LEARNING_PARAMSAdmin) + admin.site.register(Result) diff --git a/website/admin.pyc b/website/admin.pyc new file mode 100644 index 0000000..e34dae7 Binary files /dev/null and b/website/admin.pyc differ diff --git a/website/gp.py b/website/gp.py new file mode 100755 index 0000000..526d8d6 --- /dev/null +++ b/website/gp.py @@ -0,0 +1,79 @@ +import numpy as np +import tensorflow as tf + +def gp_tf(xs,ys,xt,ridge): + + MAX_ITER = 100 + batch_size = 3000 + sigma_cl = 1.07; + y_best = tf.cast(tf.reduce_min(ys,0,True),tf.float32); #array + sample_size = xs.shape[0] + nfeats = xs.shape[1] + train_size = 1 + arr_offset = 0 + ini_size = xt.shape[0] + + yhats = np.zeros([train_size,1]); + sigmas = np.zeros([train_size,1]); + eips = np.zeros([train_size,1]); + xs = np.float32(xs) + ys = np.float32(ys) + xt = np.float32(xt) + ############## + xt_ = tf.Variable(xt[0],tf.float32) + + sess = tf.Session() + init = tf.initialize_all_variables() + sess.run(init) + + + ridge = np.float32(ridge) + + + v1 = tf.placeholder(tf.float32,name="v1") + v2 = tf.placeholder(tf.float32,name="v2") + dist = tf.sqrt(tf.reduce_sum(tf.pow(tf.sub(v1, v2), 2),1)) + + tmp = np.zeros([sample_size,sample_size]) + for i in range(sample_size): + tmp[i] = sess.run(dist,feed_dict={v1:xs[i],v2:xs}) +# print "Finished euc matrix \n" + + + tmp = tf.cast(tmp,tf.float32) + K = tf.exp(-tmp/sigma_cl) + tf.diag(ridge); +# print "Finished K " + + K2_mat = tf.sqrt(tf.reduce_sum(tf.pow(tf.sub(xt_, xs), 2),1)) + K2_mat = tf.transpose(tf.expand_dims(K2_mat,0)) + K2 = tf.cast(tf.exp(-K2_mat/sigma_cl),tf.float32) + + x = tf.matmul(tf.matrix_inverse(K) , ys) + yhat_ = tf.cast(tf.matmul( tf.transpose(K2) ,x),tf.float32) + sig_val = tf.cast((tf.sqrt(1 - tf.matmul( tf.transpose(K2) ,tf.matmul(tf.matrix_inverse(K) , K2)) )),tf.float32) + + Loss = tf.squeeze(tf.sub(yhat_,sig_val)) +# optimizer = tf.train.GradientDescentOptimizer(0.1) + optimizer = tf.train.AdamOptimizer(0.1) + train = optimizer.minimize(Loss) + init = tf.initialize_all_variables() + sess.run(init) + + yhats = [] + sigmas = [] + minL = [] + new_conf = [] + for i in range(ini_size): + assign_op = xt_.assign(xt[i]) + sess.run(assign_op) + for step in range(MAX_ITER): +# print i, step, sess.run(Loss) + sess.run(train) + yhats.append(sess.run(yhat_)[0][0]) + sigmas.append(sess.run(sig_val)[0][0]) + minL.append(sess.run(Loss)) + new_conf.append(sess.run(xt_)) + return yhats, sigmas, minL,new_conf + + + diff --git a/website/gp.pyc b/website/gp.pyc new file mode 100644 index 0000000..10ce3ab Binary files /dev/null and b/website/gp.pyc differ diff --git a/website/gp_workload.py b/website/gp_workload.py new file mode 100755 index 0000000..5379aeb --- /dev/null +++ b/website/gp_workload.py @@ -0,0 +1,92 @@ + + +import numpy as np +import tensorflow as tf +import time + + + +def gp_workload(xs,ys,xt,ridge): + + batch_size = 3000 + sigma_cl = 1.07; + xs = np.float32(xs) + ys = np.float32(ys) + xt = np.float32(xt) + ridge = np.float32(ridge) + + y_best = tf.cast(tf.reduce_min(ys,0,True),tf.float32); #array + sample_size = xs.shape[0] + nfeats = xs.shape[1] + train_size = xt.shape[0] + arr_offset = 0 + yhats = np.zeros([train_size,1]); + # sigmas = np.zeros([train_size,1]); + + + v1 = tf.placeholder(tf.float32,name="v1") + v2 = tf.placeholder(tf.float32,name="v2") + dist = tf.sqrt(tf.reduce_sum(tf.pow(tf.sub(v1, v2), 2),1)) + sess = tf.Session() +# sess = tf.Session(config=tf.ConfigProto(log_device_placement=True)) + + tmp = np.zeros([sample_size,sample_size]) + for i in range(sample_size): + tmp[i] = sess.run(dist,feed_dict={v1:xs[i],v2:xs}) +# print "Finished euc matrix \n" + + + tmp = tf.cast(tmp,tf.float32) + K = tf.exp(-tmp/sigma_cl) + tf.diag(ridge); + # print "Finished K " + + + K2 = tf.placeholder(tf.float32,name="K2") + K3 = tf.placeholder(tf.float32,name="K3") + + x = tf.matmul(tf.matrix_inverse(K) , ys) + yhat_ = tf.cast(tf.matmul( tf.transpose(K2) ,x),tf.float32); +# sig_val = tf.cast((tf.sqrt(tf.diag_part(K3 - tf.matmul( tf.transpose(K2) ,tf.matmul(tf.matrix_inverse(K) , K2)) ))),tf.float32) + + + + + while arr_offset < train_size: + if arr_offset + batch_size > train_size: + end_offset = train_size + else: + end_offset = arr_offset + batch_size; + + + xt_ = xt[arr_offset:end_offset]; + batch_len = end_offset - arr_offset + + tmp = np.zeros([sample_size,batch_len]) + for i in range(sample_size): + tmp[i] = sess.run(dist,feed_dict={v1:xs[i],v2:xt_}) + + K2_ = tf.exp(-tmp/sigma_cl); + K2_ = sess.run(K2_) + + # tmp = np.zeros([batch_len,batch_len]) + # for i in range(batch_len): + # tmp[i] = sess.run(dist,feed_dict={v1:xt_[i],v2:xt_}) + # K3_ =tf.exp(-tmp/sigma_cl); + # K3_ = sess.run(K3_) + + + yhat = sess.run(yhat_,feed_dict={K2:K2_}) + + # sigma = np.zeros([1,batch_len],np.float32) + # sigma[0] = (sess.run(sig_val,feed_dict={K2:K2_,K3:K3_})) + # sigma = np.transpose(sigma) + + yhats[arr_offset:end_offset] = yhat + # sigmas[arr_offset:end_offset] = sigma; + arr_offset = end_offset ; + + sess.close() + + return yhats +#,sigmas, eips + diff --git a/website/gp_workload.pyc b/website/gp_workload.pyc new file mode 100644 index 0000000..b732766 Binary files /dev/null and b/website/gp_workload.pyc differ diff --git a/website/migrations/0001_initial.py b/website/migrations/0001_initial.py new file mode 100644 index 0000000..f9f7ebd --- /dev/null +++ b/website/migrations/0001_initial.py @@ -0,0 +1,158 @@ +# -*- coding: utf-8 -*- +# Generated by Django 1.10.1 on 2016-09-08 13:31 +from __future__ import unicode_literals + +from django.conf import settings +import django.core.validators +from django.db import migrations, models +import django.db.models.deletion +import re + + +class Migration(migrations.Migration): + + initial = True + + dependencies = [ + migrations.swappable_dependency(settings.AUTH_USER_MODEL), + ] + + operations = [ + migrations.CreateModel( + name='Application', + fields=[ + ('id', models.AutoField(auto_created=True, primary_key=True, serialize=False, verbose_name='ID')), + ('name', models.CharField(max_length=64)), + ('description', models.TextField()), + ('creation_time', models.DateTimeField()), + ('last_update', models.DateTimeField()), + ('upload_code', models.CharField(max_length=30)), + ], + ), + migrations.CreateModel( + name='DBConf', + fields=[ + ('id', models.AutoField(auto_created=True, primary_key=True, serialize=False, verbose_name='ID')), + ('name', models.CharField(max_length=50)), + ('description', models.CharField(max_length=512)), + ('creation_time', models.DateTimeField()), + ('configuration', models.TextField()), + ('similar_conf', models.TextField(default=b'zbh')), + ('db_type', models.CharField(max_length=9)), + ('application', models.ForeignKey(on_delete=django.db.models.deletion.CASCADE, to='website.Application')), + ], + ), + migrations.CreateModel( + name='ExperimentConf', + fields=[ + ('id', models.AutoField(auto_created=True, primary_key=True, serialize=False, verbose_name='ID')), + ('name', models.CharField(max_length=50)), + ('description', models.CharField(max_length=512)), + ('configuration', models.TextField()), + ('benchmark_type', models.CharField(max_length=512)), + ('creation_time', models.DateTimeField()), + ('isolation', models.TextField()), + ('scalefactor', models.TextField()), + ('terminals', models.TextField()), + ('application', models.ForeignKey(on_delete=django.db.models.deletion.CASCADE, to='website.Application')), + ], + ), + migrations.CreateModel( + name='FEATURED_PARAMS', + fields=[ + ('id', models.AutoField(auto_created=True, primary_key=True, serialize=False, verbose_name='ID')), + ('db_type', models.CharField(max_length=64)), + ('params', models.CharField(max_length=512)), + ], + ), + migrations.CreateModel( + name='LEARNING_PARAMS', + fields=[ + ('id', models.AutoField(auto_created=True, primary_key=True, serialize=False, verbose_name='ID')), + ('db_type', models.CharField(max_length=64)), + ('params', models.CharField(max_length=512)), + ], + ), + migrations.CreateModel( + name='Project', + fields=[ + ('id', models.AutoField(auto_created=True, primary_key=True, serialize=False, verbose_name='ID')), + ('name', models.CharField(max_length=64)), + ('description', models.TextField()), + ('creation_time', models.DateTimeField()), + ('last_update', models.DateTimeField()), + ('upload_code', models.CharField(max_length=30)), + ('user', models.ForeignKey(on_delete=django.db.models.deletion.CASCADE, to=settings.AUTH_USER_MODEL)), + ], + ), + migrations.CreateModel( + name='Result', + fields=[ + ('id', models.AutoField(auto_created=True, primary_key=True, serialize=False, verbose_name='ID')), + ('creation_time', models.DateTimeField()), + ('timestamp', models.DateTimeField()), + ('throughput', models.FloatField()), + ('avg_latency', models.FloatField()), + ('min_latency', models.FloatField()), + ('p25_latency', models.FloatField()), + ('p50_latency', models.FloatField()), + ('p75_latency', models.FloatField()), + ('p90_latency', models.FloatField()), + ('p95_latency', models.FloatField()), + ('p99_latency', models.FloatField()), + ('max_latency', models.FloatField()), + ('most_similar', models.CharField(max_length=100, validators=[django.core.validators.RegexValidator(re.compile('^\\d+(?:\\,\\d+)*\\Z'), code='invalid', message='Enter only digits separated by commas.')])), + ('application', models.ForeignKey(on_delete=django.db.models.deletion.CASCADE, to='website.Application')), + ('benchmark_conf', models.ForeignKey(on_delete=django.db.models.deletion.CASCADE, to='website.ExperimentConf')), + ('db_conf', models.ForeignKey(on_delete=django.db.models.deletion.CASCADE, to='website.DBConf')), + ], + ), + migrations.CreateModel( + name='Statistics', + fields=[ + ('id', models.AutoField(auto_created=True, primary_key=True, serialize=False, verbose_name='ID')), + ('time', models.IntegerField()), + ('throughput', models.FloatField()), + ('avg_latency', models.FloatField()), + ('min_latency', models.FloatField()), + ('p25_latency', models.FloatField()), + ('p50_latency', models.FloatField()), + ('p75_latency', models.FloatField()), + ('p90_latency', models.FloatField()), + ('p95_latency', models.FloatField()), + ('p99_latency', models.FloatField()), + ('max_latency', models.FloatField()), + ('result', models.ForeignKey(on_delete=django.db.models.deletion.CASCADE, to='website.Result')), + ], + ), + migrations.CreateModel( + name='Task', + fields=[ + ('id', models.IntegerField(primary_key=True, serialize=False)), + ('creation_time', models.DateTimeField()), + ('finish_time', models.DateTimeField(null=True)), + ('running_time', models.IntegerField(null=True)), + ('status', models.CharField(max_length=64)), + ('traceback', models.TextField(null=True)), + ('result', models.TextField(null=True)), + ], + ), + migrations.CreateModel( + name='Website_Conf', + fields=[ + ('id', models.AutoField(auto_created=True, primary_key=True, serialize=False, verbose_name='ID')), + ('name', models.CharField(max_length=64)), + ('value', models.CharField(max_length=512)), + ], + ), + migrations.AddField( + model_name='application', + name='project', + field=models.ForeignKey(on_delete=django.db.models.deletion.CASCADE, to='website.Project'), + ), + migrations.AddField( + model_name='application', + name='user', + field=models.ForeignKey(on_delete=django.db.models.deletion.CASCADE, to=settings.AUTH_USER_MODEL), + ), + ] diff --git a/website/migrations/0001_initial.pyc b/website/migrations/0001_initial.pyc new file mode 100644 index 0000000..eb8d843 Binary files /dev/null and b/website/migrations/0001_initial.pyc differ diff --git a/website/migrations/0002_auto_20160913_1143.py b/website/migrations/0002_auto_20160913_1143.py new file mode 100644 index 0000000..8fa6b5d --- /dev/null +++ b/website/migrations/0002_auto_20160913_1143.py @@ -0,0 +1,110 @@ +# -*- coding: utf-8 -*- +# Generated by Django 1.9 on 2016-09-13 15:43 +from __future__ import unicode_literals + +from django.conf import settings +from django.db import migrations, models +import django.db.models.deletion + + +class Migration(migrations.Migration): + + dependencies = [ + migrations.swappable_dependency(settings.AUTH_USER_MODEL), + ('website', '0001_initial'), + ] + + operations = [ + migrations.CreateModel( + name='DBMS_catalog', + fields=[ + ('id', models.IntegerField(primary_key=True, serialize=False)), + ('dbms_name', models.TextField()), + ('version', models.TextField()), + ], + ), + migrations.CreateModel( + name='Knob_catalog', + fields=[ + ('id', models.IntegerField(primary_key=True, serialize=False)), + ('dbms_id', models.IntegerField()), + ('name', models.TextField()), + ('vartype', models.TextField()), + ('unit', models.TextField(null=True)), + ('category', models.TextField(null=True)), + ('summary', models.TextField(null=True)), + ('description', models.TextField(null=True)), + ('scope', models.TextField()), + ('dynamic', models.BooleanField()), + ('min_value', models.TextField(null=True)), + ('max_value', models.TextField(null=True)), + ('valid_vals', models.TextField(null=True)), + ('default_val', models.TextField()), + ('deprecated', models.BooleanField()), + ('dangerous', models.TextField(null=True)), + ('safe_vals', models.TextField(null=True)), + ('rank', models.IntegerField(null=True)), + ], + ), + migrations.CreateModel( + name='KNOB_PARAMS', + fields=[ + ('id', models.AutoField(auto_created=True, primary_key=True, serialize=False, verbose_name='ID')), + ('db_type', models.CharField(max_length=64)), + ('params', models.CharField(max_length=512)), + ], + ), + migrations.CreateModel( + name='Metric_catalog', + fields=[ + ('id', models.IntegerField(primary_key=True, serialize=False)), + ('dbms_id', models.IntegerField()), + ('scale', models.TextField()), + ('name', models.TextField()), + ('vartype', models.TextField()), + ('description', models.TextField(null=True)), + ('scope', models.TextField(null=True)), + ('featured', models.BooleanField()), + ], + ), + migrations.CreateModel( + name='Oltpbench_info', + fields=[ + ('id', models.AutoField(auto_created=True, primary_key=True, serialize=False, verbose_name='ID')), + ('dbms_name', models.CharField(max_length=64)), + ('dbms_version', models.CharField(max_length=64)), + ('hardware', models.CharField(max_length=64, null=True)), + ('cluster', models.TextField(null=True)), + ('summary', models.TextField()), + ('res', models.TextField()), + ('status', models.TextField()), + ('cfg', models.TextField()), + ('raw', models.TextField(null=True)), + ('user', models.ForeignKey(on_delete=django.db.models.deletion.CASCADE, to=settings.AUTH_USER_MODEL)), + ], + ), + migrations.CreateModel( + name='Workload_info', + fields=[ + ('id', models.AutoField(auto_created=True, primary_key=True, serialize=False, verbose_name='ID')), + ('isolation', models.CharField(max_length=64)), + ('scalefactor', models.IntegerField()), + ('terminals', models.IntegerField()), + ('time', models.IntegerField()), + ('rate', models.CharField(max_length=64)), + ('skew', models.FloatField(null=True)), + ('trans_weights', models.TextField()), + ('workload', models.TextField()), + ], + ), + migrations.AlterField( + model_name='result', + name='most_similar', + field=models.CommaSeparatedIntegerField(max_length=100), + ), + migrations.AddField( + model_name='oltpbench_info', + name='wid', + field=models.ForeignKey(on_delete=django.db.models.deletion.CASCADE, to='website.Workload_info'), + ), + ] diff --git a/website/migrations/0002_auto_20160913_1143.pyc b/website/migrations/0002_auto_20160913_1143.pyc new file mode 100644 index 0000000..1815006 Binary files /dev/null and b/website/migrations/0002_auto_20160913_1143.pyc differ diff --git a/website/migrations/__init__.py b/website/migrations/__init__.py new file mode 100644 index 0000000..e69de29 diff --git a/website/migrations/__init__.pyc b/website/migrations/__init__.pyc new file mode 100644 index 0000000..2ea7fac Binary files /dev/null and b/website/migrations/__init__.pyc differ diff --git a/website/models.py b/website/models.py index dbf379c..fc83d1a 100644 --- a/website/models.py +++ b/website/models.py @@ -3,15 +3,94 @@ from django.db import models from django.contrib.auth.models import User from django import forms +from django.contrib import admin +class Knob_catalog(models.Model): + id = models.IntegerField(primary_key=True) +# dbms_name = models.TextField() +# dbms_version = models.TextField() + dbms_id = models.IntegerField() + name = models.TextField() + vartype = models.TextField() + unit = models.TextField(null=True) + category = models.TextField(null=True) + summary = models.TextField(null=True) + description = models.TextField(null=True) + scope = models.TextField() + dynamic = models.BooleanField() + min_value = models.TextField(null=True) + max_value = models.TextField(null=True) + valid_vals = models.TextField(null=True) + default_val = models.TextField() + deprecated = models.BooleanField() + dangerous = models.TextField(null=True) + safe_vals = models.TextField(null=True) + rank = models.IntegerField(null=True) + + +class Metric_catalog(models.Model): + id = models.IntegerField(primary_key=True) + dbms_id = models.IntegerField() + # dbms_name = models.TextField() + # dbms_version = models.TextField() + scale = models.TextField() + name = models.TextField() + vartype = models.TextField() + description = models.TextField(null=True) + scope = models.TextField(null=True) + featured = models.BooleanField() + +class DBMS_catalog(models.Model): + id = models.IntegerField(primary_key=True) + dbms_name = models.TextField() + version = models.TextField() + + +class Workload_info(models.Model): + #id = models.AutoField(primary_key=True) + isolation = models.CharField(max_length=64) + scalefactor = models.IntegerField() + terminals = models.IntegerField() + time = models.IntegerField() + rate = models.CharField(max_length=64) + skew = models.FloatField(null=True) + trans_weights = models.TextField() + workload = models.TextField() + +class Oltpbench_info(models.Model): +# id = models.IntegerField(primary_key=True) + + user = models.ForeignKey(User) + dbms_name = models.CharField(max_length=64) + dbms_version = models.CharField(max_length=64) + + hardware = models.CharField(null=True, max_length=64) + cluster = models.TextField(null=True) + + summary = models.TextField() + res = models.TextField() + status = models.TextField() + cfg = models.TextField() + raw = models.TextField(null=True) + + wid = models.ForeignKey(Workload_info) + + class NewResultForm(forms.Form): upload_code = forms.CharField(max_length=30) + + upload_use = forms.CharField(max_length=30) #compute/store + hardware = forms.CharField(max_length=30) # hardware + cluster = forms.CharField(max_length=200) # store cluster + sample_data = forms.FileField() raw_data = forms.FileField() db_conf_data = forms.FileField() benchmark_conf_data = forms.FileField() summary_data = forms.FileField() + db_status =forms.FileField() #.status + class Project(models.Model): @@ -24,38 +103,59 @@ class Project(models.Model): upload_code = models.CharField(max_length=30) def delete(self, using=None): - targets = DBConf.objects.filter(project=self) - results = Result.objects.filter(project=self) + apps = Application.objects.filter(project=self) + for x in apps: + x.delete() + super(Project, self).delete(using) + + + + +class Task(models.Model): + id = models.IntegerField(primary_key=True) + creation_time = models.DateTimeField() + finish_time = models.DateTimeField(null=True) + running_time = models.IntegerField(null=True) + status = models.CharField(max_length=64) + traceback = models.TextField(null=True) + result = models.TextField(null=True) + + +class Application(models.Model): + user = models.ForeignKey(User) + name = models.CharField(max_length=64) + description = models.TextField() + + project = models.ForeignKey(Project) + creation_time = models.DateTimeField() + last_update = models.DateTimeField() + + upload_code = models.CharField(max_length=30) + + def delete(self, using=None): + targets = DBConf.objects.filter(application=self) + results = Result.objects.filter(application=self) + expconfs = ExperimentConf.objects.filter(application=self) for t in targets: t.delete() for r in results: r.delete() - super(Project, self).delete(using) + for x in expconfs: + x.delete() + super(Application, self).delete(using) + + + class ExperimentConf(models.Model): - BENCHMARK_TYPES = [x.upper() for x in sorted([ - 'tpcc', - 'tatp', - 'wikipedia', - 'resourcestresser', - 'twitter', - 'epinions', - 'ycsb', - 'jpab', - 'seats', - 'auctionmark', - 'chbenchmark', - 'voter', - 'linkbench', - 'sibench' - ])] + application = models.ForeignKey(Application) + - project = models.ForeignKey(Project) name = models.CharField(max_length=50) description = models.CharField(max_length=512) configuration = models.TextField() - benchmark_type = models.CharField(max_length=sum(map(lambda x: len(x) + 1, BENCHMARK_TYPES))) + benchmark_type = models.CharField(max_length=512) creation_time = models.DateTimeField() isolation = models.TextField() scalefactor = models.TextField() @@ -68,56 +168,23 @@ class ExperimentConf(models.Model): ] -FEATURED_VARS = { - 'DB2': [], - 'MYSQL': [ - re.compile(ur'innodb_buffer_pool_size', re.UNICODE | re.IGNORECASE), - re.compile(ur'innodb_buffer_pool_instances', re.UNICODE | re.IGNORECASE), - re.compile(ur'innodb_log_file_size', re.UNICODE | re.IGNORECASE), - re.compile(ur'innodb_log_buffer_size', re.UNICODE | re.IGNORECASE), - re.compile(ur'innodb_flush_log_at_trx_commit', re.UNICODE | re.IGNORECASE), - re.compile(ur'innodb_thread_concurrency', re.UNICODE | re.IGNORECASE), - re.compile(ur'innodb_file_per_table', re.UNICODE | re.IGNORECASE), - re.compile(ur'key_buffer_size', re.UNICODE | re.IGNORECASE), - re.compile(ur'table_cache', re.UNICODE | re.IGNORECASE), - re.compile(ur'thread_cache', re.UNICODE | re.IGNORECASE), - re.compile(ur'query_cache_size', re.UNICODE | re.IGNORECASE), - ], - 'POSTGRES': [], - 'ORACLE': [], - 'SQLSERVER': [], - 'SQLITE': [], - 'AMAZONRDS': [], - 'HSTORE': [], - 'SQLAZURE': [], - 'ASSCLOWN': [], - 'HSQLDB': [], - 'H2': [], - 'NUODB': [] -} +class FEATURED_PARAMS(models.Model): + db_type = models.CharField(max_length=64) + params = models.CharField(max_length=512) + +class Website_Conf(models.Model): + name = models.CharField(max_length=64) + value = models.CharField(max_length=512) + +class LEARNING_PARAMS(models.Model): + db_type = models.CharField(max_length=64) + params = models.CharField(max_length=512) + +class KNOB_PARAMS(models.Model): + db_type = models.CharField(max_length=64) + params = models.CharField(max_length=512) -LEARNING_VARS = { - 'DB2': [], - 'MYSQL': [ - re.compile(ur'innodb_buffer_pool_size', re.UNICODE | re.IGNORECASE), - re.compile(ur'innodb_buffer_pool_instances', re.UNICODE | re.IGNORECASE), - re.compile(ur'innodb_log_file_size', re.UNICODE | re.IGNORECASE), - re.compile(ur'innodb_log_buffer_size', re.UNICODE | re.IGNORECASE), - re.compile(ur'innodb_thread_concurrency', re.UNICODE | re.IGNORECASE), - ], - 'POSTGRES': [], - 'ORACLE': [], - 'SQLSERVER': [], - 'SQLITE': [], - 'AMAZONRDS': [], - 'HSTORE': [], - 'SQLAZURE': [], - 'ASSCLOWN': [], - 'HSQLDB': [], - 'H2': [], - 'NUODB': [] -} class DBConf(models.Model): DB_TYPES = sorted([ @@ -135,8 +202,7 @@ class DBConf(models.Model): 'H2', 'NUODB' ]) - - project = models.ForeignKey(Project) + application = models.ForeignKey(Application) name = models.CharField(max_length=50) description = models.CharField(max_length=512) creation_time = models.DateTimeField() @@ -173,9 +239,12 @@ class DBConf(models.Model): class Result(models.Model): - project = models.ForeignKey(Project) benchmark_conf = models.ForeignKey(ExperimentConf) db_conf = models.ForeignKey(DBConf) + + application = models.ForeignKey(Application) + creation_time = models.DateTimeField() + timestamp = models.DateTimeField() throughput = models.FloatField() avg_latency = models.FloatField() diff --git a/website/models.pyc b/website/models.pyc new file mode 100644 index 0000000..51cdd4f Binary files /dev/null and b/website/models.pyc differ diff --git a/website/settings.py b/website/settings.py new file mode 100644 index 0000000..02a87c7 --- /dev/null +++ b/website/settings.py @@ -0,0 +1,214 @@ +# Django settings for sample project. +import djcelery +from django.template import loader + +djcelery.setup_loader() + +# BasePath +BasePath = '/home/ubuntu' + +# deploy RabbitMq +BROKER_URL='amqp://guest:guest@localhost:5672//' +CELERY_TRACK_STARTED = True +TEST_RUNNER = 'django.test.runner.DiscoverRunner' +DEBUG = True + +TEMPLATES = [ + { + 'BACKEND': 'django.template.backends.django.DjangoTemplates', + 'DIRS': [ + # insert your TEMPLATE_DIRS here + # Put strings here, like "/home/html/django_templates" or "C:/www/django/templates". + # Always use forward slashes, even on Windows. + # Don't forget to use absolute paths, not relative paths. + BasePath + '/website/website/template' + ], + 'OPTIONS': { + 'context_processors': [ + # Insert your TEMPLATE_CONTEXT_PROCESSORS here or use this + # list if you haven't customized them: + 'django.contrib.auth.context_processors.auth', + 'django.template.context_processors.debug', + 'django.template.context_processors.i18n', + 'django.template.context_processors.media', + 'django.template.context_processors.static', + 'django.template.context_processors.tz', + 'django.contrib.messages.context_processors.messages', + 'django.template.context_processors.csrf', + ], + 'loaders':['django.template.loaders.filesystem.Loader', + 'django.template.loaders.app_directories.Loader', + ] , + 'debug': DEBUG, + }, + }, +] + + +ADMINS = ( + # ('Your Name', 'your_email@example.com'), +) + +MANAGERS = ADMINS + +DATABASES = { + 'default': { + 'ENGINE': 'django.db.backends.mysql', # Add 'postgresql_psycopg2', 'mysql', 'sqlite3' or 'oracle'. + 'NAME': 'websitedb', # Or path to database file if using sqlite3. + # The following settings are not used with sqlite3: + 'USER': 'zbh', #'dvanaken', + 'PASSWORD': 'zbh19950730', #'DthwboH4l4l', + 'HOST': 'localhost', # Empty for localhost through domain sockets or '127.0.0.1' for localhost through TCP. + 'PORT': '', # Set to empty string for default. + 'OPTIONS': { + 'init_command': "SET sql_mode='STRICT_TRANS_TABLES',innodb_strict_mode=1", + }, + } +} + +# Email Configuration +EMAIL_USE_TLS = True +EMAIL_HOST = '' # Add smtp server's URL +EMAIL_PORT = 587 # Add smtp server's TLS port if USE_TLS, else use SSL port +EMAIL_HOST_USER = '' # Add username for mail server account +EMAIL_HOST_PASSWORD = '' # Add mail server account's password + +# Hosts/domain names that are valid for this site; required if DEBUG is False +# See https://docs.djangoproject.com/en/1.5/ref/settings/#allowed-hosts +ALLOWED_HOSTS = [] + +# Local time zone for this installation. Choices can be found here: +# http://en.wikipedia.org/wiki/List_of_tz_zones_by_name +# although not all choices may be available on all operating systems. +# In a Windows environment this must be set to your system time zone. +TIME_ZONE = 'America/New_York' + +# Language code for this installation. All choices can be found here: +# http://www.i18nguy.com/unicode/language-identifiers.html +LANGUAGE_CODE = 'en-us' + +SITE_ID = 1 + +# If you set this to False, Django will make some optimizations so as not +# to load the internationalization machinery. +USE_I18N = True + +# If you set this to False, Django will not format dates, numbers and +# calendars according to the current locale. +USE_L10N = True + +# If you set this to False, Django will not use timezone-aware datetimes. +USE_TZ = True + +# Absolute filesystem path to the directory that will hold user-uploaded files. +# Example: "/var/www/example.com/media/" +MEDIA_ROOT = BasePath + '/website/data/media' +#MEDIA_ROOT = '/var/www/oltpbench/media/' +MEDIA_ROOT_URL = '/media/' + +# URL that handles the media served from MEDIA_ROOT. Make sure to use a +# trailing slash. +# Examples: "http://example.com/media/", "http://media.example.com/" +MEDIA_URL = '/media/' + +# Absolute path to the directory static files should be collected to. +# Don't put anything in this directory yourself; store your static files +# in apps' "static/" subdirectories and in STATICFILES_DIRS. +# Example: "/var/www/example.com/static/" +STATIC_ROOT = BasePath + '/website/data/static' + +# URL prefix for static files. +# Example: "http://example.com/static/", "http://static.example.com/" +STATIC_URL = '/static/' + +# Additional locations of static files +STATICFILES_DIRS = ( + # Put strings here, like "/home/html/static" or "C:/www/django/static". + # Always use forward slashes, even on Windows. + # Don't forget to use absolute paths, not relative paths. +) + +# List of finder classes that know how to find static files in +# various locations. +STATICFILES_FINDERS = ( + 'django.contrib.staticfiles.finders.FileSystemFinder', + 'django.contrib.staticfiles.finders.AppDirectoriesFinder', +# 'django.contrib.staticfiles.finders.DefaultStorageFinder', +) + +# Make this unique, and don't share it with anybody. +SECRET_KEY = 'xwkw(0!fae+&6t@(6uth=4c&m&sdzu%odu4#u++0-9b0o0n3=!' + +FILE_UPLOAD_DIRECTORY_PERMISSIONS = 0o644 +FILE_UPLOAD_PERMISSIONS = 0o644 + +#UPLOAD_DIR = '/var/www/oltpbench/media' +UPLOAD_DIR = BasePath + '/website/data/media' + + +MIDDLEWARE_CLASSES = ( + 'django.middleware.common.CommonMiddleware', + 'django.contrib.sessions.middleware.SessionMiddleware', + 'django.middleware.csrf.CsrfViewMiddleware', + 'django.contrib.auth.middleware.AuthenticationMiddleware', + 'django.contrib.messages.middleware.MessageMiddleware', + 'debug_toolbar.middleware.DebugToolbarMiddleware', + # Uncomment the next line for simple clickjacking protection: + # 'django.middleware.clickjacking.XFrameOptionsMiddleware', +) + +ROOT_URLCONF = 'website.urls' + +# Python dotted path to the WSGI application used by Django's runserver. +WSGI_APPLICATION = 'website.wsgi.application' + + +INSTALLED_APPS = ( + 'django.contrib.auth', + 'django.contrib.contenttypes', + 'django.contrib.sessions', + 'django.contrib.sites', + 'django.contrib.messages', + 'django.contrib.staticfiles', + 'debug_toolbar', + #'django_extensions', + # Uncomment the next line to enable the admin: + 'django.contrib.admin', + # Uncomment the next line to enable admin documentation: + # 'django.contrib.admindocs', + #'rest_framework', + #'south', + 'djcelery', + 'website', +) + +SESSION_SERIALIZER = 'django.contrib.sessions.serializers.JSONSerializer' + +# A website logging configuration. The only tangible logging +# performed by this configuration is to send an email to +# the site admins on every HTTP 500 error when DEBUG=False. +# See http://docs.djangoproject.com/en/dev/topics/logging for +# more details on how to customize your logging configuration. +LOGGING = { + 'version': 1, + 'disable_existing_loggers': False, + 'filters': { + 'require_debug_false': { + '()': 'django.utils.log.RequireDebugFalse' + } + }, + 'handlers': { + 'mail_admins': { + 'level': 'ERROR', + 'filters': ['require_debug_false'], + 'class': 'django.utils.log.AdminEmailHandler' + } + }, + 'loggers': { + 'django.request': { + 'handlers': ['mail_admins'], + 'level': 'ERROR', + 'propagate': True, + }, + } +} diff --git a/website/settings.py-SAMPLE b/website/settings.py-SAMPLE deleted file mode 100644 index 5fe6340..0000000 --- a/website/settings.py-SAMPLE +++ /dev/null @@ -1,167 +0,0 @@ -""" -Django settings for Ottertune - -""" - -# Build paths inside the project like this: os.path.join(BASE_DIR, ...) -import os -BASE_DIR = os.path.dirname(os.path.dirname(__file__)) - -# Quick-start development settings - unsuitable for production - -# SECURITY WARNING: keep the secret key used in production secret! -SECRET_KEY = '***CHANGE ME***' - -# SECURITY WARNING: don't run with debug turned on in production! -DEBUG = True - -ALLOWED_HOSTS = [] - -PROJECT_ROOT = os.path.abspath(os.path.dirname(__file__)) - -# Application definition -INSTALLED_APPS = ( - 'django.contrib.auth', - 'django.contrib.contenttypes', - 'django.contrib.sessions', - 'django.contrib.sites', - 'django.contrib.messages', - 'django.contrib.staticfiles', - 'debug_toolbar', - #'django_extensions', - # Uncomment the next line to enable the admin: - 'django.contrib.admin', - # Uncomment the next line to enable admin documentation: - # 'django.contrib.admindocs', - #'rest_framework', - #'south', - 'djcelery', - 'website', - 'celery_example', -) - -MIDDLEWARE_CLASSES = ( - 'django.middleware.common.CommonMiddleware', - 'django.contrib.sessions.middleware.SessionMiddleware', - 'django.middleware.csrf.CsrfViewMiddleware', - 'django.contrib.auth.middleware.AuthenticationMiddleware', -#'django.middleware.csrf.CsrfResponseMiddleware', - 'django.contrib.messages.middleware.MessageMiddleware', - # Uncomment the next line for simple clickjacking protection: - # 'django.middleware.clickjacking.XFrameOptionsMiddleware', -) - -ROOT_URLCONF = 'website.urls' - -WSGI_APPLICATION = 'website.wsgi.application' - -TEMPLATES = [ - { - 'DIRS': [ - os.path.join(PROJECT_ROOT, 'templates').replace('\\','/') - ], - 'BACKEND': 'django.template.backends.django.DjangoTemplates', - 'APP_DIRS': True, - 'OPTIONS': { - 'debug': True, - 'context_processors': [ - 'django.contrib.auth.context_processors.auth', - 'django.template.context_processors.debug', - 'django.template.context_processors.request', - 'django.template.context_processors.static', - 'django.template.context_processors.media', - 'django.contrib.messages.context_processors.messages', - ], - }, - }, -] - -# Database - -DATABASES = { - 'default': { - 'ENGINE': 'django.db.backends.mysql', - 'NAME': 'ottertune', - 'USER': '***CHANGEME***', - 'PASSWORD': '***CHANGEME***', - 'PORT': '3306', - } -} - -# Internationalization - -# Local time zone for this installation. Choices can be found here: -# http://en.wikipedia.org/wiki/List_of_tz_zones_by_name -# although not all choices may be available on all operating systems. -# In a Windows environment this must be set to your system time zone. -TIME_ZONE = 'America/New_York' - -# Language code for this installation. All choices can be found here: -# http://www.i18nguy.com/unicode/language-identifiers.html -LANGUAGE_CODE = 'en-us' - -# If you set this to False, Django will make some optimizations so as not -# to load the internationalization machinery. -USE_I18N = True - -# If you set this to False, Django will not format dates, numbers and -# calendars according to the current locale. -USE_L10N = True - -# If you set this to False, Django will not use timezone-aware datetimes. -USE_TZ = True - - -FILE_UPLOAD_DIRECTORY_PERMISSIONS = 0o644 -FILE_UPLOAD_PERMISSIONS = 0o644 - -#UPLOAD_DIR = '/var/www/oltpbench/media' -UPLOAD_DIR = '/Users/zhangbohan/.git/website/data/media' - - -# Static files (CSS, JavaScript, Images) -STATICFILES_DIRS = ( - os.path.join(PROJECT_ROOT, "static"), -) -STATIC_URL = '/static/' - - -# A website logging configuration. The only tangible logging -# performed by this configuration is to send an email to -# the site admins on every HTTP 500 error when DEBUG=False. -# See http://docs.djangoproject.com/en/dev/topics/logging for -# more details on how to customize your logging configuration. -LOGGING = { - 'version': 1, - 'disable_existing_loggers': False, - 'filters': { - 'require_debug_false': { - '()': 'django.utils.log.RequireDebugFalse' - } - }, - 'handlers': { - 'mail_admins': { - 'level': 'ERROR', - 'filters': ['require_debug_false'], - 'class': 'django.utils.log.AdminEmailHandler' - } - }, - 'loggers': { - 'django.request': { - 'handlers': ['mail_admins'], - 'level': 'ERROR', - 'propagate': True, - }, - } -} - - -# CELERY SETTINGS -import djcelery -djcelery.setup_loader() - -BROKER_HOST = "localhost" -BROKER_PORT = 5672 -BROKER_USER = "CHANGEME" -BROKER_PASSWORD = "CHANGE" -BROKER_VHOST = "/" diff --git a/website/settings.pyc b/website/settings.pyc new file mode 100644 index 0000000..d6d3b85 Binary files /dev/null and b/website/settings.pyc differ diff --git a/website/static/js/jquery-1.7.2.min.js b/website/static/js/jquery-1.7.2.min.js new file mode 100755 index 0000000..93adea1 --- /dev/null +++ b/website/static/js/jquery-1.7.2.min.js @@ -0,0 +1,4 @@ +/*! jQuery v1.7.2 jquery.com | jquery.org/license */ +(function(a,b){function cy(a){return f.isWindow(a)?a:a.nodeType===9?a.defaultView||a.parentWindow:!1}function cu(a){if(!cj[a]){var b=c.body,d=f("<"+a+">").appendTo(b),e=d.css("display");d.remove();if(e==="none"||e===""){ck||(ck=c.createElement("iframe"),ck.frameBorder=ck.width=ck.height=0),b.appendChild(ck);if(!cl||!ck.createElement)cl=(ck.contentWindow||ck.contentDocument).document,cl.write((f.support.boxModel?"":"")+""),cl.close();d=cl.createElement(a),cl.body.appendChild(d),e=f.css(d,"display"),b.removeChild(ck)}cj[a]=e}return cj[a]}function ct(a,b){var c={};f.each(cp.concat.apply([],cp.slice(0,b)),function(){c[this]=a});return c}function cs(){cq=b}function cr(){setTimeout(cs,0);return cq=f.now()}function ci(){try{return new a.ActiveXObject("Microsoft.XMLHTTP")}catch(b){}}function ch(){try{return new a.XMLHttpRequest}catch(b){}}function cb(a,c){a.dataFilter&&(c=a.dataFilter(c,a.dataType));var d=a.dataTypes,e={},g,h,i=d.length,j,k=d[0],l,m,n,o,p;for(g=1;g0){if(c!=="border")for(;e
t |
ID: |
+ {{ id }} | +
Project: |
+ {{ result.application.project.name|linebreaks }} | +
Applications: |
+ {{result.application.name}} |
+
Start time: |
+ {{ task.creation_time }} | +
Running time: |
+ {{ time }} seconds | +
Time Limit: |
+ {{ limit }} seconds | +
Status: |
+ {{ task.status }} | +
Traceback: |
+ {{ task.traceback }} | +
Result: |
+ Download | +
Name: |
+ {{ project.name }} | +
Description: |
+ {{ project.description|linebreaks }} | +
Applications: |
+ + |
Creation time: |
+ {{ project.creation_time }} | +
Last update: |
+ {{ project.last_update }} | +