summaryrefslogtreecommitdiff
path: root/randgen
diff options
context:
space:
mode:
authorMarko Mäkelä <marko.makela@mariadb.com>2021-03-22 18:11:44 +0200
committerMarko Mäkelä <marko.makela@mariadb.com>2021-03-22 18:12:44 +0200
commit56274bd5e4115d86059936ddd3bf656dab1b4354 (patch)
tree5ba80dc3d9438e2afb049d2232dd9686406e8526 /randgen
parent0f8caadc96d1b34ac6bfe980fba660166ed65f9b (diff)
downloadmariadb-git-56274bd5e4115d86059936ddd3bf656dab1b4354.tar.gz
MDEV-23076 Misleading "InnoDB: using atomic writes"
As suggested by Vladislav Vaintroub, let us remove misleading and malformatted startup messages. Even if the global variable srv_use_atomic_writes were set, we would still invoke my_test_if_atomic_write() to check if writes are atomic with a particular page size. When using the default innodb_page_size=16k, page writes should be atomic on NTFS when using ROW_FORMAT=COMPRESSED and KEY_BLOCK_SIZE<=4. Disabling srv_use_atomic_writes when innodb_file_per_table=OFF does not make sense, because that is a dynamic parameter. We also correct the documentation string of innodb_use_atomic_writes and remove the duplicate variable innobase_use_atomic_writes.
Diffstat (limited to 'randgen')
0 files changed, 0 insertions, 0 deletions