lp:maria

Owned by Maria-captains
Get this repository:
git clone https://git.launchpad.net/maria

Import details

Import Status: Reviewed

This repository is an import of the Git repository at https://github.com/MariaDB/server.git.

The next import is scheduled to run in 47 minutes.

Last successful import was 5 hours ago.

Import started 5 hours ago on alnitak and finished 5 hours ago taking 3 minutes — see the log
Import started 11 hours ago on alnitak and finished 11 hours ago taking 3 minutes — see the log
Import started 17 hours ago on alnitak and finished 17 hours ago taking 3 minutes — see the log
Import started 23 hours ago on alnitak and finished 23 hours ago taking 3 minutes — see the log
Import started on 2020-05-27 on alnitak and finished on 2020-05-27 taking 3 minutes — see the log
Import started on 2020-05-27 on alnitak and finished on 2020-05-27 taking 3 minutes — see the log
Import started on 2020-05-26 on alnitak and finished on 2020-05-26 taking 3 minutes — see the log
Import started on 2020-05-26 on alnitak and finished on 2020-05-26 taking 3 minutes — see the log
Import started on 2020-05-26 on alnitak and finished on 2020-05-26 taking 2 minutes — see the log
Import started on 2020-05-25 on alnitak and finished on 2020-05-25 taking 3 minutes — see the log

Branches

Name Last Modified Last Commit
bb-10.4-MDEV-21910-v2 2020-05-06 06:27:12 UTC 2020-05-06
Analysis from 10.4

Author: Jan Lindström
Author Date: 2020-04-29 11:46:52 UTC

Analysis from 10.4

BF abort:
wsrep_kill_victim (lock_sys->mutex, trx->mutex) => wsrep_kill_one_trx (thd->LOCK_thd_data)

KILL QUERY:
find_thread_by_id(thd->LOCK_thd_data , thd->LOCK_thd_kill) => thd->awake_no_mutex() => innobase_kill_query() => lock_trx_handle_wait( lock_sys->mutex, trx->mutex if not wsrep victim)

From these only lock_sys->mutex is global mutex. All others are either thread internal (thd) or transaction internal (trx). Therefore, mutex deadlock is possible if and only if thread we have selected as victim for BF abort and thread user is trying to kill are exactly the same one. While BF abort also will call thd->awake() it will have trx->lock.was_chosen_as_wsrep_victim=true and then we do not take lock_sys->mutex or trx->mutex at lock_trx_handle_wait(). Second problem is possible when in wsrep_kill_one_trx() we set trx->lock.was_chosen_as_wsrep_victim=true and release thd->LOCK_thd_data mutex. Now if we have a schedule where KILL is executed there is possibility that we either try to take lock_sys->mutex and have to wait or if this is same thread as victim no InnoDB mutexes are taken. Furthermore, in bf_abort() we might take thd->LOCK_thd_data again in wsrep-lib.

In this fix candidate we release lock_sys->mutex and trx->mutex before
we call wsrep_innobase_kill_one_trx(). Thus, it is safe to take
thd->LOCK_thd_data similarly as KILL does. We can remove
was_chosen_as_wsrep_victim variable from trx as it is not anymore
needed.

bb-10.2-varun 2020-05-05 15:22:44 UTC 2020-05-05
MDEV-22461: JOIN::make_aggr_tables_info(): Assertion `select_options & (1ULL ...

Author: varun
Author Date: 2020-05-05 15:14:43 UTC

MDEV-22461: JOIN::make_aggr_tables_info(): Assertion `select_options & (1ULL << 17)' failed.

A temporary table is needed for window function computation but if only a NAMED WINDOW SPEC
is used and there is no window function, then there is no need to create a temporary
table as there is no stage to compute WINDOW FUNCTION

bb-10.4-MDEV-20502 2020-05-05 13:41:10 UTC 2020-05-05
MDEV-20502 Queries against spider tables return wrong values for columns foll...

Author: Kentoku SHIBA
Author Date: 2020-05-05 13:41:10 UTC

MDEV-20502 Queries against spider tables return wrong values for columns following constant declarations.

Add test cases.

bb-10.3-serg 2020-05-05 12:12:30 UTC 2020-05-05
MDEV-22123 On RHEL8 mariadb-server is not provided

Author: Sergei Golubchik
Author Date: 2020-05-04 21:25:20 UTC

MDEV-22123 On RHEL8 mariadb-server is not provided

setup alternative name for rhel8/centos8

use correct C/C version when providing mariadb-connector-c

bb-10.5-sujatha 2020-05-05 10:13:33 UTC 2020-05-05
MDEV:20220: Add status variable that gets incremented if slave's parallel wor...

Author: Sujatha Sivakumar
Author Date: 2020-05-05 10:13:33 UTC

MDEV:20220: Add status variable that gets incremented if slave's parallel worker thread is idle due to full queue

Fix: Added a new status variable named 'Slave_idle_parallel_worker_count'.
The variable gets incremented whenever a worker enters idle state. ie
Workers state in SHOW PROCESSLIST becomes "Waiting for work from SQL thread".
'Slave_idle_parallel_worker_count' variable gets cleared during START SLAVE.

bb-10.5-serg 2020-05-04 19:03:07 UTC 2020-05-04
MDEV-22424 Server crashes in handler::check_duplicate_long_entry_key or Asser...

Author: Sergei Golubchik
Author Date: 2020-05-04 09:32:08 UTC

