mariadb/extra
Vlad Lesin d39d5dd2bc MDEV-20060: Failing assertion: srv_log_file_size <= 512ULL << 30 while preparing backup
The general reason why innodb redo log file is limited by 512G is that
log_block_convert_lsn_to_no() returns value limited by 1G. But there is no
need to have unique log block numbers in log group. The fix removes 512G
limit and limits log group size by
(uint32_t maximum value) * (minimum page size), which, in turns, can be
removed if fil_io() is no longer used for innodb redo log io.
2019-08-07 17:26:44 +03:00
..
crc32-vpmsum crc32-vpmsum: Restore non volatile registers on zero length CRC 2016-08-05 11:50:46 +04:00
mariabackup MDEV-20060: Failing assertion: srv_log_file_size <= 512ULL << 30 while preparing backup 2019-08-07 17:26:44 +03:00
readline Merge branch '5.5' into 10.1 2019-05-11 22:19:05 +03:00
yassl Merge 10.1 into 10.2 2019-07-09 13:22:22 +03:00
charset2html.c Merge branch '5.5' into 10.1 2019-05-11 22:19:05 +03:00
CMakeLists.txt Merge 10.1 into 10.2 2019-05-13 17:54:04 +03:00
comp_err.c Merge 10.1 into 10.2 2019-05-13 17:54:04 +03:00
innochecksum.cc MDEV-19781 Add page id matching check in innochecksum tool 2019-06-28 18:58:52 +05:30
my_print_defaults.c Merge branch '5.5' into 10.1 2019-05-11 22:19:05 +03:00
mysql_waitpid.c Update FSF Address 2019-05-11 21:29:06 +03:00
mysqld_safe_helper.c mysqld_safe_help - remove warning 2017-04-30 15:06:01 +04:00
perror.c Merge 10.1 into 10.2 2019-05-13 17:54:04 +03:00
replace.c Merge branch '5.5' into 10.1 2019-05-11 22:19:05 +03:00
resolve_stack_dump.c Merge 10.1 into 10.2 2019-05-13 17:54:04 +03:00
resolveip.c Update FSF Address 2019-05-11 21:29:06 +03:00