summaryrefslogtreecommitdiff
path: root/extra
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch '10.3' into 10.4Oleksandr Byelkin2020-01-243-7/+9
|\
| * Merge branch '10.2' into 10.3Oleksandr Byelkin2020-01-243-7/+9
| |\
| | * Merge branch '10.1' into 10.2Oleksandr Byelkin2020-01-243-7/+9
| | |\
| | | * MDEV-17601: MariaDB Galera does not expect 'mbstream' as streamfmtJulius Goryavsky2020-01-213-7/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Setting "streamfmt=mbstream" in the "[sst]" section causes SST to fail because the format automatically switches to 'tar' by default (insead of mbstream). To fix this, we need to add mbstream to the list of valid values for the format, making it synonymous with xbstream. This must be done both in the SST script and when parsing the options of the corresponding utilities.
* | | | silence a warning in WolfSSL.Vladislav Vaintroub2020-01-211-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There is a warning about inconsistency between function definition and prototype. See https://github.com/wolfSSL/wolfssl/issues/2752 Disable specific MSVC warning for now.
* | | | new wolfssl v4.3.0-stableOleksandr Byelkin2020-01-201-0/+0
| | | |
* | | | Merge 10.3 into 10.4Marko Mäkelä2019-12-271-1/+3
|\ \ \ \ | |/ / /
| * | | Merge 10.2 into 10.3Marko Mäkelä2019-12-271-1/+3
| |\ \ \ | | |/ /
| | * | MDEV-19176 Reduce the memory usage during recoveryThirunarayanan Balathandayuthapani2019-12-231-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - Moved the recv_sys->heap memory condition inside recv_parse_log_recs(). So that, InnoDB can mark the status as STORE_NO earlier. - InnoDB uses one third of buffer pool chunk size for reading the redo log records. In that case, we can avoid the scenario where buffer ran out of memory issue during recovery.
* | | | Merge 10.3 into 10.4Marko Mäkelä2019-12-131-33/+9
|\ \ \ \ | |/ / / | | | | | | | | | | | | We disable the MDEV-21189 test galera.galera_partition because it times out.
| * | | Merge 10.2 into 10.3Marko Mäkelä2019-12-121-33/+9
| |\ \ \ | | |/ /
| | * | MDEV-21255: Deadlock of parallel slave and mariabackup (with failed logVlad Lesin2019-12-121-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | copy thread) mariabackup hangs waiting until innodb redo log thread read log till certain LSN, and it waits under FTWRL. If there is redo log read error in the thread, it is finished, and main thread knows nothing about it, what leads to hanging. As it hangs under FTWRL, slave threads on server side can be blocked due to MDL lock conflict. The fix is to finish mariabackup with error message on innodb redo log read failure.
| | * | MDEV-11345 Compile english error messages into mysqld executable.Vladislav Vaintroub2019-12-111-32/+6
| | | | | | | | | | | | | | | | | | | | Simplify loading messages into mariabackup. Do the same as server does We're forcing english, so there is no attempt to load errmsg.sys
* | | | Merge branch '10.3' into 10.4Oleksandr Byelkin2019-12-094-15/+24
|\ \ \ \ | |/ / /
| * | | Merge remote-tracking branch 10.2 into 10.3Jan Lindström2019-12-021-11/+20
| |\ \ \ | | |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: mysql-test/suite/galera/t/galera_binlog_event_max_size_max-master.opt mysql-test/suite/innodb/r/innodb-mdev-7513.result mysql-test/suite/innodb/t/innodb-mdev-7513.test mysql-test/suite/wsrep/disabled.def storage/innobase/ibuf/ibuf0ibuf.cc
| | * | MDEV-18310: Aria engine: Undo phase failed with "Got error 121 whenVlad Lesin2019-11-291-11/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | executing undo undo_key_delete" upon startup on datadir restored from incremental backup aria_log* files were not copied on --prepare --incremental-dir step from incremental to destination backup directory.
| * | | Lintian complains on spelling errorFaustin Lammler2019-12-026-10/+10
| | | | | | | | | | | | | | | | | | | | The lintian check complains on spelling error: https://salsa.debian.org/mariadb-team/mariadb-10.3/-/jobs/95739
* | | | Fix a couple of clang-cl warningsVladislav Vaintroub2019-11-151-2/+1
| | | |
* | | | MDEV-21062 Buildbot, Windows - sporadically missing lines from mtr's "exec"Vladislav Vaintroub2019-11-151-10/+13
| | | | | | | | | | | | | | | | | | | | Provide own version of popen/pclose, in attempt to workaround sporadic erratic behavior of UCRT's one.
* | | | Cleanup: Remove mach_read_ulint()Marko Mäkelä2019-11-081-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The function mach_read_ulint() is a wrapper for the lower-level functions mach_read_from_1(), mach_read_from_2(), mach_read_from_8(). Invoke those functions directly, for better readability of the code. mtr_t::read_ulint(), mtr_read_ulint(): Remove. Yes, we will lose the ability to assert that the read is covered by the mini-transaction. We would still check that on writes, and any writes that wrongly bypass mini-transaction logging would likely be caught by stress testing with Mariabackup.
* | | | Merge 10.3 into 10.4Marko Mäkelä2019-11-062-2/+2
|\ \ \ \ | |/ / /
| * | | Merge 10.2 into 10.3Marko Mäkelä2019-11-062-2/+2
| |\ \ \ | | |/ /
| | * | Merge 10.1 to 10.2Marko Mäkelä2019-11-062-2/+2
| | |\ \ | | | |/
| | | * Fix GCC 9.2.1 -Wstringop-truncationMarko Mäkelä2019-11-043-3/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | dict_table_rename_in_cache(): Use strcpy() instead of strncpy(), because they are known to be equivalent in this case (the length of old_name was already validated). mariabackup: Invoke strncpy() with one less than the buffer size, and explicitly add NUL as the last byte of the buffer.
| * | | compilation failure on ppc with -DCMAKE_BUILD_TYPE=DebugSergei Golubchik2019-10-221-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | if ${CRC32_LIBRARY} target has no COMPILE_FLAGS yet, GET_TARGET_PROPERTY returns COMPILE_FLAGS-NOTFOUND, which doesn't work very well when it's later fed back into COMPILE_FLAGS. GET_PROPERTY() returns an empty string in this case. Cherry-picked from 10.4 - 13e8f728ec83133b990ed21404cbac1d8a0bc74c Signed-off-by: Vicențiu Ciorbaru <vicentiu@mariadb.org>
* | | | Revert "wolfssl 4.2.0" (it is not ready jet)Oleksandr Byelkin2019-11-021-0/+0
| | | | | | | | | | | | | | | | This reverts commit dacd1794e43ae8fb6874f96458738b6fe4782555.
* | | | wolfssl 4.2.0Oleksandr Byelkin2019-11-021-0/+0
| | | |
* | | | Merge 10.3 into 10.4Marko Mäkelä2019-10-102-5/+5
|\ \ \ \ | |/ / /
| * | | Merge 10.2 into 10.3Marko Mäkelä2019-10-092-5/+5
| |\ \ \ | | |/ /
| | * | MDEV-19335 Remove buf_page_t::encryptedThirunarayanan Balathandayuthapani2019-10-091-3/+1
| | | | | | | | | | | | | | | | | | | | The field buf_page_t::encrypted was added in MDEV-8588. It was made mostly redundant in MDEV-12699. Remove the field.
| | * | MDEV-20703: mariabackup creates binlog files in server binlog directory on ↵Vlad Lesin2019-10-011-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | --prepare --export step When "--export" mariabackup option is used, mariabackup starts the server in bootstrap mode to generate *.cfg files for the certain innodb tables. The started instance of the server reads options from the file, pointed out in "--defaults-file" mariabackup option. If the server uses the same config file as mariabackup, and binlog is switched on in that config file, then "mariabackup --prepare --export" will create binary log files in the server's binary log directory, what can cause issues. The fix is to add "--skip-log-bin" in mysld options when the server is started to generate *.cfg files.
* | | | Merge 10.3 into 10.4Marko Mäkelä2019-09-234-10/+41
|\ \ \ \ | |/ / / | | | | | | | | Disable MDEV-20576 assertions until MDEV-20595 has been fixed.
| * | | Merge 10.2 into 10.3Marko Mäkelä2019-09-234-10/+41
| |\ \ \ | | |/ /
| | * | MDEV-18438 Don't stream xtrabackup_info of extra-lsndirSimon Lipp2019-09-194-10/+41
| | | |
* | | | Merge 10.3 into 10.4Marko Mäkelä2019-08-161-8/+3
|\ \ \ \ | |/ / /
| * | | Merge 10.2 into 10.3Marko Mäkelä2019-08-151-8/+3
| |\ \ \ | | |/ /
| | * | MDEV-19740: Silence a bogus "may be uninitialized" warningMarko Mäkelä2019-08-151-8/+3
| | | |
* | | | Merge 10.3 into 10.4Marko Mäkelä2019-08-142-2/+3
|\ \ \ \ | |/ / /
| * | | Merge 10.2 to 10.3Marko Mäkelä2019-08-132-2/+3
| |\ \ \ | | |/ /
| | * | Merge 10.1 into 10.2Marko Mäkelä2019-08-121-1/+2
| | |\ \ | | | |/
| | | * MDEV-17638 Improve error message about corruption of encrypted pagebb-10.1-MDEV-17638-improve-warningEugene Kosov2019-08-011-1/+2
| | | | | | | | | | | | | | | | Help user distinguish between space ID and page number.
| | * | MDEV-20060: Failing assertion: srv_log_file_size <= 512ULL << 30 while ↵Vlad Lesin2019-08-071-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| * | | Merge 10.2 into 10.3Eugene Kosov2019-07-161-1/+1
| |\ \ \ | | |/ /
| | * | Merge 10.1 into 10.2Eugene Kosov2019-07-091-1/+1
| | |\ \ | | | |/
| | | * imporve clang buildEugene Kosov2019-06-253-4/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | cmake -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang++ -DCMAKE_BUILD_TYPE=Debug Maintainer mode makes all warnings errors. This patch fix warnings. Mostly about deprecated `register` keyword. Too much warnings came from Mroonga and I gave up on it.
* | | | Do not compile socket IO code in WolfSSLVladislav Vaintroub2019-07-281-0/+1
| | | | | | | | | | | | | | | | We use own IO callbacks from server code anyway.
* | | | Update WolfSSL, remove older workarounds.Vladislav Vaintroub2019-07-282-4/+0
| | | |
* | | | Merge 10.3 into 10.4Marko Mäkelä2019-07-022-9/+84
|\ \ \ \ | |/ / /
| * | | Merge 10.2 into 10.3Marko Mäkelä2019-07-022-14/+89
| |\ \ \ | | |/ /
| | * | MDEV-19781 Add page id matching check in innochecksum toolThirunarayanan Balathandayuthapani2019-06-281-13/+88
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Added the condition in innochecksum tool to check page id mismatch. This could catch the write corruption caused by InnoDB. Added the debug insert inside fil_io() to check whether it writes the page to wrong offset.
View Lorry Controller Status