MDEV-22424 Server crashes in handler::check_duplicate_long_entry_key or Assertion `inited == NONE || lookup_handler != this' failed upon DELETE FOR PORTION on table with long unique key

even if we're *allowed to* convert DELETE .. FOR PERIOD OF
into an update internally, doesn't think we'll *be able to*.

We always have to prepare for insert.

bb-10.4-MDEV-19650 2020-05-04 10:26:10 UTC 2020-05-04
MDEV-19650: Privilege bug on MariaDB 10.4

Author: Oleksandr Byelkin
Author Date: 2020-02-19 16:50:30 UTC

MDEV-19650: Privilege bug on MariaDB 10.4

Also fixes:
MDEV-21487: Implement option for mysql_upgrade that allows root@localhost to be replaced
MDEV-21486: Implement option for mysql_install_db that allows root@localhost to be replaced

Add user mariadb.sys to be definer of user view
(and has right on underlying table global_priv for
required operation over global_priv
(SELECT,UPDATE,DELETE))

Also changed definer of gis functions in case of creation,
but they work with any definer so upgrade script do not try
to push this change.

bb-10.4-mdev22377 2020-04-29 22:25:11 UTC 2020-04-29
MDEV-22377: Subquery in an [UPDATE] query uses full scan instead of range

Author: Sergey Petrunia
Author Date: 2020-04-29 22:25:11 UTC

MDEV-22377: Subquery in an [UPDATE] query uses full scan instead of range

When doing IN->EXISTS rewrite, Item_in_subselect::inject_in_to_exists_cond
injects equalities into subquery's WHERE condition.

The problem is that build_equal_items() has already been called for the
subquery's WHERE, and tampering with the WHERE condition can prevent
equality propagation from working.

If the subquery's WHERE is an Item_cond_and with multiple equalities:
- Item_equal objects form a suffix sub-list of the list in WHERE's
  Item_cond_and::list. The suffix is stored in
  JOIN::cond_equal->current_level.
- Item_cond_and::m_cond_equal must also be preserved.

This patch makes inject_in_to_exists_cond() not to break these properties

bb-5.5-serg 2020-04-29 19:31:09 UTC 2020-04-29
BUG#30301356 - SOME EVENTS ARE DELAYED AFTER DROPPING EVENT

Author: Sergei Golubchik
Author Date: 2020-04-28 09:20:52 UTC

BUG#30301356 - SOME EVENTS ARE DELAYED AFTER DROPPING EVENT

queues.c cleanup and refactoring.

Restore old version of _downhead() (from before cd483c55209)
that works well in an average case. Use it for queue_fix().

Move existing specialized version of _downhead() to queue_replace()
where it'll be handling the case it was specifically optimized for
(moving the element to the end of the queue).
And correct it to fix the heap not only down, but also up
(this fixes BUG#30301356).

Add unit tests.

Collateral cosmetic fixes.

bb-10.4-MDEV-21910 2020-04-29 07:13:31 UTC 2020-04-29
MDEV-21910 : KIlling thread on Galera could cause mutex deadlock

Author: Jan Lindström
Author Date: 2020-04-29 07:13:31 UTC

MDEV-21910 : KIlling thread on Galera could cause mutex deadlock

WIP

Analysis from 10.4

BF abort:
wsrep_kill_victim (lock_sys->mutex, trx->mutex) => wsrep_kill_one_trx (thd->LOCK_thd_data)

KILL QUERY:
find_thread_by_id(thd->LOCK_thd_data , thd->LOCK_thd_kill) => thd->awake_no_mutex() => innobase_kill_query() => lock_trx_handle_wait( lock_sys->mutex, trx->mutex if not wsrep victim)

From these only lock_sys->mutex is global mutex. All others are either thread internal (thd) or transaction internal (trx). Therefore, mutex deadlock is possible if and only if thread we have selected as victim for BF abort and thread user is trying to kill are exactly the same one. While BF abort also will call thd->awake() it will have trx->lock.was_chosen_as_wsrep_victim=true and then we do not take lock_sys->mutex or trx->mutex at lock_trx_handle_wait(). Second problem is possible when in wsrep_kill_one_trx() we set trx->lock.was_chosen_as_wsrep_victim=true and release thd->LOCK_thd_data mutex. Now if we have a schedule where KILL is executed there is possibility that we either try to take lock_sys->mutex and have to wait or if this is same thread as victim no InnoDB mutexes are taken. Furthermore, in bf_abort() we might take thd->LOCK_thd_data again in wsrep-lib.

10.5-varun 2020-04-29 07:06:04 UTC 2020-04-29
MDEV-22399: Remove multiple calls to enable and disable Handler::keyread and ...

Author: varun
Author Date: 2020-04-23 05:54:24 UTC

MDEV-22399: Remove multiple calls to enable and disable Handler::keyread and perform it after the plan refinement phase is done

Introduce a function to enable keyreads for indexes and use this
function when all the decision of plan refinement phase are done.

bb-10.4-mdev22401 2020-04-28 22:13:52 UTC 2020-04-28
MDEV-22401: Optimizer trace: multi-component range is not printed correctly

Author: Sergey Petrunia
Author Date: 2020-04-28 22:13:52 UTC

MDEV-22401: Optimizer trace: multi-component range is not printed correctly

KEY_MULTI_RANGE::range_flag does not have correct flag bits for
per-endpoint flags (NEAR_MIN, NEAR_MAX, NO_MIN_RANGE, NO_MAX_RANGE).
It only has bits for flags that describe both endpoints.
So
- Document this.
- Switch optimizer trace to using {start|end}_key.flag values, instead.
  This fixes the bug.
- Switch records_in_column_ranges() to doing that too. (This used to
  work, because KEY_MULTI_RANGE::range_flag had correct flag value
  for the last key component, and EITS only uses one-component
  pseudo-indexes)

bb-10.4-serg 2020-04-28 13:12:02 UTC 2020-04-28
fix the test for windows

Author: Sergei Golubchik
Author Date: 2020-04-27 13:05:18 UTC

fix the test for windows

bb-10.3-kevgs 2020-04-28 12:40:54 UTC 2020-04-28
split log_t::buf into two buffers

Author: Eugene
Author Date: 2020-04-27 21:40:13 UTC

split log_t::buf into two buffers

Maybe this patch will help catch problems like buffer overflow.

log_t::first_in_use: removed

log_t::buf: this is where mtr_t are supposed to append data
log_t::flush_buf: this is from server writes to a file

Those two buffers are std::swap()ped when some thread is gonna write
to a file

bb-10.4-svoj 2020-04-28 10:44:07 UTC 2020-04-28
MDEV-19508 - Issue with: #define SI_KERNEL

Author: Sergey Vojtovich
Author Date: 2020-04-28 10:25:42 UTC

MDEV-19508 - Issue with: #define SI_KERNEL

Reverted 07e9b1389, use setsid() instead.

Conventional use of SIGHUP to dump daemon information or flush caches
assumes preceeding setsid() call.

Ideally we should not setup SIGHUP handler in bootstrap and (probably)
debug_gdb modes.

Additional information on SysV style and systemd style daemons:
https://www.freedesktop.org/software/systemd/man/daemon.html

bb-5.5-MDEV-22374 2020-04-28 07:16:33 UTC 2020-04-28
MDEV-22374: VIEW with security definer require FILE privilege from definer no...

Author: Oleksandr Byelkin
Author Date: 2020-04-28 07:16:33 UTC

MDEV-22374: VIEW with security definer require FILE privilege from definer not invoker in case of INTO OUTFILE

Check INTO OUTFILE clause always from invoker.

bb-10.4-MDEV-20230-ftwrl-wait-timeout 2020-04-27 19:29:24 UTC 2020-04-27
MDEV-20230: mariabackup --ftwrl-wait-timeout never times out on explicit

Author: Vlad Lesin
Author Date: 2020-04-27 18:46:05 UTC

MDEV-20230: mariabackup --ftwrl-wait-timeout never times out on explicit
lock

--ftwrl-wait-timeout does not finish mariabackup execution when acquired
backup lock can't be grabbed for the certain amount of time, it just
waits for a long queries finishing before acquiring the lock to avoid
unnecessary locking.

This commit extends --ftwrl-wait-timeout so, that mariabackup execution
is finished if it waits for backup lock during certain amount of time.

bb-10.5-6915-ext 2020-04-27 15:19:07 UTC 2020-04-27
Compilation fix

Author: midenok
Author Date: 2020-04-27 15:19:07 UTC

Compilation fix

bb-10.2-svoj 2020-04-27 14:49:29 UTC 2020-04-27
MDEV-17749 - ALTER TABLE asserts under LOCK TABLES

Author: Sergey Vojtovich
Author Date: 2020-04-27 13:32:02 UTC

MDEV-17749 - ALTER TABLE asserts under LOCK TABLES

Regression after 43f6e118f caused by "automatic UNLOCK TABLES if we
don't have any locked tables (safety fix)", which didn't commit (or
rollback) pending transaction prior to leaving locked tables mode.

Leaving locked tables mode is a bit more complex than calling
unlock_locked_tables(), see e.g. SQLCOM_UNLOCK_TABLES branch of
mysql_execute_command(). Also such leaving should've been done
consistently in all cases whenever a table gets unlock.

Given that the above is hardly doable in old-GA, reverted part of the
43f6e118f. It doesn't seem to be required to fix the original problem
as original test passes without this change.

bb-10.2-robert 2020-04-27 13:18:59 UTC 2020-04-27
MDEV-20685: server_audit fix in auditing_v8

Author: Daniel Black
Author Date: 2020-04-04 10:58:04 UTC

MDEV-20685: server_audit fix in auditing_v8

Fixes compile warnings on Solaris

[ 91%] Building C object plugin/server_audit/CMakeFiles/server_audit.dir/server_audit.c.o
/plugin/server_audit/server_audit.c: In function 'auditing_v8':
/plugin/server_audit/server_audit.c:2194:20: error: unused variable 'db_len_off' [-Werror=unused-variable]
 2194 | static const int db_len_off= 128;
      | ^~~~~~~~~~
/plugin/server_audit/server_audit.c:2193:20: error: unused variable 'db_off' [-Werror=unused-variable]
 2193 | static const int db_off= 120;
      | ^~~~~~
/plugin/server_audit/server_audit.c:2192:20: error: unused variable 'cmd_off' [-Werror=unused-variable]
 2192 | static const int cmd_off= 4432;
      | ^~~~~~~
At top level:
/plugin/server_audit/server_audit.c:2192:20: error: 'cmd_off' defined but not used [-Werror=unused-const-variable=]
/plugin/server_audit/server_audit.c:2193:20: error: 'db_off' defined but not used [-Werror=unused-const-variable=]
 2193 | static const int db_off= 120;
      | ^~~~~~
/plugin/server_audit/server_audit.c:2194:20: error: 'db_len_off' defined but not used [-Werror=unused-const-variable=]
 2194 | static const int db_len_off= 128;
      | ^~~~~~~~~~
cc1: all warnings being treated as errors

bb-10.4-MDEV-22203 2020-04-23 14:48:48 UTC 2020-04-23
Trigger retest

Author: Jan Lindström
Author Date: 2020-04-23 14:48:48 UTC

Trigger retest

bb-10.5-wlad-MDEV-21612 2020-04-23 14:35:13 UTC 2020-04-23
MDEV-21612 Remove COM_MULTI

Author: Vladislav Vaintroub
Author Date: 2020-04-21 23:57:53 UTC

MDEV-21612 Remove COM_MULTI

remove com_multi from the C/C as well.

columnstore_cache 2020-04-23 13:45:47 UTC 2020-04-23
Column_store_cache, stage 1

Author: Monty
Author Date: 2020-04-19 09:07:16 UTC

Column_store_cache, stage 1

This is implemented on top of csv engine. Should be moved to ColumnStore
ASAP

bb-10.3-marko 2020-04-23 13:41:34 UTC 2020-04-23
MDEV-22351 RESET MASTER should be propagated to InnoDB

Author: Marko Mäkelä
Author Date: 2020-04-23 13:41:34 UTC

MDEV-22351 RESET MASTER should be propagated to InnoDB

Ever since commit 947efe17ed8188ca4feef6deb0c2831a246b5c8f
InnoDB no longer writes binlog position in one place.
It will not at all be written to the TRX_SYS page, and
instead it will be written to the undo log header page that
changes the transaction state.

ha_reset_master(), trx_rseg_reset_binlog_pos(): Reset the
binlog information in InnoDB when RESET MASTER is invoked.

reset_master(): Invoke ha_reset_master() to discard the
information in InnoDB.

bb-10.3-MDEV-19273 2020-04-23 12:30:48 UTC 2020-04-23
MDEV-19273: Server crash in MDL_ticket::has_stronger_or_equal_type or Asserti...

Author: Oleksandr Byelkin
Author Date: 2020-03-22 10:33:53 UTC

MDEV-19273: Server crash in MDL_ticket::has_stronger_or_equal_type or Assertion `thd->mdl_context.is_lock_owner(MDL_key::TABLE, table->db.str, table->table_name.str, MDL_SHARED)' failed in mysql_rm_table_no_locks

