Last commit made on 2019-06-19
Get this branch:
git clone -b bb-5.5-sujatha

Branch merges

Branch information


Recent commits

fb61995... by Sujatha <email address hidden> on 2019-06-19

MDEV-15010: Wrong Seconds_Behind_Master when only starting the SQL_Thread

When I run replication normally, I get a value in "Seconds_Behind_Master" from
"SHOW SLAVE STATUS". However, when I run only the SQL Thread (on local relay
logs that have been downloaded previously), I have "NULL" in
"Seconds_Behind_Master". I would expect to have a numeric value.

Implemented following changes.
case 1: "Seconds_Behind_Master" shows 0, when SQL thread is in sync with IO
        thread and IO thread is running.
case 2: "Seconds_Behind_Master" reports NULL, when SQL thread is in sync with
        IO thread and IO thread is stopped.
case 3: "Seconds_Behind_Master" reports NULL, when SQL thread is stopped while
        IO thread is up and running.
case 4: "Seconds_Behind_Master" reports a valid numerical value when IO thread
        is stopped and SQL thread is consuming existing relay log.

7a7d990... by Marko Mäkelä on 2019-06-11

MDEV-18479: Avoid COST_MULT(records, 1)

96ee9ea... by Igor Babaev on 2019-06-11

MDEV-18479 Another complement

This patch complements the patch that fixes bug MDEV-18479.
This patch takes care of possible overflow in JOIN::get_examined_rows().

6db2ebb... by Igor Babaev on 2019-06-09

MDEV-19580 Unrelated JOINs corrupt usage of 'WHERE function() IN (subquery)'

Handling of top level conjuncts in WHERE whose used_tables() contained
RAND_TABLE_BIT in the function make_join_select() was incorrect.
As a result if such a conjunct referred to fields non of which belonged
to the last joined table it was pushed twice. (This could be seen
for a test case from subselect.test whose output was changed after this
patch had been applied. In 10.1 when running EXPLAIN FORMAT=JSON for
the query from this test case we clearly see that one of the conjuncts
is pushed twice.) This fact by itself was not good. Besides, if such a
conjunct was pushed to a table that was the result of materialization
of a semi-join the query could return a wrong result set. In particular
we could watch it for queries with semi-join subqueries whose left parts
used stored functions without "deterministic' specifier.

6660c07... by Sergei Golubchik on 2019-05-22

MDEV-19491 update query stopped working after mariadb upgrade 10.2.23 -> 10.2.24

as well as

MDEV-19500 Update with join stopped worked if there is a call to a procedure in a trigger
MDEV-19521 Update Table Fails with Trigger and Stored Function
MDEV-19497 Replication stops because table not found
MDEV-19527 UPDATE + JOIN + TRIGGERS = table doesn't exists error

Reimplement the fix for (5d510fdbf00)

MDEV-18507 can't update temporary table when joined with table with triggers on read-only

instead of calling open_tables() twice, put multi-update
prepare code inside open_tables() loop.

Add a test for a MDL backoff-and-retry loop inside open_tables()
across multi-update prepare code.

1d4ac3d... by Sergei Golubchik on 2019-05-22


5de08a5... by Eugene on 2019-04-11

MDEV-13631 Make use of clang-format

Add .clang-format files to a root directory and to storage/innobase

cbb90f7... by Igor Babaev on 2019-05-29

MDEV-18479 Complement

This patch complements the patch that fixes bug MDEV-18479.
This patch takes care of possible overflow when calculating the
estimated number of rows in a materialized derived table / view.

eb09580... by Igor Babaev on 2019-05-28

MDEV-19588 Wrong results from query, using left join.

This bug could happen when queries with nested outer joins were
executed employing join buffers. At such an execution if the method
JOIN_CACHE::join_records() is called when a join buffer has become
full no 'first_unmatched' field should be cleaned up in the JOIN_TAB
structure to which the join cache with this buffer is attached.

0955462... by Igor Babaev on 2019-05-28

MDEV-18479 Assertion `join->best_read < double(1.79769313486231570815e+308L)'
or server crashes in JOIN::fix_all_splittings_in_plan after EXPLAIN

This patch resolves the problem of overflowing when performing
calculations to estimate the cost of an evaluated query execution plan.
The overflowing in a non-debug build could cause different kind of
problems uncluding crashes of the server.