add innodb_file_per_table option by default
mysql has one innodb file per default and this can become very huge, which can trigger various issues [1]. So in general it is recommended to set the innodb_file_per_table option [2]. [1] http://forums.mysql.com/read.php?35,121880,121886 [2] http://dev.mysql.com/doc/refman/5.0/en/innodb-multiple-tablespaces.html
This commit is contained in:
parent
8e18c75911
commit
a72ab41660
3 changed files with 7 additions and 0 deletions
|
@ -47,6 +47,8 @@ thread_cache_size = 4
|
|||
# set it too high.
|
||||
innodb_buffer_pool_size = 50MB
|
||||
|
||||
innodb_file_per_table
|
||||
|
||||
query_cache_limit=5M
|
||||
|
||||
[mysql.server]
|
||||
|
|
|
@ -98,6 +98,9 @@ skip-bdb
|
|||
# Read the manual for more InnoDB related options. There are many!
|
||||
# You might want to disable InnoDB to shrink the mysqld process by circa 100MB.
|
||||
#skip-innodb
|
||||
|
||||
innodb_file_per_table
|
||||
|
||||
#
|
||||
# * Security Features
|
||||
#
|
||||
|
|
|
@ -124,6 +124,8 @@ set-variable = innodb_log_files_in_group=2
|
|||
innodb_flush_log_at_trx_commit = 1
|
||||
innodb_lock_wait_timeout = 50
|
||||
|
||||
innodb_file_per_table
|
||||
|
||||
[mysqldump]
|
||||
quick
|
||||
max_allowed_packet = 16M
|
||||
|
|
Loading…
Reference in a new issue