Early report error in case of DROP SEQUENCE <non-sequence>

Do not use error variable for other purposes except error.

bb-10.5-elenst 2020-04-23 08:26:01 UTC 2020-04-23
MDEV-22349 MTR re-bootstrap modifies environment variable MYSQLD_BOOTSTRAP_CMD

Author: Elena Stepanova
Author Date: 2020-04-23 01:49:24 UTC

MDEV-22349 MTR re-bootstrap modifies environment variable MYSQLD_BOOTSTRAP_CMD

bb-10.1-elenst 2020-04-23 01:49:24 UTC 2020-04-23
MDEV-22349 MTR re-bootstrap modifies environment variable MYSQLD_BOOTSTRAP_CMD

Author: Elena Stepanova
Author Date: 2020-04-23 01:49:24 UTC

MDEV-22349 MTR re-bootstrap modifies environment variable MYSQLD_BOOTSTRAP_CMD

bb-10.1-anel-MDEV-22313 2020-04-22 18:48:55 UTC 2020-04-22
MDEV-22313: Neither SHOW CREATE USER nor SHOW GRANTS prints a user's default ...

Author: Anel Husakovic
Author Date: 2020-04-22 18:13:21 UTC

MDEV-22313: Neither SHOW CREATE USER nor SHOW GRANTS prints a user's default role

bb-10.5-vicentiu 2020-04-22 18:29:16 UTC 2020-04-22
DO NOT PUSH THIS COMMIT! Force a rebuild

Author: Vicențiu Ciorbaru
Author Date: 2020-04-22 18:29:16 UTC

DO NOT PUSH THIS COMMIT! Force a rebuild

bb-10.2-galera 2020-04-22 04:54:52 UTC 2020-04-22
MDEV-22159: Don't redirect as root to a tmp file not owned by root

Author: Otto Kekäläinen
Author Date: 2020-04-21 18:14:54 UTC

MDEV-22159: Don't redirect as root to a tmp file not owned by root

Also add a check for tmp file being empty and bail out with a clear
error message in such a case, as mysqld_safe prevents normal stderr
from being displayed anywhere and would fail silently on this.

bb-10.1-MDEV-21117 2020-04-20 09:32:09 UTC 2020-04-20
MDEV-21117: Fixing windows build failure.

Author: Sujatha Sivakumar
Author Date: 2020-04-20 09:31:33 UTC

MDEV-21117: Fixing windows build failure.

Addressing Marko's review comments.

