Server System Variables Maximum Value 4294967295 Command-Line Format --max-write-lock-count=# System Variable max_write_lock_count Scope Global Dynamic Yes SET_VAR  Hint Applies No Type Integer Default Value (Windows) 4294967295 Default Value (Other, 64-bit platforms) 18446744073709551615 Default Value (Other, 32-bit platforms) 4294967295 Minimum Value 1 Maximum Value (Windows) 4294967295 Maximum Value (Other, 64-bit platforms) 18446744073709551615 Maximum Value (Other, 32-bit platforms) 4294967295 Command-Line Format --mecab-rc-file=file_name System Variable mecab_rc_file Scope Global Dynamic No SET_VAR  Hint Applies No 836 The maximum number of simultaneous connections permitted to any given MySQL user account. A value of 0 (the default) means “no limit.” This variable has a global value that can be set at server startup or runtime. It also has a read-only session value that indicates the effective simultaneous-connection limit that applies to the account associated with the current session. The session value is initialized as follows: Account resource limits are specified using the  CREATE USER  or  ALTER USER  statement. See Section 6.2.20, “Setting Account Resource Limits” . •If the user account has a nonzero  MAX_USER_CONNECTIONS  resource limit, the session max_user_connections  value is set to that limit. •Otherwise, the session  max_user_connections  value is set to the global value. • max_write_lock_count • mecab_rc_file After this many write locks, permit some pending read lock requests to be processed in between. Write lock requests have higher priority than read lock requests. However, if  max_write_lock_count  is set to some low value (say, 10), read lock requests may be preferred over pending write lock requests if the read lock requests have already been passed over in favor of 10 write lock requests. Normally this behavior does not occur because  max_write_lock_count  by default has a very large value.