2
# Tests the behvaiour of the transaction-log-sync-method
3
# configuration option. At this point, the only thing we
4
# can check is that the options appear in the INFORMATION_SCHEMA.VARIABLES
5
# view, since I can't think of a way to test fsync() behaviour
6
# properly through the test suite...it might be that we just do this
7
# basic variables test and rely on LCOV code coverage to check
11
SELECT * FROM DATA_DICTIONARY.GLOBAL_VARIABLES
12
WHERE Variable_name LIKE 'transaction_log%';