10.5-mdev8306 2020-04-20 04:24:14 UTC 2020-04-20
Implement a bush for the materialized nest

Author: varun
Author Date: 2020-04-15 05:51:37 UTC

Implement a bush for the materialized nest

bb-10.5-midenok-MDEV-17554 2020-04-19 19:35:39 UTC 2020-04-19
Buildbot fixes

Author: midenok
Author Date: 2020-04-19 19:34:52 UTC

Buildbot fixes

bb-10.3-MDEV-21884 2020-04-16 16:49:46 UTC 2020-04-16
MDEV-21884 MariaDB with Spider crashes on a query

Author: Kentoku SHIBA
Author Date: 2020-04-16 16:49:46 UTC

MDEV-21884 MariaDB with Spider crashes on a query

bb-10.2-MDEV-20638 2020-04-16 10:44:36 UTC 2020-04-16
MDEV-20638 Remove the deadcode from srv_master_thread() and srv_active_wake_m...

Author: THIRUNARAYANAN BALATHANDAYUTHAPANI
Author Date: 2020-04-16 10:44:36 UTC

MDEV-20638 Remove the deadcode from srv_master_thread() and srv_active_wake_master_thread_low()

- Changed srv_check_activity() parameter.

bb-10.5-MDEV-21910 2020-04-16 09:36:56 UTC 2020-04-16
Fix embedded server compilation errors.

Author: Jan Lindström
Author Date: 2020-04-16 09:36:56 UTC

Fix embedded server compilation errors.

bb-10.3-MDEV-20100 2020-04-15 15:44:20 UTC 2020-04-15
MDEV-20100 MariaDB 13.3.9 Crash "[ERROR] mysqld got signal 11 ;"

Author: Kentoku SHIBA
Author Date: 2020-04-15 15:44:20 UTC

MDEV-20100 MariaDB 13.3.9 Crash "[ERROR] mysqld got signal 11 ;"

Some functions on ha_partition call functions on all partitions, but handler->reset() is only called that pruned by m_partitions_to_reset. So Spider didn't clear pointer on unpruned partitions, if the unpruned partitions are used by next query, Spider reference the pointer that is already freed.

10.5-order_by_limit 2020-04-15 04:56:46 UTC 2020-04-15
more test added

Author: varun
Author Date: 2020-04-15 04:56:46 UTC

more test added

bb-10.1-vicentiu 2020-04-14 09:46:05 UTC 2020-04-14
mtr: Only old windows patch-2.5.9 needs --binary

Author: Daniel Black
Author Date: 2020-03-31 00:39:36 UTC

mtr: Only old windows patch-2.5.9 needs --binary

Windows GNU patch 2.7.6 is ok without it.

So account for the old buildbot version for now.

Linux works without it.

--binary fails on FreeBSD-12.0:

$ patch --version
patch 2.0-12u11 FreeBSD
$ patch --binary
patch: unrecognized option `--binary'

bb-10.2-vicentiu 2020-04-13 11:47:32 UTC 2020-04-13
Travis-CI: Shorten deb build log to keep it under 4 MB

Author: Otto Kekäläinen
Author Date: 2020-04-05 20:55:23 UTC

Travis-CI: Shorten deb build log to keep it under 4 MB

There is a 4 MB hard limit on Travis-CI and build output needs to be less
than that. Silencing the 'make install' step gets rid of a lot of
"Installing.." and "Missing.." and removing all mysql-test files will
make the dh_missing warnings much shorter.

Cherry-picked from 41952c85f1644690249ce624de7609cbebb93638.

bb-10.3-vicentiu 2020-04-10 13:32:03 UTC 2020-04-10
MDEV-21984: POWER crc32 acceleration - fix clang's behavior on versions >= 7

Author: Tulio Magno Quites Machado Filho
Author Date: 2020-03-26 02:13:31 UTC

MDEV-21984: POWER crc32 acceleration - fix clang's behavior on versions >= 7

Clang 7 changed the behavior of vec_xxpermdi in order to match GCC's
behavior. After this change, code that used to work on Clang 6 stopped
to work on Clang >= 7.

Tested on Clang 6, 7, 8 and 9.

Reference: https://bugs.llvm.org/show_bug.cgi?id=38192

Upstream fix: https://github.com/antonblanchard/crc32-vpmsum/commit/361aaf77a599995e23acd50c9c50d48d30c69241

bb-10.5-midenok 2020-04-09 18:16:29 UTC 2020-04-09
MDEV-22155 ALTER add default history partitions name clash on non-default par...

Author: midenok
Author Date: 2020-04-09 18:16:29 UTC

MDEV-22155 ALTER add default history partitions name clash on non-default partitions

If any of default names clashes with existing names find next large
enough name gap for the requested number of partitions.

bb-5.5-varun 2020-04-08 18:17:03 UTC 2020-04-08
MDEV-22191: Range access is not picked when index_merge_sort_union is turned off

Author: varun
Author Date: 2020-04-08 12:09:27 UTC

MDEV-22191: Range access is not picked when index_merge_sort_union is turned off

When index_merge_sort_union is turned off only ror scans were considered for range
scans, which is wrong.
To fix the problem ensure both ror scans and non ror scans are considered for range
access

bb-10.4-MDEV-22051 2020-04-08 13:42:18 UTC 2020-04-08
MDEV-22051: Protocol::end_statement(): Assertion `0' failed on Galera node up...

Author: mkaruza
Author Date: 2020-03-31 16:43:10 UTC

