- 24 Dec, 2021 1 commit
-
-
Thirunarayanan Balathandayuthapani authored
This issue is caused by MDEV-24621 (commit 045757af). InnoDB tries to insert the number of rows into an empty spatial index table, but it fails to apply the buffered insert. InnoDB should insert into the spatial index directly instead of buffering the insert operation.
-
- 21 Dec, 2021 2 commits
-
-
Sergei Golubchik authored
-
Sergei Golubchik authored
-
- 14 Dec, 2021 2 commits
-
-
Marko Mäkelä authored
-
mkaruza authored
SQL statments could have table entries added in lexer. This entries should not invalidate `next_global` member. Reviewed-by: Jan Lindström <jan.lindstrom@mariadb.com>
-
- 12 Dec, 2021 3 commits
-
-
Thirunarayanan Balathandayuthapani authored
- Addressing the format issue in deferred_dblwr() and changed the function comment.
-
Thirunarayanan Balathandayuthapani authored
InnoDB fails to identify the deferred tablespace after recovery. Problem is that InnoDB fails to rename the tablespace present in recovered tablespace. Fix is that InnoDB should try to rename the recovered tablespace when tablespace is being deferred
-
Thirunarayanan Balathandayuthapani authored
This patch reverts the commit cab8f4b5. InnoDB fails to restore page0 from doublewrite buffer when the tablespace is being deferred. In that case, InnoDB doesn't find INIT_PAGE redo log record for page0 and it leads to failure. InnoDB should recovery page0 from doublewrite buffer for the deferred tablespace before applying the redo log records. Added deferred_dblwr() to restore page0 of deferred tablespace from doublewrite buffer
-
- 10 Dec, 2021 4 commits
-
-
Marko Mäkelä authored
-
Marko Mäkelä authored
-
Marko Mäkelä authored
-
Marko Mäkelä authored
In commit 49e2c8f0 (MDEV-25743) some more use of the printf-style format "%.*s" was added. The length parameter is of type int, not size_t. On 64-bit platforms that follow the LLP64 convention (such as 64-bit Microsoft Windows), sizeof(int)==4 and sizeof(size_t)==8. Let us explicitly cast the lengths to the correct type in order to avoid any trouble.
-
- 08 Dec, 2021 3 commits
-
-
Sergei Golubchik authored
-
Sergei Golubchik authored
-
Sergei Golubchik authored
-
- 07 Dec, 2021 8 commits
-
-
Sergei Golubchik authored
-
Sergei Golubchik authored
BUG#31761802 STATISTICS ANY QUERIES USING VIEWS ARE SUMMARIZED TOGETHER WITH THE VIEW DEFINITION SELECT test case only
-
Sergei Golubchik authored
now when SLES12.3 is gone, we can enforce it
-
Sergei Golubchik authored
-
Sergei Golubchik authored
-
Marko Mäkelä authored
During startup, InnoDB must write a FILE_CHECKPOINT record. However, before MDEV-12353 (in MariaDB Server 10.2, 10.3, 10.4) the corresponding record MLOG_CHECKPOINT was encoded in a different way. When we are upgrading from a logically empty 10.2, 10.3, or 10.4 redo log, we must not write anything to the old log file, because if the server were killed during the upgrade, we would end up with a corrupted log file, and both the old and the new server would refuse to start up. On upgrade, we must simply create a new logically empty log file and replace the old ib_logfile0 with that.
-
Eugene Kosov authored
This is a low hanging fruit. Before this patch std::map::emplace() was a ~50% of the whole recv_sys_t::parse() operation in by test. After the fix it's only ~20%. recv_sys_t::parse() recv_sys_t::pages is a collection of all pages to recovery. Often, there are multiple changes for a single page. Often, they go in a row and for such cases let's avoid lookup in a std::map. cached_pages_it serves as a cache of size 1. recv_sys_t::add(): replace page_id argument with a std::map::iterator
-
Sergei Golubchik authored
-
- 06 Dec, 2021 4 commits
-
-
Sergei Golubchik authored
-
Sergei Golubchik authored
-
Sergei Golubchik authored
-
Eugene Kosov authored
-
- 04 Dec, 2021 3 commits
-
-
Marko Mäkelä authored
-
Marko Mäkelä authored
page_zip_des_t::clear(): Avoid a bogus GCC warning with some pointer arithmetics. Yes, storing the unrelated member "fix" in this object is ugly, but it avoids memory alignment overhead on 64-bit architectures.
-
Marko Mäkelä authored
-
- 03 Dec, 2021 6 commits
-
-
Marko Mäkelä authored
In commit aae3f921 recv_apply_hashed_log_recs() was replaced by recv_sys_t::apply().
-
Eugene Kosov authored
log_write_buf(): do not cast to size_t which prevents to write to files which a bigger that 4G and remove useless assertion
-
Marko Mäkelä authored
-
Marko Mäkelä authored
A part of the test main.long_unique attempts to insert records with two 60,000,001-byte columns. Let us move that test into a separate file main.long_unique_big, declared as big test, so that it can be skipped in environments with limited memory.
-
Christopher Odenbach authored
How 'bout know?
-
Christopher Odenbach authored
Hi, if the pid-file option is configured more than once (e.g. multiple times in different files), my_print_defaults prints it twice, resulting in the logrotate postrotate script failing because of a syntax error. Debian fixed this already (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830976#42). Perhaps you could implement this small change in the other branches as well? Thanks, Christopher
-
- 02 Dec, 2021 2 commits
-
-
Marko Mäkelä authored
-
Lukas Javorsky authored
Include gronnga and groonga-normalizer-mysql install path
-
- 01 Dec, 2021 2 commits
-
-
Marko Mäkelä authored
Several EXTENDED type records have already been implemented.
-
Thirunarayanan Balathandayuthapani authored
- Replaced the pointer parameter of validate_for_recovery() with uint32_t
-