MySQL Forums
Forum List  »  Docs

Re: details about Server Parameters, which are server & which thread?
Posted by: Jay Pipes
Date: June 23, 2005 02:15PM

They are predominantly server variables, and exist at a global level for ALL client connections. Therefore, you don't consider things like query_cache_size to be for a specific thread. However, be aware that not all server variables are used by all storage engines. You can usually (but not always) tell which server variables correspond to which engine because they'll begin with the name of the storage engine, for instance: innodb_log_buffer_size or myisam_max_sort_file_size, however, be aware that some server variables are a little confusing. For instance, the key_buffer_size pertains ONLY to MyISAM index blocks, not to InnoDB index pages.

For a list of all the SERVER variables, simply do a SHOW VARIABLES from the command line. Anything you see there is a server variable, but, as noted above, if you use different storage engines, not all those server variables will be pertinent.

For thread-specific variables, anything which appears in the [client] section of your configuration file will be a thread-specific variables. These variables typically include things like socket, user, host, max_client_packet_length, etc. You can read the manual on the mysql client to see the variables used in the client.

All the variables listed in the "regular" documentation of the server (most of the docs) pertain to server variables, and belong in the [mysqld] section of your configuration file.

Hope this clears some things up. By all means, if you have question regarding a specific variable, then shoot the forum a question... :)

Jay Pipes
Community Relations Manager, North America, MySQL Inc.

Got Cluster? http://www.mysql.com/cluster
Personal: http://jpipes.com

Options: ReplyQuote


Subject
Views
Written By
Posted
Re: details about Server Parameters, which are server & which thread?
2418
June 23, 2005 02:15PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.