MDEV-22051: Protocol::end_statement(): Assertion `0' failed on Galera node upon DDL attempt with conflicting lock

If FTWRL is issued, DDL statements should report error back to user before
TOI is started.

bb-10.5-MDEV-22193 2020-04-08 13:15:52 UTC 2020-04-08
MDEV-22193 Avoid un-necessary page initialization during recovery

Author: THIRUNARAYANAN BALATHANDAYUTHAPANI
Author Date: 2020-04-08 13:01:18 UTC

MDEV-22193 Avoid un-necessary page initialization during recovery

- InnoDB is doing un-necessary redo log page initialisation during
recovery and unnecessary traversal of redo log during last phase.
This patch does the optimization of removing unnecessary redo log page
initialisation and detects the memory exhaust earlier.

bb-10.2-MDEV-21681-page-LSN-doesnt-match-cb 2020-04-08 09:02:35 UTC 2020-04-08
Some debug code

Author: Vlad Lesin
Author Date: 2020-04-05 19:20:49 UTC

Some debug code

10.5-MDEV-17812 2020-04-07 18:51:54 UTC 2020-04-07
MDEV-17812 Use MariaDB in error messages instead of MySQL

Author: Rasmus Johansson
Author Date: 2020-04-07 18:51:54 UTC

MDEV-17812 Use MariaDB in error messages instead of MySQL

Changed wording in error messages from MySQL to MariaDB. In
cases where the word server could be used instead it was done.

Tests that have these errors recorded were updated.

10.5-mdev21829 2020-04-05 09:39:24 UTC 2020-04-05
Fixing more test failures

Author: varun
Author Date: 2020-04-05 07:52:05 UTC

Fixing more test failures

bb-10.3-midenok-MDEV-21138 2020-04-04 08:37:20 UTC 2020-04-04
Exclude just added row

Author: midenok
Author Date: 2020-04-04 08:37:20 UTC

Exclude just added row

bb-10.1-anel-PR1265 2020-04-04 04:59:35 UTC 2020-04-04
MDEV-19227 mysql_plugin doesn't run bootstrap from source

Author: Anel Husakovic
Author Date: 2019-04-10 10:35:01 UTC

MDEV-19227 mysql_plugin doesn't run bootstrap from source

bb-10.5-MDEV-17395-replace 2020-04-03 10:16:28 UTC 2020-04-03
add tests for double PS exec and auto_increment

Author: Nikita Malyavin
Author Date: 2020-04-03 10:16:28 UTC

add tests for double PS exec and auto_increment

bb-10.5-oalter-rebase 2020-04-02 11:54:38 UTC 2020-04-02
xyz

Author: Sachin Setiya
Author Date: 2020-04-02 11:54:38 UTC

xyz

bb-10.3-anel-PR1477 2020-04-02 05:31:27 UTC 2020-04-02
MDEV-21984: POWER crc32 acceleration - fix clang's behavior on versions >= 7

Author: Tulio Magno Quites Machado Filho
Author Date: 2020-03-26 02:13:31 UTC

MDEV-21984: POWER crc32 acceleration - fix clang's behavior on versions >= 7

Clang 7 changed the behavior of vec_xxpermdi in order to match GCC's
behavior. After this change, code that used to work on Clang 6 stopped
to work on Clang >= 7.

Tested on Clang 6, 7, 8 and 9.

Reference: https://bugs.llvm.org/show_bug.cgi?id=38192

Upstream fix: https://github.com/antonblanchard/crc32-vpmsum/commit/361aaf77a599995e23acd50c9c50d48d30c69241

PR 1477

10.5-mdev11563 2020-04-01 12:34:46 UTC 2020-04-01
MDEV-22089: Group concat returns incorrect result when using DISTINCT and ORD...

Author: varun
Author Date: 2020-04-01 11:55:57 UTC

MDEV-22089: Group concat returns incorrect result when using DISTINCT and ORDER BY

For ORDER BY to work with distinct, read the values from the UNIQUE tree and
then insert the values into the ORDER BY tree. Then walk the ORDER BY tree
to get the desired ordering.

bb-10.3-robert 2020-04-01 11:02:14 UTC 2020-04-01
Assertion `old_part_id == m_last_part' failed in ha_partition::update_row or ...

Author: Nikita Malyavin
Author Date: 2019-03-04 09:09:30 UTC

Assertion `old_part_id == m_last_part' failed in ha_partition::update_row or `part_id == m_last_part' in ha_partition::delete_row upon UPDATE/DELETE after dropping versioning

PRIMARY KEY change hadn't been treated as partition reorganization in case of partitioning by KEY() (without parameters).

* set `*partition_changed= true` in the described case.
* since add/drop system versioning does not affect alter_info->key_list, it required separate attention

bb-10.5-clustrixdb 2020-03-31 22:49:13 UTC 2020-03-31
Merge pull request #79 from mariadb-corporation/fix_rowbased_update

Author: Michael Erickson
Author Date: 2020-03-31 22:49:13 UTC

Merge pull request #79 from mariadb-corporation/fix_rowbased_update

Remove sql_command check in rnd_init.

10.1-MDEV-20676 2020-03-31 12:18:06 UTC 2020-03-31
MDEV-20676: systemd script not working

Author: Julius Goryavsky
Author Date: 2020-03-31 12:18:06 UTC

MDEV-20676: systemd script not working

When trying to start mariadb via systemctl, WSREP failed
to start mysqld for wsrep recovery, because the binary
"galera-recovery" is neither searching the mysqld in the
same folder as the binary itself nor in the path variable
but instead expects the root to be /usr/local/mysql.

This fix changes the current directory to the desired
directory before starting mysqld.

10.5-MDEV-22023 2020-03-31 08:39:38 UTC 2020-03-31
MDEV-22023 fix manpages to use mariadb* executable names

Author: Rasmus Johansson
Author Date: 2020-03-31 08:39:38 UTC

MDEV-22023 fix manpages to use mariadb* executable names

bb-10.1-anel-removexbcloud 2020-03-30 22:37:57 UTC 2020-03-30
Remove unused file xbcloud.cc

Author: Anel Husakovic
Author Date: 2020-03-30 22:37:53 UTC

Remove unused file xbcloud.cc

Commit ce4c56db0c5806c exclude file from compiling

bb-10.4-MDEV-22021 2020-03-30 13:36:35 UTC 2020-03-30
MDEV-22021: Galera database could get inconsistent with rollback to savepoint

Author: Daniele Sciascia
Author Date: 2020-03-16 14:03:00 UTC

MDEV-22021: Galera database could get inconsistent with rollback to savepoint

When binlog is disabled, WSREP will not behave correctly when
SAVEPOINT ROLLBACK is executed and we will not rollback transaction.

bb-10.2-MDEV-22021 2020-03-30 08:44:51 UTC 2020-03-30
Merge branch 'codership-10.2-MDEV-22021' into bb-10.2-MDEV-22021

Author: Jan Lindström
Author Date: 2020-03-30 08:44:51 UTC

Merge branch 'codership-10.2-MDEV-22021' into bb-10.2-MDEV-22021

bb-10.5-mdev22014 2020-03-29 10:31:52 UTC 2020-03-29
MDEV-22014: Rowid Filtering is not displayed well in the optimizer trace

Author: Sergey Petrunia
Author Date: 2020-03-29 10:31:52 UTC

MDEV-22014: Rowid Filtering is not displayed well in the optimizer trace

- Print the rowid filters that are available for use with each table.
- Make print_best_access_for_table() print which filter it has picked.
- Make best_access_path() print the filter for considered ref accesses.

bb-10.5-monty-opt 2020-03-26 14:07:10 UTC 2020-03-26
More cost fixes:

Author: Monty
Author Date: 2020-03-24 11:34:03 UTC

More cost fixes:

- heap::read_time() and heap::keyread_time() adjusted to not add +1.
  This was to ensure that handler::keyread_time() doesn't give
  higher cost for heap tables than for normal tables. One effect of
  this is that heap and derived tables stored in heap will prefer
  key access as this is now regarded as cheap.
- Changed cost for index read in sql_select.cc to match
  multi_range_read_info_const(). All index cost calculation is now
  done trough one function.
- 'ref' will now use quick_cost for keys if it exists. This is done
  so that for '=' ranges, 'ref' is prefered over 'range'.
- scan_time() now takes avg_io_costs() into account
- get_delayed_table_estimates() uses block_size and avg_io_cost()
- Removed default argument to test_if_order_by_key(); simplifies code

bb-10.2-anel-PR900 2020-03-26 10:00:45 UTC 2020-03-26
PR 900 update for debian

Author: Anel Husakovic
Author Date: 2020-03-26 10:00:45 UTC

