Home - Waterfall Grid T-Grid Console Builders Recent Builds Buildslaves Changesources - JSON API - About

Console View

Categories: connectors experimental galera main
Legend:   Passed Failed Warnings Failed Again Running Exception Offline No data

connectors experimental galera main
Marko Mäkelä
MDEV-24188: Merge 10.2 into 10.3
Do not run maria.repair with --embedded as memory usage is different
Marko Mäkelä
Merge mariadb-10.2.36 into 10.2
Sergei Petrunia
MDEV-24117: Memory management problem (in range optimizer)

Adjust the testcase for MariaDB 10.3+ : prevent IN-to-subquery conversion
optimization from working.
Marko Mäkelä
Cleanup: Remove dict_space_is_empty(), dict_space_get_id()

As noted in commit 0b66d3f70d365bbb936aae4ca67892c17d68d241,
MariaDB does not support CREATE TABLESPACE for InnoDB.
Hence, some code that was added in
commit fec844aca88e1c6b9c36bb0b811e92d9d023ffb9
and originally in
is unused in MariaDB and should be removed.
Anel Husakovic
MDEV-23769: MTR can abort before it prints the test result summary

- Patch is solving generating report on warning
        To repeat the error run single worker:
        ./mtr --mysqld=--lock-wait-timeout=-xx 1st 1st --force --parallel 1
        or `N` workers with `N+1` tests with failures and `force`
        ./mtr --mysqld=--lock-wait-timeout=-xx 1st 1st grant5 --force --parallel 2
- Patch is doing cosmetic fix of `current_test` log file which holds the old log value of test `CURRENT TEST:..` in `mark_log()` in case of `unknown option` and as such
  the logic which is using it's content doesn't output valid log content and doesn't generate valid `$test->{'comment'}` message.asdf

- Closing the socket/handler after the removing the handler from IO for

Reviewed by: serg@mariadb.com
Oleksandr Byelkin
Fix to make it compiling on new ubuntu.
Sergei Golubchik
cleanup: RAII helper for changing thd->count_cuted_rows
Igor Babaev
MDEV-23811: With large number of indexes optimizer chooses an inefficient plan

This bug could manifest itself for a query with WHERE condition containing
top level OR formula such that each conjunct contained a single-range
condition supported by the same index. One of these range conditions must
be fully covered by another range condition that is used later in the OR
formula. Additionally at least one of these condition should be ANDed with
a sargable range condition supported by a different index.

There were several attempts to fix related problems for OR conditions after
the backport of range optimizer code from MySQL (commit
0e19f3e36f7842583feb6bead2c2600cd620bced). Unfortunately the first of these
fixes contained typo remained unnoticed until recently. This typo bug led
to rejection of valid range accesses. This patch fixed this typo bug.
The fix revealed another two bugs: one in a constructor for SEL_ARG,
the other in the function tree_or(). Both are fixed in this patch.