- 09 Jan, 2019 1 commit
-
-
Sergey Vojtovich authored
Simplified mutex code. MutexDebug uses OSMutex instead of atomic operations now.
-
- 08 Jan, 2019 4 commits
-
-
Marko Mäkelä authored
-
Vladislav Vaintroub authored
-
Marko Mäkelä authored
-
Thirunarayanan Balathandayuthapani authored
- Changed the performance schema query which gives sampling with event counting. It should fix the issue.
-
- 07 Jan, 2019 5 commits
-
-
Marko Mäkelä authored
dict_table_t::instant_column(): Correctly compute the value of metadata_changed. The original computation in commit 00372075 would essentially invoke memcmp(x,x,y), which can only return 0.
-
Sergey Vojtovich authored
buf_page_t::buf_fix_count transition to Atomic_counter.
-
Sergey Vojtovich authored
Replaced srv_fatal_semaphore_wait_threshold juggling with btr_validate_index_running counter. Removed last argument of btr_validate_index(): always false. Simplified away btr_validate_spatial_index().
-
Daniel Bartholomew authored
-
Marko Mäkelä authored
-
- 06 Jan, 2019 1 commit
-
-
Marko Mäkelä authored
-
- 04 Jan, 2019 7 commits
-
-
Jan Lindström authored
-
Jan Lindström authored
-
Elena Stepanova authored
-
Elena Stepanova authored
-
Jan Lindström authored
Make mariabackup.sh compatible on FreeBSD
-
Vladislav Vaintroub authored
-
Marko Mäkelä authored
-
- 03 Jan, 2019 8 commits
-
-
Marko Mäkelä authored
Fix an inadvertently inverted condition that caused galera.galera_sst_mariabackup_table_options test failure.
-
Marko Mäkelä authored
-
Marko Mäkelä authored
-
Marko Mäkelä authored
MDEV-18129 Backup fails for encrypted tables: mariabackup: Database page corruption detected at page 1 If an encrypted table is created during backup, then mariabackup --backup could wrongly fail. This caused a failure of the test mariabackup.huge_lsn once on buildbot. This is due to the way how InnoDB creates .ibd files. It would first write a dummy page 0 with no encryption information. Due to this, xb_fil_cur_open() could wrongly interpret that the table is not encrypted. Subsequently, page_is_corrupted() would compare the computed page checksum to the wrong checksum. (There are both "before" and "after" checksums for encrypted pages.) To work around this problem, we introduce a Boolean option --backup-encrypted that is enabled by default. With this option, Mariabackup will assume that a nonzero key_version implies that the page is encrypted. We need this option in order to be able to copy encrypted tables from MariaDB 10.1 or 10.2, because unencrypted pages that were originally created before MySQL 5.1.48 could contain nonzero garbage in the fields that were repurposed for encryption. Later, MDEV-18128 would clean up the way how .ibd files are created, to remove the need for this option. page_is_corrupted(): Add missing const qualifiers, and do not check space->crypt_data unless --skip-backup-encrypted has been specified. xb_fil_cur_read(): After a failed page read, output a page dump.
-
Sergei Golubchik authored
-
Sergei Golubchik authored
-
Sergei Golubchik authored
-
Sergei Golubchik authored
-
- 02 Jan, 2019 9 commits
-
-
Sergei Golubchik authored
-
Sergei Golubchik authored
-
Sergei Golubchik authored
-
Sergei Golubchik authored
-
Daniel Bartholomew authored
-
Sergei Golubchik authored
-
Sergei Golubchik authored
-
Sergei Golubchik authored
-
Tao ZHOU authored
-
- 01 Jan, 2019 2 commits
-
-
Marko Mäkelä authored
-
Michael Widenius authored
-
- 31 Dec, 2018 1 commit
-
-
Marko Mäkelä authored
-
- 30 Dec, 2018 1 commit
-
-
Sergei Golubchik authored
-
- 29 Dec, 2018 1 commit
-
-
Sergei Golubchik authored
-