PR 900 update for debian

10.5-MDEV-21951 2020-03-24 13:55:07 UTC 2020-03-24
MDEV-21951: mariabackup SST fail if data-directory have lost+found directory

Author: Julius Goryavsky
Author Date: 2020-03-24 13:55:07 UTC

MDEV-21951: mariabackup SST fail if data-directory have lost+found directory

To fix this, it is necessary to add an option to exclude the
database with the name "lost+found" from processing (the database
name will be checked by the check_if_skip_database_by_path() or
by the check_if_skip_database() function, and as a result
"lost+found" will be skipped).

In addition, it is necessary to slightly modify the verification
logic in the check_if_skip_database() function.

bb-10.3-16272 2020-03-24 07:17:03 UTC 2020-03-24
Empty commit 1

Author: Sachin Setiya
Author Date: 2020-03-24 07:17:03 UTC

Empty commit 1

bb-10.5-MDEV-21452 2020-03-23 17:11:43 UTC 2020-03-23
MDEV-21452 Default MUTEXTYPE=sys for improved performance

Author: Marko Mäkelä
Author Date: 2020-03-23 17:11:43 UTC

MDEV-21452 Default MUTEXTYPE=sys for improved performance

On POWER and ARMv8, the native mutex implementation of the standard
library on GNU/Linux seems to perform noticeably better than
the current default MUTEXTYPE=event or the MUTEXTYPE=futex.

On x86, the difference is smaller, and the MUTEXTYPE=event might be
slightly faster than the system mutex, but not by much.

Let us default to MUTEXTYPE=sys, that is, sys_mutex_t
(pthread_mutex_t or CRITICAL_SECTION) wrapped by
OSMutex and OSTrackMutex. Later, we might remove the
other implementations altogether.

bb-10.5-MDEV-21988 2020-03-23 10:58:57 UTC 2020-03-23
Merge branch 'codership-10.5-MDEV-21988' into 10.5

Author: Jan Lindström
Author Date: 2020-03-23 10:58:57 UTC

Merge branch 'codership-10.5-MDEV-21988' into 10.5

bb-10.2-MDEV-21360 2020-03-23 09:57:21 UTC 2020-03-23
MDEV-21360 restore debud_dbug through a session variable instead of '-d,..'

Author: Larysa Sherepa
Author Date: 2020-03-19 17:55:57 UTC

MDEV-21360 restore debud_dbug through a session variable instead of '-d,..'

bb-10.5-serg2 2020-03-21 19:21:58 UTC 2020-03-21
cleanup: remove unused PLUGIN_INIT_SKIP_DYNAMIC_LOADING

Author: Sergei Golubchik
Author Date: 2020-03-21 19:21:58 UTC

cleanup: remove unused PLUGIN_INIT_SKIP_DYNAMIC_LOADING

bb-10.4-MDEV-21675 2020-03-20 13:47:07 UTC 2020-03-20
Merge branch 'codership-10.4-MDEV-21675' into 10.4

Author: Jan Lindström
Author Date: 2020-03-20 13:47:07 UTC

Merge branch 'codership-10.4-MDEV-21675' into 10.4

bb-10.1-vicentiu-pristene 2020-03-20 11:24:06 UTC 2020-03-20
MDEV-21977 main.func_math fails due to undefined behaviour

Author: Alexander Barkov
Author Date: 2020-03-20 11:24:06 UTC

MDEV-21977 main.func_math fails due to undefined behaviour

The problem happened in these line:

uval0= (ulonglong) (val0_negative ? -val0 : val0);
uval1= (ulonglong) (val1_negative ? -val1 : val1);

return check_integer_overflow(val0_negative ? -(longlong) res : res,
                              !val0_negative);

when unary minus was performed on -9223372036854775808.
This behavior is undefined in C/C++.

10.5-MDEV-15053 2020-03-19 15:30:26 UTC 2020-03-19
WIP (crashes/hangs!) MDEV-15053 Reduce buf_pool_t::mutex contention

Author: Marko Mäkelä
Author Date: 2020-03-19 15:30:26 UTC

WIP (crashes/hangs!) MDEV-15053 Reduce buf_pool_t::mutex contention

TODO: Carefully review and document the changed latching rules,
make ASAN happy, and possibly make more use of std::atomic
and make more things private in buf_pool_t to control access.

bb-10.4-MDEV-MDEV-20616 2020-03-19 10:39:26 UTC 2020-03-19
Fix test case name and add debug sync include.

Author: Jan Lindström
Author Date: 2020-03-19 10:39:26 UTC

Fix test case name and add debug sync include.

bb-10.5-pr1471 2020-03-18 20:49:55 UTC 2020-03-18
Travis-CI: Ignore clang/GCC 6 that permanently fails on 10.5 branch

Author: Otto Kekäläinen
Author Date: 2020-03-17 21:52:01 UTC

Travis-CI: Ignore clang/GCC 6 that permanently fails on 10.5 branch

The purpose of a CI system is to validate if a change is acceptable or not.
Thus tests that always fail should be ignored, otherwise the result of the
CI (green/red) is not reliable and actionable.

bb-10.2-hf 2020-03-18 09:55:21 UTC 2020-03-18
MDEV-14057 InnoDB GIS tests fail.

Author: Alexey Botchkov
Author Date: 2020-03-18 09:55:21 UTC

MDEV-14057 InnoDB GIS tests fail.

Tests fixed.
MBR::Within() function fixed.

bb-10.5-monty3 2020-03-17 19:39:04 UTC 2020-03-17
Debug push to find problem with rpl.rpl_skip_replication

Author: Monty
Author Date: 2020-03-17 19:39:04 UTC

Debug push to find problem with rpl.rpl_skip_replication

bb-10.5-monty2 2020-03-17 16:09:49 UTC 2020-03-17
Merge remote-tracking branch 'origin/10.4' into 10.5

Author: Monty
Author Date: 2020-03-17 16:09:49 UTC

Merge remote-tracking branch 'origin/10.4' into 10.5

bb-10.5-MDEV-15053-2 2020-03-17 09:24:59 UTC 2020-03-17
Rename buf_pool->mutex back from buf_pool->LRU_list_mutex

Author: Marko Mäkelä
Author Date: 2020-03-17 09:24:59 UTC

Rename buf_pool->mutex back from buf_pool->LRU_list_mutex

bb-10.2-14057-hf 2020-03-17 08:48:22 UTC 2020-03-17
MDEV-14057 InnoDB GIS tests fail.

Author: Alexey Botchkov
Author Date: 2020-03-17 08:48:22 UTC

MDEV-14057 InnoDB GIS tests fail.

Tests fixed and reenabled.

bb-10.4-monty3 2020-03-17 00:16:49 UTC 2020-03-17
MDEV-21932 A fast plan with ROR index-merge is ignored when

Author: Igor Babaev
Author Date: 2020-03-13 13:55:32 UTC

MDEV-21932 A fast plan with ROR index-merge is ignored when
           'index_merge_sort_union=off'

When index_merge_sort_union is set to 'off' and index_merge_union is set
to 'on' then any evaluated index merge scan must consist only of ROR scans.
The cheapest out of such index merges must be chosen. This index merge
might not be the cheapest index merge.

bb-10.4-monty 2020-03-16 21:10:55 UTC 2020-03-16
Make JT_EQ_REF and JT_REF have equal calculated cost formula

Author: Monty
Author Date: 2020-03-06 12:10:53 UTC

Make JT_EQ_REF and JT_REF have equal calculated cost formula

10.5-mdev21955 2020-03-16 19:43:23 UTC 2020-03-16
MDEV-21955: Alternative way of doing packed-sort keys

Author: Sergey Petrunia
Author Date: 2020-03-16 19:43:23 UTC

MDEV-21955: Alternative way of doing packed-sort keys

Use "Variable-Length Space Padded Encoding" that MyRocks uses.
The value comparison function is memcmp().

A very crude just to evaluate the performance of this.

bb-10.4-elenst 2020-03-15 17:15:11 UTC 2020-03-15
Testing buildbot changes for skipping upgrade on old branches

Author: Elena Stepanova
Author Date: 2020-03-15 17:15:11 UTC

Testing buildbot changes for skipping upgrade on old branches

bb-10.5-mdev_742 2020-03-15 15:04:29 UTC 2020-03-15
MDEV-742: read-only, pure myisam, binlog-*, @@skip_log_bin corner cases

Author: Andrei Elkin
Author Date: 2020-03-08 19:52:30 UTC

MDEV-742: read-only, pure myisam, binlog-*, @@skip_log_bin corner cases

(Pushed to 10.5)
Are addressed along the following policies.
Prepared read-only, or on non-transactional engines, or
binlog-* filter in binlog, or skipped to binlog XA:s remains in the xid cache after disconnect.
But their consequent completion with Commit or Rollback differs.

1. The read-only at reconnect marks XID to fail for future
completion with ER_XA_RBROLLBACK.

2. `binlog-*` filtered XA when it changes engine data is regarded
as loggable even when nothing got cached for binlog.
An empty XA-prepare group is recorded. Consequent Commit-or-Rollback
succeeds in the Engine(s) as well as recorded into binlog.

3. The same applies to the non-transactional engine XA.

4. @@skip_log_bin=OFF does not record anything at XA-prepare (obviously),
but the completion event is recorded into binlog to admit
inconsistency with slave.

The following actions are taken by the patch.

At XA-prepare:
  when empty binlog cache - don't do anything to binlog if RO,
  otherwise write empty XA_prepare (assert(binlog-filter case)).
At Disconnect:
  when Prepared && RO (=> no binlogging was done)
    set Xid_cache_element::error := ER_XA_RBROLLBACK
    *keep* XID in the cache, and rollback the transaction.
At XA-"complete":
   Discover the error, if any don't binlog the "complete", return the error to the user.

RO patch review notes.

10.5-wlad 2020-03-14 21:48:10 UTC 2020-03-14
dynamic nr of Innodb io threads

Author: Vladislav Vaintroub
Author Date: 2020-03-14 19:52:17 UTC

dynamic nr of Innodb io threads

bb-10.2-MDEV-21910 2020-03-13 11:40:00 UTC 2020-03-13
MDEV-21910 : KIlling thread on Galera could cause mutex deadlock

Author: Jan Lindström
Author Date: 2020-03-12 13:34:50 UTC

MDEV-21910 : KIlling thread on Galera could cause mutex deadlock

Following issues here:

Whenever Galera BF (brute force) transaction decides to abort conflicting
transaction it will kill that thread using thd::awake()

User KILL [QUERY|CONNECTION] ... for a thread it will also call thd::awake()

Whenever one of these actions is executed we will hold number of InnoDB
internal mutexes and thd mutexes. Sometimes these mutexes are taken in
different order causing mutex deadlock.

Lets consider a example starting from Galera BF transaction deciding to abort
conflicting transaction (let's call this thread1):

thread1:
lock_rec_other_has_conflicting
  here we hold both lock_sys mutex and trx mutex for conflicting lock transaction.
wsrep_innobase_kill_one_trx
  For victim we call wsrep_thd_awake

Next thread2 we assume user to execute KILL QUERY to some other executing
query (note it can't be BF query).

thread2:
sql_kill()
kill_one_thread
find_thread_by_id
  takes LOCK_thd_kill
thd->awake_no_mutex()

thread1:
thd->awake(KILL_QUERY)
  Tries to have LOCK_thd_kill but it is hold by thread2 so we wait (note that
  we still hold lock_sys mutex and trx mutex).

thread2:
ha_kill_query()
kill_handlerton
innobase_kill_query
lock_trx_handle_wait
  lock_mutex_enter() must wait as thread1 is holding it

Thus thread1 lock_sys, trx_mutex waits -> thread2 LOCK_thd_kill waits lock_sys -> thread1
==> thread1 waits -> thread2 waits -> thread1 ==> mutex deadlock.

In this patch we will fix Galera BF and user kill cases so that we enqueue
victim thread to a list while we hold InnoDB mutexes and we then release them.
A new background thread will pick victim thread from this new list and uses
thd::awake() with no InnoDB mutexes. Idea is similar to replication background
kill. This fix enforces that we take LOCK_thd_data -> lock sys mutex -> trx mutex
always in this order.

wsrep_mysqld.cc
 Here we introduce a list where victim threads are stored,
 condition variable to be used to wake up background thread
 and mutex to protect list.

wsrep_thd.cc
 Create a new background thread to handle victim thread
 abort. We may take wsrep_thd_LOCK mutex here but not any
 InnoDB mutexes.

wsrep_innobase_kill_one_trx
 Remove all the wsrep code that was moved to wsrep_thd.cc
 We just enqueue required information to background kill
 list and cancel victim trx lock wait if there is such.
 Here we have InnoDB lock sys mutex and trx mutex so here
 we can't take wsrep_thd_LOCK mutex.

wsrep_abort_transaction
 Cleanup only.

10.2-MDEV-21910 2020-03-13 11:40:00 UTC 2020-03-13
MDEV-21910 : KIlling thread on Galera could cause mutex deadlock

Author: Jan Lindström
Author Date: 2020-03-12 13:34:50 UTC

MDEV-21910 : KIlling thread on Galera could cause mutex deadlock

Following issues here:

Whenever Galera BF (brute force) transaction decides to abort conflicting
transaction it will kill that thread using thd::awake()

User KILL [QUERY|CONNECTION] ... for a thread it will also call thd::awake()

Whenever one of these actions is executed we will hold number of InnoDB
internal mutexes and thd mutexes. Sometimes these mutexes are taken in
different order causing mutex deadlock.

Lets consider a example starting from Galera BF transaction deciding to abort
conflicting transaction (let's call this thread1):

thread1:
lock_rec_other_has_conflicting
  here we hold both lock_sys mutex and trx mutex for conflicting lock transaction.
wsrep_innobase_kill_one_trx
  For victim we call wsrep_thd_awake

Next thread2 we assume user to execute KILL QUERY to some other executing
query (note it can't be BF query).

thread2:
sql_kill()
kill_one_thread
find_thread_by_id
  takes LOCK_thd_kill
thd->awake_no_mutex()

thread1:
thd->awake(KILL_QUERY)
  Tries to have LOCK_thd_kill but it is hold by thread2 so we wait (note that
  we still hold lock_sys mutex and trx mutex).

thread2:
ha_kill_query()
kill_handlerton
innobase_kill_query
lock_trx_handle_wait
  lock_mutex_enter() must wait as thread1 is holding it

Thus thread1 lock_sys, trx_mutex waits -> thread2 LOCK_thd_kill waits lock_sys -> thread1
==> thread1 waits -> thread2 waits -> thread1 ==> mutex deadlock.

In this patch we will fix Galera BF and user kill cases so that we enqueue
victim thread to a list while we hold InnoDB mutexes and we then release them.
A new background thread will pick victim thread from this new list and uses
thd::awake() with no InnoDB mutexes. Idea is similar to replication background
kill. This fix enforces that we take LOCK_thd_data -> lock sys mutex -> trx mutex
always in this order.

wsrep_mysqld.cc
 Here we introduce a list where victim threads are stored,
 condition variable to be used to wake up background thread
 and mutex to protect list.

wsrep_thd.cc
 Create a new background thread to handle victim thread
 abort. We may take wsrep_thd_LOCK mutex here but not any
 InnoDB mutexes.

wsrep_innobase_kill_one_trx
 Remove all the wsrep code that was moved to wsrep_thd.cc
 We just enqueue required information to background kill
 list and cancel victim trx lock wait if there is such.
 Here we have InnoDB lock sys mutex and trx mutex so here
 we can't take wsrep_thd_LOCK mutex.

wsrep_abort_transaction
 Cleanup only.

bb-10.5-thiru 2020-03-12 17:55:41 UTC 2020-03-12
- Fixing the fts failure hang during shutdown. Basically,

Author: THIRUNARAYANAN BALATHANDAYUTHAPANI
Author Date: 2020-03-12 17:54:47 UTC

- Fixing the fts failure hang during shutdown. Basically,
fts_optimize_callback() should free the fts_optimize_wq variable
and make it as null. It allows the subsequent fts_optimize_callback()
to return earlier.

bb-10.1-kevgs 2020-03-11 15:02:12 UTC 2020-03-11
MDEV-21918 improve page_zip_verify_checksum()

Author: Eugene
Author Date: 2020-03-11 13:40:34 UTC

MDEV-21918 improve page_zip_verify_checksum()

actually, page_zip_verify_checksum() generally allows all-zeroes
checksums because our CRC32 checksum is something like
crc_1 ^ crc_2 ^ crc_3

Also, all zeroes page is considered correct.

As a side effect fix nasty reinterpret_cast<> UB

Also, since c0f47a4a5842 innodb_checksum_algorithm=full_crc32
exists which computes CRC32 in one go (without bitwise arithmetic)

10.5-mdev6915 2020-03-11 11:23:35 UTC 2020-03-11
Pack addon fields always if we can save more than 8 bytes

Author: varun
Author Date: 2020-03-11 11:23:35 UTC

Pack addon fields always if we can save more than 8 bytes

bb-10.5-MDEV-13362 2020-03-11 11:07:06 UTC 2020-03-11
Merge branch '10.5' of https://github.com/MariaDB/server into bb-10.5-MDEV-13362

Author: Julius Goryavsky
Author Date: 2020-03-11 11:07:06 UTC

Merge branch '10.5' of https://github.com/MariaDB/server into bb-10.5-MDEV-13362

10.5-MDEV-13362 2020-03-11 10:10:30 UTC 2020-03-11
MDEV-13362: implement --require_secure_transport option

Author: Julius Goryavsky
Author Date: 2020-03-02 22:46:07 UTC

MDEV-13362: implement --require_secure_transport option

Currently, if a user wants to require TLS for every connection made
over the network, then every user account on the system needs to be
created with "REQUIRE SSL" or one of the other TLS options.

Implementing a require_secure_transport system varuable (which,
in particular, can be set using the --require_secure_transport=ON
command line option) in the MariaDB Server would make it a lot
easier to require TLS (or other secure transport) system-wide.

This patch implements this new system variable, adds the ability
to set it with SQL statements, from the command line and from the
configuration file, and also contains improvements for mtr that allow
the user to establish non-secure TCP/IP connections (for example,
to verify the operation of the new option).

bb-10.5-oalter 2020-03-10 15:47:34 UTC 2020-03-10
States reduced

Author: Sachin Setiya
Author Date: 2020-03-10 15:47:34 UTC

States reduced

bb-10.5-MDEV-16978-without-overlaps 2020-03-10 14:46:24 UTC 2020-03-10
support NULL fields in key

Author: Nikita Malyavin
Author Date: 2020-03-10 14:46:24 UTC

support NULL fields in key

bb-10.5-xpand 2020-03-10 08:23:43 UTC 2020-03-10
Merge XPand Storage Engine (rebased)

Author: Sergey Petrunia
Author Date: 2020-03-10 08:23:43 UTC

Merge XPand Storage Engine (rebased)

bb-10.5-wlad-15053 2020-03-09 19:44:56 UTC 2020-03-09
Fix comments in buf_read_page

Author: Vladislav Vaintroub
Author Date: 2020-03-09 19:44:56 UTC

Fix comments in buf_read_page

bb-10.5-pre_mdev-742 2020-03-09 15:33:07 UTC 2020-03-09
MDEV-21659 XA rollback foreign_xid is allowed inside active XA

Author: Andrei Elkin
Author Date: 2020-03-02 15:12:35 UTC

MDEV-21659 XA rollback foreign_xid is allowed inside active XA
MDEV-21854 xa commit `xid` one phase for already prepared transaction must always error out

Added state and one-phase option checks to XA "external" commit/rollback
branches. While the XA standard does not prohibit it,
Commit and Rollback of an XA external to the current ongoing transaction
is not allowed; after all the current transaction may rollback
to not being able to revert that decision.

bb-10.2-MDEV-21758 2020-03-09 07:00:14 UTC 2020-03-09
MDEV-21758 : Events switched randomly to SLAVESIDE_DISABLED

Author: Jan Lindström
Author Date: 2020-03-09 07:00:14 UTC

MDEV-21758 : Events switched randomly to SLAVESIDE_DISABLED

Change events only on Galera environment where idea is that
event is enabled only on one node of the cluster and nodes
are identified by server_id.

10.5-mdev21784-reg1-vfuncs 2020-03-08 21:29:48 UTC 2020-03-08
MDEV-21784: Performance testing for packed sort keys

Author: Sergey Petrunia
Author Date: 2020-03-08 21:29:48 UTC

MDEV-21784: Performance testing for packed sort keys

A piece of cumulative patch for

  MDEV-21580 Allow packed sort keys in sort buffer

which just adds some virtual functions (without any calls to them)

101200 of 615 results
This repository contains Public information 
Everyone can see this information.

Subscribers