View Bazaar branches
Get this repository:
git clone https://git.launchpad.net/maria

Branches

Name Last Modified Last Commit
bb-5.5-serg 2018-01-20 16:59:37 UTC 3 hours ago
Free memory in unit tests. Makes ASAN happier.

Author: Sergei Golubchik
Author Date: 2018-01-20 16:59:37 UTC

Free memory in unit tests. Makes ASAN happier.

bb-10.0-pentve 2018-01-20 13:47:01 UTC 6 hours ago
MDEV-14185 -- CREATE TEMPORARY TABLE AS SELECT causes error 1290 with read_on...

Author: Vesa Pentti
Author Date: 2018-01-20 13:46:47 UTC

MDEV-14185 -- CREATE TEMPORARY TABLE AS SELECT causes error 1290 with read_only and InnoDB

 * Did affect only transactional engines like InnoDB
 * Note: During table creation handler's 'table_share' is NULL
 * Now the transaction isn't marked rw for a temporary table when it's created

bb-10.3-MDEV14638 2018-01-20 12:10:38 UTC 8 hours ago
Get rid of trx->read_view pointer juggling

Author: Sergey Vojtovich
Author Date: 2018-01-19 19:03:18 UTC

Get rid of trx->read_view pointer juggling

trx->read_view|= 1 was done in a silly attempt to fix race condition
where trx->read_view was closed without trx_sys.mutex lock by read-only
trasnactions.

This just made the problem less likely to happen. In fact there was race
condition in const version of trx_get_read_view(): pointer may change to
garbage any moment after MVCC::is_view_active(trx->read_view) check and
before this function returns.

This patch doesn't fix this race condition, but rather makes it's
consequences less destructive.

10.3 2018-01-20 12:10:38 UTC 8 hours ago
Get rid of trx->read_view pointer juggling

Author: Sergey Vojtovich
Author Date: 2018-01-19 19:03:18 UTC

Get rid of trx->read_view pointer juggling

trx->read_view|= 1 was done in a silly attempt to fix race condition
where trx->read_view was closed without trx_sys.mutex lock by read-only
trasnactions.

This just made the problem less likely to happen. In fact there was race
condition in const version of trx_get_read_view(): pointer may change to
garbage any moment after MVCC::is_view_active(trx->read_view) check and
before this function returns.

This patch doesn't fix this race condition, but rather makes it's
consequences less destructive.

bb-10.3-monty 2018-01-19 18:22:59 UTC 2018-01-19
Added some checking that LEX_CSTRING is \0 terminated

Author: Monty
Author Date: 2018-01-19 17:56:34 UTC

Added some checking that LEX_CSTRING is \0 terminated

- When adding LEX_CSTRING to String, we are now checking that
  string is \0 terminated (as normally LEX_CSTRING should be
  usable for printf(). In the cases when one wants to avoid the
  checking one can use String->append(ptr, length) instead of just
  String->append(LEX_CSTRING*)

5.5-galera 2018-01-19 18:08:03 UTC 2018-01-19
Set wsrep_rli to NULL after deleting it

Author: Vasil Dimov
Author Date: 2017-10-24 13:48:08 UTC

Set wsrep_rli to NULL after deleting it

bb-10.1-serg 2018-01-19 17:46:55 UTC 2018-01-19
MDEV-12301: galera_recovery use @sbindir@ macro for mysqld

Author: Michal Schorm
Author Date: 2018-01-19 09:55:34 UTC

MDEV-12301: galera_recovery use @sbindir@ macro for mysqld

5.5 2018-01-19 16:05:24 UTC 2018-01-19
Add dummy defintion for Dl_info in case we're missing dladdr

Author: Vicențiu Ciorbaru
Author Date: 2018-01-19 16:04:51 UTC

Add dummy defintion for Dl_info in case we're missing dladdr

bb-10.2-marko 2018-01-19 16:03:44 UTC 2018-01-19
MDEV-14941 Timeouts on persistent statistics tables after MDEV-14511

Author: Marko Mäkelä
Author Date: 2018-01-19 15:41:57 UTC

MDEV-14941 Timeouts on persistent statistics tables after MDEV-14511

MDEV-14511 tries to avoid some consistency problems related to InnoDB
persistent statistics. The persistent statistics are being written by
an InnoDB internal SQL interpreter that requires the InnoDB
data dictionary cache to be locked.

Before MDEV-14511, the statistics were written during DDL in separate
transactions, which could unnecessarily reduce performance (each commit
would require a redo log flush) and break atomicity, because the
statistics would be updated separately from the dictionary transaction.

However, because it is unacceptable to hold the InnoDB data dictionary
cache locked while suspending the execution for waiting for a
transactional lock (in the mysql.innodb_index_stats or
mysql.innodb_table_stats tables) to be released, any lock conflict
was immediately reported as "lock wait timeout".

MySQL 5.7.11 (and MariaDB 10.2.2) will purposely drop the statistics
when adding or dropping virtual columns in ALTER TABLE...ALGORITHM=INPLACE.
It turns out that we can do the same with ALTER TABLE...ALGORITHM=COPY
and with table-rebuilding and DROP INDEX operations performed by
ALGORITHM=INPLACE. The statistics would be recalculated when the table
is next opened.

With this fix, it is still possible to get statistics-related error
messages on ALTER TABLE operations on partitioned tables, such as
ALTER TABLE t1 PARTITION BY HASH(pk). In my test, this was due to
a locking conflict between dict_stats_thread executing dict_stats_update()
and the ALTER TABLE renaming one of the partitions.

DB_TABLE_IN_FK_CHECK, HA_ERR_TABLE_IN_FK_CHECK: Remove. A RENAME TABLE
operation will no longer conflict with FOREIGN KEY checks, because
it will acquire an exclusive lock on the table.

dict_stats_snapshot_create(), dict_stats_snapshot_free(): Remove.
The table object cannot disappear, because we will hold a table lock.

dict_stats_update_persistent(): Acquire a table IS lock to prevent
a conflict on statistics updates in RENAME TABLE.

dict_stats_save(): Acquire a table IS lock to prevent
a conflict on statistics updates in RENAME TABLE. (Empty statistics
are written without invoking dict_stats_update_persistent().)

dict_stats_drop_index(): Acquire dict_sys->mutex for a shorter period,
and let the caller report a more compact error.

dict_stats_drop_table(): Let the caller report a more compact error.

dict_stats_rename_table(): Remove some retrying logic. If a timeout
occurs (which should be rare, because we will now hold an exclusive
lock on the table), there is no point sleeping and retrying.

innobase_rename_table(): Do not lock the data dictionary, and do
not update the statistics. That is now done in
row_rename_table_for_mysql().

drop_stats(): Drop persistent statistics during certain
ALTER TABLE...ALGORITHM=INPLACE operations.

alter_stats_rebuild(): Remove.

row_mysql_lock_table(): Allow LOCK_IS to be acquired.

lock_table_enqueue_waiting(): Relax the condition about no lock
waits during a dictionary operation.

bb-10.2-MDEV-13103 2018-01-19 12:12:18 UTC 2018-01-19
Can't run on embedded as uses restart.

Author: Jan Lindström
Author Date: 2018-01-19 12:12:18 UTC

Can't run on embedded as uses restart.

10.2 2018-01-18 23:56:28 UTC 2018-01-18
Fixed mdev-14969 Non-recursive Common Table Expressions used in view

Author: Igor Babaev
Author Date: 2018-01-18 23:56:28 UTC

Fixed mdev-14969 Non-recursive Common Table Expressions used in view
caused an error

The function subselect_single_select_engine::print() did not print
the WITH clause attached to a subselect with single select engine.
As a result views using suqueries with attached WITH clauses lost
these clauses when saved in frm files.

bb-5.5-varun 2018-01-18 21:54:15 UTC 2018-01-18
MDEV-14241: Server crash in key_copy / get_matching_chain_by_join_key or valg...

Author: varun
Author Date: 2018-01-18 21:54:15 UTC

MDEV-14241: Server crash in key_copy / get_matching_chain_by_join_key or valgrind warnings

In this case we were using the optimization derived_with_keys but we could not create a key because
the length of the key was greater than the max allowed(MI_MAX_KEY_LENGTH). To do the join we needed
to create a hash join key instead, but in the explain output it showed that we were still referring
to derived keys which were created but not used.

bb-10.2-monty 2018-01-18 13:20:30 UTC 2018-01-18
Fixed performance problem with Aria in find_head()

Author: Monty
Author Date: 2018-01-18 00:15:00 UTC

Fixed performance problem with Aria in find_head()

For some simple benchmarks, a majority of time was
spend in find_head() which tries to find the best
place to put the record.

The result of this patch is a 2x or more speedup for
inserts without keys for format PAGE. All changes
are only related to how rows are stored

The following changes where done:
- For rows with a small row length that fits into
  a page (818 bytes with 8192 pages), stop as soon as we
  hit a match.
- Added markers full_head_size and full_tail_size that tells
  us where to start searching on the bitmap page
- Ensure that page->used_size is correctly updated when
  bitmap grows. This allows us to stop searching at used_size
- Added code to check that the bitmap variables are correct.
- Fixed a wrong test where we set "first_bitmap_with_space".
  This shouldn't have caused any notable problems.

bb-10.1-MDEV-13103 2018-01-18 11:53:12 UTC 2018-01-18
Doulbewrite test for page compressed tables.

Author: Jan Lindström
Author Date: 2018-01-18 11:53:12 UTC

Doulbewrite test for page compressed tables.

10.1 Version

10.0 2018-01-18 07:29:49 UTC 2018-01-18
Make row_mysql_table_id_reassign() static

Author: Marko Mäkelä
Author Date: 2018-01-18 07:29:49 UTC

Make row_mysql_table_id_reassign() static

bb-10.2-ext 2018-01-17 14:22:27 UTC 2018-01-17
Merge 10.2 into bb-10.2-ext

Author: Marko Mäkelä
Author Date: 2018-01-17 14:22:27 UTC

Merge 10.2 into bb-10.2-ext

bb-10.3-serg 2018-01-17 12:32:35 UTC 2018-01-17
MDEV-13946 Server RPMs have dependency on "which"

Author: Sergei Golubchik
Author Date: 2017-10-10 20:47:18 UTC

MDEV-13946 Server RPMs have dependency on "which"

cleanup. use "command -v" instead of "which"
simplify some checks.

bb-10.3-release 2018-01-16 23:45:02 UTC 2018-01-16
Merge branch 'github/10.3' into bb-10.3-temporal

Author: Sergei Golubchik
Author Date: 2018-01-16 23:45:02 UTC

Merge branch 'github/10.3' into bb-10.3-temporal

bb-5.5-vicentiu 2018-01-16 20:57:52 UTC 2018-01-16
MDEV-14229: Stack trace is not resolved for shared objects

Author: Vicențiu Ciorbaru
Author Date: 2018-01-16 20:57:52 UTC

MDEV-14229: Stack trace is not resolved for shared objects

Resolving a stacktrace including functions in dynamic libraries requires
us to look inside the libraries for the symbols. Addr2line needs to be
started with the correct binary for each address on the stack. To do this,
figure out which library it is using dladdr, then if the addr2line
binary was started with a different binary, fork it again with the
correct one.

We only have one addr2line process running at any point during the
stacktrace resolving step. The maximum number of forks for addr2line should
generally be around 6.

One for server stacktrace code, one for plugin code, one when going back
into server code, one for pthread library, one for libc, one for the
_start function in the server. More can come up if plugin calls server
function which goes back to a plugin, etc.

bb-5.5-MDEV-14786 2018-01-15 19:52:58 UTC 2018-01-15
MDEV-14786: Server crashes in Item_cond::transform on 2nd execution of SP que...

Author: Oleksandr Byelkin
Author Date: 2018-01-15 13:50:35 UTC

MDEV-14786: Server crashes in Item_cond::transform on 2nd execution of SP querying from a view

Do not touch merged derived (it is irreversible)

bb-10.2-wlad 2018-01-15 18:59:27 UTC 2018-01-15
Windows : fix compile warnings C4267, on 32bit first

Author: Vladislav Vaintroub
Author Date: 2018-01-15 18:59:27 UTC

Windows : fix compile warnings C4267, on 32bit first

10.1 2018-01-15 14:19:46 UTC 2018-01-15
Fix a test that always failed on --embedded

Author: Marko Mäkelä
Author Date: 2018-01-15 14:19:46 UTC

Fix a test that always failed on --embedded

bb-5.5-svoj 2018-01-15 12:19:53 UTC 2018-01-15
debian: insecure root password is only if plugin is empty

Author: Daniel Black
Author Date: 2017-12-29 00:25:42 UTC

debian: insecure root password is only if plugin is empty

bb-10.3-mariarocks 2018-01-13 22:22:54 UTC 2018-01-13
Merge remote-tracking branch 'origin/10.2' into bb-10.3-mariarocks

Author: Sergey Petrunia
Author Date: 2018-01-13 22:22:54 UTC

Merge remote-tracking branch 'origin/10.2' into bb-10.3-mariarocks

bb-10.3-temporal-serg 2018-01-13 01:01:36 UTC 2018-01-13
cleanup: remove include/rpl_events.inc

Author: Sergei Golubchik
Author Date: 2018-01-12 21:21:38 UTC

cleanup: remove include/rpl_events.inc

introduces 10 years ago, still included only once.
no need to complicate debugging by unnecessary includes.

bb-10.2-mariarocks 2018-01-12 22:26:06 UTC 2018-01-12
rocksdb.information_schema testcase is not stable

Author: Sergey Petrunia
Author Date: 2018-01-12 22:26:06 UTC

rocksdb.information_schema testcase is not stable

bb-10.3-temporal 2018-01-12 20:20:24 UTC 2018-01-12
SQL: uninitialized read [#387]

Author: Eugene
Author Date: 2018-01-12 19:45:35 UTC

SQL: uninitialized read [#387]

rpl.rpl_events sometimes fails in release mode after be81b00c843b4a3335a630afa7200fda6eab8e89

This could be prevented with MSAN

bb-5.5-pentve 2018-01-12 10:15:50 UTC 2018-01-12
MDEV-14185 -- CREATE TEMPORARY TABLE AS SELECT causes error 1290 with read_on...

Author: Vesa Pentti
Author Date: 2018-01-11 15:18:29 UTC

MDEV-14185 -- CREATE TEMPORARY TABLE AS SELECT causes error 1290 with read_only and InnoDB

     * Did affect only transactional engines like InnoDB
     * Note: During table creation handler's 'table_share' is NULL
     * Now the transaction isn't marked rw for a temporary table when it's created

bb-10.3-vicentiu-travis2 2018-01-12 01:57:02 UTC 2018-01-12
To avoid travis network timeouts, use travis's retry script

Author: Vicențiu Ciorbaru
Author Date: 2018-01-12 01:57:02 UTC

To avoid travis network timeouts, use travis's retry script

bb-10.2-compatibility 2018-01-11 21:58:53 UTC 2018-01-11
MDEV-11952 Oracle-style packages: stage#5

Author: Alexander Barkov
Author Date: 2017-08-18 19:36:42 UTC

MDEV-11952 Oracle-style packages: stage#5

- CREATE PACKAGE [BODY] statements are now
  entirely written to mysql.proc with type='PACKAGE' and type='PACKAGE BODY'.
- CREATE PACKAGE BODY now supports IF NOT EXISTS
- DROP PACKAGE BODY now supports IF EXISTS
- CREATE OR REPLACE PACKAGE [BODY] is now supported
- CREATE PACKAGE [BODY] now support the DEFINER clause:

    CREATE DEFINER user@host PACKAGE pkg ... END;
    CREATE DEFINER user@host PACKAGE BODY pkg ... END;

- CREATE PACKAGE [BODY] now supports SQL SECURITY and COMMENT clauses, e.g.:

    CREATE PACKAGE p1 SQL SECURITY INVOKER COMMENT "comment" AS ... END;

- Package routines are now created from the package CREATE PACKAGE BODY
  statement and don't produce individual records in mysql.proc.

- CREATE PACKAGE BODY now supports package-wide variables.
  Package variables can be read and set inside package routines.
  Package variables are stored in a separate sp_rcontext,
  which is cached in THD on the first packate routine call.

- CREATE PACKAGE BODY now supports the initialization section.

- All public routines (i.e. declared in CREATE PACKAGE)
  must have implementations in CREATE PACKAGE BODY

- Only public package routines are available outside of the package

- {CREATE|DROP} PACKAGE [BODY] now respects CREATE ROUTINE and ALTER ROUTINE
  privileges

- "GRANT EXECUTE ON PACKAGE BODY pkg" is now supported

- SHOW CREATE PACKAGE [BODY] is now supported

- SHOW PACKAGE [BODY] STATUS is now supported

- CREATE and DROP for PACKAGE [BODY] now works for non-current databases

- mysqldump now supports packages

- "SHOW {PROCEDURE|FUNCTION) CODE pkg.routine" now works for package routines

- "SHOW PACKAGE BODY CODE pkg" now works (the package initialization section)

- A new package body level MDL was added

- Recursive calls for package procedures are now possible

- Routine forward declarations in CREATE PACKATE BODY are now supported.

- Package body variables now work as SP OUT parameters

- Package body variables now work as SELECT INTO targets

- Package body variables now support ROW, %ROWTYPE, %TYPE

10.3-MDEV-11953 2018-01-09 20:31:00 UTC 2018-01-09
cccc

Author: Oleksandr Byelkin
Author Date: 2018-01-09 20:31:00 UTC

cccc

bb-10.3-vicentiu-dtoa 2018-01-09 07:05:48 UTC 2018-01-09
Workaround for dtoa.c

Author: Vicențiu Ciorbaru
Author Date: 2018-01-09 07:05:48 UTC

Workaround for dtoa.c

There is no obvious reason why multiplying by 1.0 helps solve a
precision problem on gcc-7 or clang-5, but it does work. Casting to
ulong however makes the problem come up again. Windows warns about loss
of precision, so to quiet warnings until an appropriate fix is
implemented, ifdef 2 versions of the code.

bb-10.3-vicentiu-no-dtoa 2018-01-08 23:22:17 UTC 2018-01-08
Fixed mdev-14880: Assertion `inj_cond_list.elements' failed

Author: Igor Babaev
Author Date: 2018-01-08 23:21:52 UTC

Fixed mdev-14880: Assertion `inj_cond_list.elements' failed
in JOIN::inject_best_splitting_cond

The value of SplM_opt_info::last_plan should be set to NULL
before any search for a splitting plan for a splittable
materialized table.

bb-10.2-pentve 2018-01-08 16:00:08 UTC 2018-01-08
MDEV-14185 -- CREATE TEMPORARY TABLE AS SELECT causes error 1290 with read_on...

Author: Vesa Pentti
Author Date: 2018-01-07 19:14:27 UTC

MDEV-14185 -- CREATE TEMPORARY TABLE AS SELECT causes error 1290 with read_only and InnoDB

 * Did affect only transactional engines like InnoDB
 * Note: During table creation handler's 'table_share' is NULL
 * Now the transaction isn't marked rw for a temporary table when it's created

bb-10.1-MDEV-14776 2018-01-08 10:53:35 UTC 2018-01-08
MDEV-14776: InnoDB Monitor output generated by specific error is flooding err...

Author: Jan Lindström
Author Date: 2018-01-08 10:53:35 UTC

MDEV-14776: InnoDB Monitor output generated by specific error is flooding error logs

innodb/buf_LRU_get_free_block
 Add debug instrumentation to produce error message about
 no free pages. Print error message only once and do not
 enable innodb monitor if it is not enabled.

xtradb/buf_LRU_get_free_block
 Add debug instrumentation to produce error message about
 no free pages. Print error message only once and do not
 enable innodb monitor if it is not enabled. Remove code
 that does not seem to be used.

innodb-lru-force-no-free-page.test
 New test case to force produce desired error message.

bb-10.1-pentve 2018-01-07 19:14:27 UTC 2018-01-07
MDEV-14185 -- CREATE TEMPORARY TABLE AS SELECT causes error 1290 with read_on...

Author: Vesa Pentti
Author Date: 2018-01-07 19:14:27 UTC

MDEV-14185 -- CREATE TEMPORARY TABLE AS SELECT causes error 1290 with read_only and InnoDB

 * Did affect only transactional engines like InnoDB
 * Note: During table creation handler's 'table_share' is NULL
 * Now the transaction isn't marked rw for a temporary table when it's created

bb-10.2-andrei-ext 2018-01-04 00:11:01 UTC 2018-01-04
The slave io thread does not conduct integrity check for row-based

Author: Andrei Elkin
Author Date: 2018-01-04 00:11:01 UTC

The slave io thread does not conduct integrity check for row-based
events. Specifically it tolerates missed STMT_END flag marked terminal
event that conclude a sequence of "elementary" "block" Rows-events.
Failure to react on a potentially missed event can confuse the applier thread
in various ways.

The slave io is made in this patch to track the STMT_END status.
Whenever at a first event following a sequence of Rows events the IO thread
finds out that a preceding Rows event did not actually had the flag, an
explicit error is issued.

Replication can be resumed as a provided test demonstrates.

Note that currently the row-based group integrity check is limited
to the version 1 rows event which are generated by Mariadb masters.

bb-10.2-release 2018-01-03 09:56:24 UTC 2018-01-03
Merge 10.1 into 10.2, with some MDEV-14799 fixups

Author: Marko Mäkelä
Author Date: 2018-01-03 09:46:31 UTC

Merge 10.1 into 10.2, with some MDEV-14799 fixups

trx_undo_page_report_modify(): For SPATIAL INDEX, keep logging
updated off-page columns twice, so that
the minimum bounding rectangle (MBR) will be logged.
Avoiding the redundant logging would require larger changes
to the undo log format.

row_build_index_entry_low(): Handle SPATIAL_UNKNOWN more robustly,
by refusing to purge the record from the spatial index.
We can get this code when processing old undo log from 10.2.10 or
10.2.11 (the releases affected by MDEV-14799, which was a regression
from MDEV-14051).

bb-10.1-release 2018-01-03 07:31:56 UTC 2018-01-03
Wake up buildbot

Author: Marko Mäkelä
Author Date: 2018-01-03 07:31:56 UTC

Wake up buildbot

bb-10.0-release 2018-01-03 07:31:25 UTC 2018-01-03
Wake up buildbot

Author: Marko Mäkelä
Author Date: 2018-01-03 07:31:25 UTC

Wake up buildbot

bb-10.2-varun 2017-12-31 14:18:39 UTC 2017-12-31
new commit

Author: varun
Author Date: 2017-12-31 14:18:39 UTC

new commit

bb-10.3-igor 2017-12-31 00:19:17 UTC 2017-12-31
Merge branch '10.3' into bb-10.3-igor

Author: Igor Babaev
Author Date: 2017-12-31 00:19:17 UTC

Merge branch '10.3' into bb-10.3-igor

bb-10.3-vicentiu-travis 2017-12-30 15:18:24 UTC 2017-12-30
Tentative fix for travis

Author: Vicențiu Ciorbaru
Author Date: 2017-12-30 15:18:24 UTC

Tentative fix for travis

This undoes a lock-unlock for LOCK_thread_count.

bb-10.2-vicentiu 2017-12-28 18:04:23 UTC 2017-12-28
MDEV-13683: crash in Item_window_func::update_used_tables

Author: Vicențiu Ciorbaru
Author Date: 2017-12-28 17:29:40 UTC

MDEV-13683: crash in Item_window_func::update_used_tables

Window definitions are resolved during fix fields. Updating used tables
for window functions must be done after all window functions have had a
chance to be resolved.

There was an additional problem with the implementation: expressions that
contained window functions never updated the expression's used tables.
To fix both these issues, make sure to call "update_used_tables" on all
items that contain window functions after we have passed through all
items.

bb-10.3-hidden 2017-12-28 12:39:28 UTC 2017-12-28
MDEV-14785 SYSTEM_INVISIBLE behavior not Consistent

Author: Sachin Setiya
Author Date: 2017-12-28 12:39:28 UTC

MDEV-14785 SYSTEM_INVISIBLE behavior not Consistent

//TODO patch commit message

bb-10.1-10715 2017-12-24 23:39:49 UTC 2017-12-24
MDEV-10715 Galera: Replicate MariaDB GTID to other nodes in the cluster

Author: sachin
Author Date: 2017-12-24 23:39:49 UTC

MDEV-10715 Galera: Replicate MariaDB GTID to other nodes in the cluster

Problem:- Gtid are not transferred in Galera Cluster.

Solution:- We need to transfer gtid in the case on either when cluster is
slave/master in async replication. In normal Gtid replication gtid are generated on
recieving node itself and it is always on sync with other nodes. Because galera keeps
node in sync , So all nodes get same no of event groups. So the issue arises when
say galera is slave in async replication.
A
| (Async replication)
D <-> E <-> F {Galera replication}
So what should happen is that all node should apply the master gtid but this does
node happen, becuase node E, F does not recieve gtid from D in write set , So what E(or F)
does is that it applies wsrep_gtid_domain_id, D server-id , E gtid next seq no. This
generated gtid does not always work when say A has different domain id.

So In this commit, on galera node when we see that this event is recieved from master
we simply write Gtid_Log_Event in write_set and send it to other nodes.

bb-10.2-serg 2017-12-24 18:59:30 UTC 2017-12-24
Appveyor: apply feedback from wlad, timeout=4

Author: Daniel Black
Author Date: 2017-11-17 16:05:22 UTC

Appveyor: apply feedback from wlad, timeout=4

PKG_CONFIG does not really work on Windows, Strawberry perl's uses mingw
libraries, which VS compiler cannot use,

BOOST not used.

Tests main.query_cache_debug and main.mdev-504 timed out on debug build
at 2 minutes so increase the timeout to 4 minutes.

Overall build time was 30 min 44 seconds so plenty of time currently.

Signed-off-by: Daniel Black <daniel@linux.vnet.ibm.com>

bb-10.3-MDEV14638-1 2017-12-22 15:20:47 UTC 2017-12-22
Restore an assertion

Author: Marko Mäkelä
Author Date: 2017-12-22 15:20:47 UTC

Restore an assertion

10.0-bb-MDEV-14572 2017-12-22 13:00:10 UTC 2017-12-22
MDEV-14572: Assertion `! is_set()' failed in Diagnostics_area::set_eof_status...

Author: Oleksandr Byelkin
Author Date: 2017-12-22 13:00:10 UTC

MDEV-14572: Assertion `! is_set()' failed in Diagnostics_area::set_eof_status upon EXPLAIN UPDATE in PS

Restore EXPAIN flag in SELECT_LEX before execution multi-update by flag in LEX
(the same but in other way made before INSERT/DELETE/SELECT)

bb-10.1-varun 2017-12-21 13:44:24 UTC 2017-12-21
MDEV-10797: RPM includes init script and a systemd unit

Author: varun
Author Date: 2017-12-19 21:51:10 UTC

MDEV-10797: RPM includes init script and a systemd unit

For systemd distributions now we only refer to systemd units and not to init.d

bb-10.1-vicentiu 2017-12-20 11:30:05 UTC 2017-12-20
Merge branch '10.0' into 10.1

Author: Vicențiu Ciorbaru
Author Date: 2017-12-20 11:30:05 UTC

Merge branch '10.0' into 10.1

bb-10.0-vicentiu 2017-12-19 18:02:12 UTC 2017-12-19
Merge remote-tracking branch 'origin/5.5' into bb-10.0-vicentiu

Author: Vicențiu Ciorbaru
Author Date: 2017-12-19 18:02:12 UTC

Merge remote-tracking branch 'origin/5.5' into bb-10.0-vicentiu

bb-10.1-MDEV-14701 2017-12-19 11:29:43 UTC 2017-12-19
MDEV-14701: install_db shows corruption for rest encryption with innodb_data_...

Author: Jan Lindström
Author Date: 2017-12-19 11:29:43 UTC

MDEV-14701: install_db shows corruption for rest encryption with innodb_data_file_path=ibdata1:3M

Problem was that crypt_data->min_key_version is not a realible way
to detect is tablespace encrypted and could lead that in first page
of the second (page 192 and similarly for other files if more configured)
system tablespace file used key_version is replaced with zero leading
a corruption as in next startup page is though to be corrupted.

fil_write_flushed_lsn
 Use crypt_data->should_encrypt() instead.

bb-10.2-mdev14629 2017-12-19 09:49:40 UTC 2017-12-19
MDEV-14629: failing assertion when a user-defined variable is defined by the ...

Author: Galina Shalygina
Author Date: 2017-12-19 09:49:40 UTC

MDEV-14629: failing assertion when a user-defined variable is defined by the recursive CTE

During the user-defined variable defined by the recursive CTE handling procedure
check_dependencies_in_with_clauses that checks dependencies between the tables
that are defined in the CTE and find recursive definitions wasn't called.

bb-10.1-hf 2017-12-18 15:31:26 UTC 2017-12-18
MDEV-11084 Select statement with partition selection against MyISAM table ope...

Author: Alexey Botchkov
Author Date: 2017-12-18 15:31:26 UTC

MDEV-11084 Select statement with partition selection against MyISAM table opens all partitions.

        Now SELECT FROM t PARTITION(x) only opens the 'x' file.
        The table->partition_names parameter is sent to ha_open
        so it only opens the required partitions.
        If the table is reopened, the
        change_partition_to_open(partition_names) is called that
        closes and opens partitions specified for the query.

bb-10.3-mdev14579 2017-12-18 13:51:27 UTC 2017-12-18
Test result changed

Author: Galina Shalygina
Author Date: 2017-12-17 19:25:48 UTC

Test result changed

bb-10.3-semisync 2017-12-18 11:43:38 UTC 2017-12-18
MDEV-13073. This patch is a followup of the previous one to convert the trail...

Author: Andrei Elkin
Author Date: 2017-11-27 19:06:17 UTC

MDEV-13073. This patch is a followup of the previous one to convert the trailing underscore identifier to mariadb standard. For identifier representing class private members the underscore is replaced with a `m_` prefix. Otherwise `_` is just removed.

bb-10.2-ext-pentve 2017-12-16 21:18:41 UTC 2017-12-16
MDEV-14315 -- Reflect use of tcmalloc in a system variable and error log

Author: Vesa Pentti
Author Date: 2017-12-11 19:20:37 UTC

MDEV-14315 -- Reflect use of tcmalloc in a system variable and error log

  * The version of tcmalloc is written to the system variable
    'version_malloc_library' if tcmalloc is used, similarly to
    jemalloc
  * Extracted method guess_malloc_library()

bb-10.3-pentve 2017-12-15 20:19:01 UTC 2017-12-15
Test cleanup related to MDEV-12501

Author: Vesa Pentti
Author Date: 2017-12-14 09:19:53 UTC

Test cleanup related to MDEV-12501

 * Removing unnecessary --plugin-maturity=unknown definitions from tests

bb-10.3-pentve2 2017-12-15 17:55:40 UTC 2017-12-15
A fix of mtr bug uncovered by MDEV-12501: passing of parameters in rebootstrap

Author: Vesa Pentti
Author Date: 2017-12-14 12:39:12 UTC

A fix of mtr bug uncovered by MDEV-12501: passing of parameters in rebootstrap

bb-10.0-serg 2017-12-15 15:38:56 UTC 2017-12-15
MDEV-14641 Incompatible key or row definition between the MariaDB .frm file a...

Author: Sergei Golubchik
Author Date: 2017-12-15 15:38:46 UTC

MDEV-14641 Incompatible key or row definition between the MariaDB .frm file and the information in the storage engine

make sure that mysql_create_frm_image() and fast_alter_partition_table()
use the same code to derive HA_OPTION_PACK_RECORD from
create_info->row_type.

bb-10.3-hidden-serg 2017-12-14 13:47:27 UTC 2017-12-14
mysqldump fix for invisible column

Author: Sachin Setiya
Author Date: 2017-12-14 13:47:27 UTC

mysqldump fix for invisible column

Actually there are 2 issues in the case of invisible columns

  1st `select fields from t1` will have more fields then `select * from t1`.
So instead of `select * from t1` we are using `select a,b,invisible from t1`
these fields are supplied from `select fields from t1`.

  2nd We are using --complete-insert when we detect that this table is using
invisible columns.

bb-10.1-MDEV-14524 2017-12-13 10:52:53 UTC 2017-12-13
MDEV-14524 TokuDB is unable to be built on Linux

Author: Oleksandr Byelkin
Author Date: 2017-12-13 10:52:53 UTC

MDEV-14524 TokuDB is unable to be built on Linux

tokudb needs either F_NOCACHE or O_DIRECT, not both

bb-10.2-spider 2017-12-12 21:43:05 UTC 2017-12-12
MDEV-14568: Server does not shut down with SIGTERM after installing

Author: Jacob Mathew
Author Date: 2017-12-05 19:18:47 UTC

MDEV-14568: Server does not shut down with SIGTERM after installing
            Spider 3.3 plugin

- Server shutdown hangs when it waits for the new Spider 3.3 table
  background threads to stop despite being unable to signal them to stop

- Changed the way that the new Spider 3.3 table background threads are
  created in order to enable server shutdown to signal them to stop

bb-10.0-galera 2017-12-11 09:22:52 UTC 2017-12-11
MDEV-14616: WSREP has not yet prepared node for application use error

Author: Jan Lindström
Author Date: 2017-12-11 09:22:52 UTC

MDEV-14616: WSREP has not yet prepared node for application use error

Contains following Galera fixes:

MW-405 Make sure wsrep is ready in wait_until_connected_again.inc

       wait_until_connected_again issues 'SHOW STATUS' query repeatedly
       until mysqld replies without errors. However, SHOW STATUS is
       treated specially by wsrep in that it is allowed to proceed
       even if wsrep is not yet in ready state. As a consequence,
       after returning from wait_until_connected_again, wsrep may
       not be ready yet and subsequent queries may fail with error
       "1047 WSREP has not yet prepared node for application use".
       To avoid those errors, the patch includes
       wait_wsrep_ready.inc at the end of the wait_until_connected_again.inc

       kill_galera.inc can no longer rely on wait_until_connected_again.inc.
       This is because wait_until_connected_again now tries to make sure
       that the server it is connected eventually transition to ready state.
       Whereas some tests may need to kill galera while the server is in a
       non-primary view.

MW-408 Fix 'WSREP error while trying to determine node state'

       mysql-test-run.pl sporadically reports 'WSREP error while
       trying to determine node state' right after starting servers
       for test execution. This happens because we try to execute a
       SELECT statement that queries the current value of status variable
       wsrep_ready. If this statement fails, the above message is reported.
       The failure is due to fact that wsrep may return error
       ER_LOCK_WAIT_TIMEOUT (on any SELECT statement) if it is not ready
       and wsrep_sync_wait enabled for SELECTs. The fix is to disable
       wsrep_sync_wait for the session that issues those SELECT statements.

bb-10.3-varun 2017-12-09 16:49:20 UTC 2017-12-09
MDEV-14573: Upgrade from previous versions is broken for procedures

Author: varun
Author Date: 2017-12-09 13:34:33 UTC

MDEV-14573: Upgrade from previous versions is broken for procedures

10.3-varun 2017-12-09 13:34:33 UTC 2017-12-09
MDEV-14573: Upgrade from previous versions is broken for procedures

Author: varun
Author Date: 2017-12-09 13:34:33 UTC

MDEV-14573: Upgrade from previous versions is broken for procedures

bb-10.1-galera 2017-12-09 09:21:56 UTC 2017-12-09
Add Galera test cases that fail to disabled.

Author: Jan Lindström
Author Date: 2017-12-09 09:21:56 UTC

Add Galera test cases that fail to disabled.

bb-10.3-wlad 2017-12-08 15:01:46 UTC 2017-12-08
MDEV-14113 Use abortive TCP close, in case server closes the connection

Author: Vladislav Vaintroub
Author Date: 2017-12-04 18:53:19 UTC

MDEV-14113 Use abortive TCP close, in case server closes the connection
first, and does not care whether client has received all data.

This is a TCP optimization, avoids TIME_WAIT in TCP connection teardown,
which can lead to port exhaustion.

This patch would abort connection on timeout, which usually happens when
client reads a large result set, at slower pace then the server can
write.

The patch also cleans up socket timeout handling, so that Windows
is consistent with another platforms (using nonblocking socket IO
 + waiting in poll/select on single socket, rather than setsockopt).
This makes identifying timeouts easier.

Also removed the superficial shutdown() before closesocket() in a few
places where it was used, because it was never needed , and
reportedly breaks SO_LINGER on Windows.

bb-10.3-MDEV-14568 2017-12-05 19:18:47 UTC 2017-12-05
MDEV-14568: Server does not shut down with SIGTERM after installing

Author: Jacob Mathew
Author Date: 2017-12-05 19:18:47 UTC

MDEV-14568: Server does not shut down with SIGTERM after installing
            Spider 3.3 plugin

- Server shutdown hangs when it waits for the new Spider 3.3 table
  background threads to stop despite being unable to signal them to stop

- Changed the way that the new Spider 3.3 table background threads are
  created in order to enable server shutdown to signal them to stop

bb-10.2-galera 2017-12-05 14:14:18 UTC 2017-12-05
MDEV-14401: Stored procedure that declares a handler that catches ER_LOCK_DEA...

Author: Jan Lindström
Author Date: 2017-12-05 08:05:58 UTC

MDEV-14401: Stored procedure that declares a handler that catches ER_LOCK_DEADLOCK error causes thd->is_error() assertion

This was missing bug fix from MySQL wsrep i.e. Galera.
Problem was that if stored procedure declares a handler that
catches deadlock error, then the error may have been
cleared in method sp_rcontext::handle_sql_condition().
Use wsrep_conflict_state correctly to determine is the
error already sent to client.

Add test case for both this bug and MDEV-12837: WSREP: BF
lock wait long. Test requires both fixes to pass.

MariaDB adjustments for MW-388 related tests and
set up galera configuration correctly to avoid unnecessary
test failures.

bb-10.3-galera4 2017-12-05 08:36:42 UTC 2017-12-05
Fix galera.partition

Author: Vasil Dimov
Author Date: 2017-12-05 08:33:48 UTC

Fix galera.partition

TC_LOG::log_and_order() returns 0 on failure and != 0 cookie number on
success. The caller at wsrep_tc_log_commit() was expecting != 0 on
failure. In addition to that, --record the test to account for
differences between MySQL and MariaDB.

bb-10.3-vicentiu 2017-12-03 16:02:28 UTC 2017-12-03
MDEV-7773: Aggregate stored functions

Author: varun
Author Date: 2017-11-22 19:09:24 UTC

MDEV-7773: Aggregate stored functions

This commit implements aggregate stored functions. The basic idea behind
the feature is:

* Implement a special instruction FETCH GROUP NEXT ROW that will pause
the execution of the stored function. When the instruction is reached,
execution of the initial query resumes "as if" the function returned.
This gives the server the opportunity to advance to the next row in the
result set.

* Stored aggregates behave like regular aggregate functions. The
implementation of thus resides in the class Item_sum_sp. Because it is
an aggregate function, for each new row in the group, the
Item_sum_sp::add() method will be called. This is when execution resumes
and the function does another iteration to "add" one extra element to
the final result.

* When the end of group is reached, val_xxx() method will be called for
the item. This case is handled by another execute step for the stored
function, only with a special flag to force a call to the return
handler. See Item_sum_sp::execute() for details.

To allow this pause and resume semantic, we must preserve the function
context across executions. This is stored in Item_sp::sp_query_arena only for
aggregate stored functions, but has no impact for regular functions.

We also enforce aggregate functions to include the "FETCH GROUP NEXT ROW"
instruction.

Signed-off-by: Vicențiu Ciorbaru <vicentiu@mariadb.org>

bb-10.3-spider 2017-12-02 19:50:08 UTC 2017-12-02
Remove compiler warnings

Author: Monty
Author Date: 2017-12-02 19:50:08 UTC

Remove compiler warnings

bb-hidden-test 2017-12-01 21:33:00 UTC 2017-12-01
Windows Fix 2

Author: Sachin Setiya
Author Date: 2017-12-01 21:33:00 UTC

Windows Fix 2

bb-10.3-svoj 2017-11-30 09:33:12 UTC 2017-11-30
Optimized event mutex

Author: Sergey Vojtovich
Author Date: 2017-11-24 07:47:50 UTC

Optimized event mutex

bb-10.2-MDEV-12837 2017-11-29 11:04:44 UTC 2017-11-29
Fix compiler error when WITH_WSREP is not defined.

Author: Jan Lindström
Author Date: 2017-11-29 11:04:44 UTC

Fix compiler error when WITH_WSREP is not defined.

bb-10.2-semisync_ali 2017-11-28 20:39:37 UTC 2017-11-28
MDEV-13073. This patch is a followup of the previous one to convert the trail...

Author: Andrei Elkin
Author Date: 2017-11-27 19:06:17 UTC

MDEV-13073. This patch is a followup of the previous one to convert the trailing underscore identifier to mariadb standard. For identifier representing class private members the underscore is replaced with a `m_` prefix. Otherwise `_` is just removed.

ks-bb-10.2-spider 2017-11-26 21:06:54 UTC 2017-11-26
merge Spider 3.3.13

Author: Kentoku SHIBA
Author Date: 2017-11-26 21:06:54 UTC

merge Spider 3.3.13

bb-10.1-wlad 2017-11-23 21:01:00 UTC 2017-11-23
MDEV-14447 mariabackup incremental incorrectly extends system tablespace

Author: Vladislav Vaintroub
Author Date: 2017-11-23 21:01:00 UTC

MDEV-14447 mariabackup incremental incorrectly extends system tablespace
for multi-file innodb_data_file_path.

Use fil_extend_space_to_desired_size() to correctly extend system
tablespace. Make sure to get tablespace size from the first tablespace
part.

aggregagte_functions 2017-11-23 13:23:27 UTC 2017-11-23
Updated tests and result files

Author: varun
Author Date: 2017-11-23 10:36:53 UTC

Updated tests and result files

bb-10.2-alice 2017-11-17 09:09:11 UTC 2017-11-17
tbsp_w

Author: Alice Sherepa
Author Date: 2017-11-17 09:09:11 UTC

tbsp_w

bb-10.2-wlad-rocksdb 2017-11-16 22:11:08 UTC 2017-11-16
Fix rocksdb tests on Windows

Author: Vladislav Vaintroub
Author Date: 2017-11-16 22:11:08 UTC

Fix rocksdb tests on Windows

bb-10.2-semisync 2017-11-16 19:14:59 UTC 2017-11-16
MDEV-13073. Fixed failing on BB sys_vars.rpl_semi_sync_master_enabled_basic. ...

Author: Andrei Elkin
Author Date: 2017-11-16 19:14:59 UTC

MDEV-13073. Fixed failing on BB sys_vars.rpl_semi_sync_master_enabled_basic. The issue forced to add up aan argument to THD::THD and THD::init to propagate skip of a mutex locking. The lock could not be released instead as this leads to clear deadlock; the test is received a piece for concurrent ack thread start/stop.

howard0su-10.2 2017-11-16 08:39:48 UTC 2017-11-16
Support CRC32 SSE2 implementation under Windows

Author: Jun Su
Author Date: 2017-10-25 09:41:23 UTC

Support CRC32 SSE2 implementation under Windows

mdev-13626 2017-11-14 22:22:09 UTC 2017-11-14
innodb tests 563

Author: Alice Sherepa
Author Date: 2017-11-14 22:22:09 UTC

innodb tests 563

10.0-galera 2017-11-14 18:03:54 UTC 2017-11-14
bump the VERSION

Author: Daniel Bartholomew
Author Date: 2017-11-14 18:03:54 UTC

bump the VERSION

bb-10.1-andrei 2017-11-14 17:23:30 UTC 2017-11-14
MDEV-9510 Segmentation fault in binlog thread causes crash

Author: Andrei Elkin
Author Date: 2017-10-16 16:32:02 UTC

MDEV-9510 Segmentation fault in binlog thread causes crash

With combination of --log-bin and Galera the server may crash
reporting two characteristic stacks:

  /usr/sbin/mysqld(_ZN13MYSQL_BIN_LOG13mark_xid_doneEmb+0xc7)[0x7f182a8e2cb7]
  /usr/sbin/mysqld(binlog_background_thread+0x2b5)[0x7f182a8e3275]

or

  /usr/sbin/mysqld(_ZN13MYSQL_BIN_LOG21do_checkpoint_requestEm+0x9d)[0x7ff395b2dafd]
  /usr/sbin/mysqld(_ZN13MYSQL_BIN_LOG20checkpoint_and_purgeEm+0x11)[0x7ff395b2db91]
  /usr/sbin/mysqld(_ZN13MYSQL_BIN_LOG16rotate_and_purgeEb+0xc2)[0x7ff395b300b2]

The reason of the failure appears to be non-matching decrements for
  `xid_count_per_binlog::xid_count`
which can occur when a transaction is executed having its connection issued
`SET @@sql_log_bin=0`. In such case the xid count is not incremented but
its decrements still runs to turn `binlog_xid_count_list` into improper state
which the following FLUSH BINARY LOGS exposes through the crash.

*Note_1*: the regression test reuses an existing galera.sql_log_bin
which does not run stably (even in its base form) by mtr with --log-bin.

*Note_2*: 10.0-galera branch is free of this issue having missed MDEV-7205
fixes.

bb-10.2-MDEV-13206 2017-11-14 09:46:43 UTC 2017-11-14
MDEV-13206: INSERT ON DUPLICATE KEY UPDATE foreign key fail

Author: Jan Lindström
Author Date: 2017-11-14 09:46:43 UTC

MDEV-13206: INSERT ON DUPLICATE KEY UPDATE foreign key fail

This is caused by following change:

commit 95d29c99f01882ffcc2259f62b3163f9b0e80c75
Author: Marko Mäkelä <marko.makela@oracle.com>
Date: Tue Nov 27 11:12:13 2012 +0200

    Bug#15920445 INNODB REPORTS ER_DUP_KEY BEFORE CREATE UNIQUE INDEX COMPLETED

    There is a phase during online secondary index creation where the index has
    been internally completed inside InnoDB, but does not 'officially' exist yet.
    We used to report ER_DUP_KEY in these situations, like this:

    ERROR 23000: Can't write; duplicate key in table 't1'

    What we should do is to let the 'offending' operation complete, but report an
    error to the
    ALTER TABLE t1 ADD UNIQUE KEY (c2):

    ERROR HY000: Index c2 is corrupted
    (This misleading error message should be fixed separately:
    Bug#15920713 CREATE UNIQUE INDEX REPORTS ER_INDEX_CORRUPT INSTEAD OF DUPLICATE)

    row_ins_sec_index_entry_low(): flag the index corrupted instead of
    reporting a duplicate, in case the index has not been published yet.

    rb:1614 approved by Jimmy Yang

Problem is that after we have found duplicate key on primary key
we continue to get necessary gap locks in secondary indexes to
block concurrent transactions from inserting the searched records.
However, search from unique index used in foreign key constraint
could return DB_NO_REFERENCED_ROW if INSERT .. ON DUPLICATE KEY UPDATE
does not contain value for foreign key column. In this case
we should return the original DB_DUPLICATE_KEY error instead
of DB_NO_REFERENCED_ROW.

Imported also missing test case from MySQL 5.7 for

commit 25781c154396dbbc21023786aa3be070057d6999
Author: Annamalai Gurusami <annamalai.gurusami@oracle.com>
Date: Mon Feb 24 14:00:03 2014 +0530

    Bug #17604730 ASSERTION: *CURSOR->INDEX->NAME == TEMP_INDEX_PREFIX

    Problem:

    When INSERT ... ON DUPLICATE UPDATE or REPLACE statements are used, then
    after encountering a DB_DUPLICATE_KEY error, we continue to process all
    the unique secondary indexes to place the necessary gap locks. The
    problem is in the following scenario:

    1. The table has one primary index, one unique secondary index and
       one non-unique secondary index.
    2. The INSERT ... ON DUPLICATE UPDATE ... is executed on the table.
    3. Insert into the clustered index reported DB_DUPLICATE_KEY. This
       error information is saved. We proceed to take gap locks in all
       unique secondary indexes.
    4. Insert into the unique secondary index reported DB_LOCK_WAIT.
    5. Step 4 is repeated from a higher layer row_ins(). When this is
       done, the earlier error information saved in step 3 is lost.
    6. Next instead of taking just gap locks or skipping non-unique
       secondary indexes, because of loss of information regarding the
       error already saved, an actual insert is performed on the non-unique
       secondary index. This triggers the assert.

    Solution:

    Save the error information in a non-local location so that it is not lost.

    rb#4723 approved by Kevin.

szworkshop 2017-11-13 06:05:34 UTC 2017-11-13
Implement File Descriptor Plugin

Author: Vicențiu Ciorbaru
Author Date: 2017-11-13 06:05:34 UTC

Implement File Descriptor Plugin

Made use of /proc filesystem to get list of open file descriptors.
This is implemented as a Information_Schema plugin table PROC_FDINFO.

bb-10.2-spider-extra-jacob 2017-11-10 21:38:09 UTC 2017-11-10
Adding direct update/delete to the server and to the partition engine.

Author: Jacob Mathew
Author Date: 2017-10-14 22:24:24 UTC

Adding direct update/delete to the server and to the partition engine.

Contains Spiral patches:
- Spiral Patch 006: 006_mariadb-10.2.0.direct_update_rows.diff MDEV-7704
- Spiral Patch 008: 008_mariadb-10.2.0.partition_direct_update.diff MDEV-7706
- Spiral Patch 010: 010_mariadb-10.2.0.direct_update_rows2.diff MDEV-7708
- Spiral Patch 011: 011_mariadb-10.2.0.aggregate.diff MDEV-7709
- Spiral Patch 027: 027_mariadb-10.2.0.force_bulk_update.diff MDEV-7724
- Spiral Patch 061: 061_mariadb-10.2.0.mariadb-10.1.8.diff MDEV-12870

- Add support for direct update and direct delete requests. A direct
  update/delete request handles all qualified rows in a single operation,
  rather than one row at a time.

- This commit has the following differences compared to the original patches:
  - Most of the parameters of the new functions are unnecessary. The
    unnecessary parameters have been removed.
  - Changed bit positions for new handler flags upon consideration of
    handler flags not needed by other Spiral patches and handler flags
    merged from MySQL.

bb-10.3-MDEV-9059 2017-11-07 16:39:29 UTC 2017-11-07
MDEV-9059: protocol: bundle first command with the authentication packet

Author: Oleksandr Byelkin
Author Date: 2017-11-06 10:23:32 UTC

MDEV-9059: protocol: bundle first command with the authentication packet

bb-10.0-galera-andrii 2017-11-06 09:51:57 UTC 2017-11-06
re-enable tests which succeeded altogether twice with: --par=6 --repeat=10

Author: Andrii Nikitin
Author Date: 2017-11-06 09:51:57 UTC

re-enable tests which succeeded altogether twice with: --par=6 --repeat=10

bb-10.0-elenst 2017-11-04 23:30:40 UTC 2017-11-04
MDEV-14288 Add MTR option to run tests with real server defaults

Author: Elena Stepanova
Author Date: 2017-11-04 23:30:40 UTC

MDEV-14288 Add MTR option to run tests with real server defaults

bb-10.0-sachin-galera 2017-11-03 07:04:05 UTC 2017-11-03
Merge tag 'mariadb-10.0.33' into bb-10.0-galera

Author: sachin
Author Date: 2017-11-03 07:04:05 UTC

Merge tag 'mariadb-10.0.33' into bb-10.0-galera

bb-10.0-elenst-mdev14029 2017-11-01 16:40:09 UTC 2017-11-01
MDEV-14029 Server does not remove #sql*.frm files after crash during ALTER TABLE

Author: Elena Stepanova
Author Date: 2017-11-01 16:40:09 UTC

MDEV-14029 Server does not remove #sql*.frm files after crash during ALTER TABLE

Add a check for #sql* files in test and mysql subdirs to the testcase check

svoj-szworkshop 2017-10-31 11:14:29 UTC 2017-10-31
PROC_FDINFO plugin for workshop

Author: Sergey Vojtovich
Author Date: 2017-10-31 11:14:29 UTC

PROC_FDINFO plugin for workshop

mdev-13625 2017-10-31 09:20:00 UTC 2017-10-31
deleted wl6501/(they are relevant only from 10.2.2)

Author: Alice Sherepa
Author Date: 2017-10-31 09:20:00 UTC

deleted wl6501/(they are relevant only from 10.2.2)

bb-10.2-mariarocks-merge 2017-10-28 07:35:40 UTC 2017-10-28
MDEV-14181: rocksdb.rocksdb fails: line 1117: query 'reap' succeeded - should...

Author: Sergey Petrunia
Author Date: 2017-10-28 07:35:40 UTC

MDEV-14181: rocksdb.rocksdb fails: line 1117: query 'reap' succeeded - should have failed

Fix a race condition in the testcase.

bb-10.1-mdev9510-andrei 2017-10-25 14:23:18 UTC 2017-10-25
MDEV-9510 Segmentation fault in binlog thread causes crash

Author: Andrei Elkin
Author Date: 2017-10-16 16:32:02 UTC

MDEV-9510 Segmentation fault in binlog thread causes crash

With combination of --log-bin and Galera the server may crash
reporting two characteristic stacks:

  /usr/sbin/mysqld(_ZN13MYSQL_BIN_LOG13mark_xid_doneEmb+0xc7)[0x7f182a8e2cb7]
  /usr/sbin/mysqld(binlog_background_thread+0x2b5)[0x7f182a8e3275]

or

  /usr/sbin/mysqld(_ZN13MYSQL_BIN_LOG21do_checkpoint_requestEm+0x9d)[0x7ff395b2dafd]
  /usr/sbin/mysqld(_ZN13MYSQL_BIN_LOG20checkpoint_and_purgeEm+0x11)[0x7ff395b2db91]
  /usr/sbin/mysqld(_ZN13MYSQL_BIN_LOG16rotate_and_purgeEb+0xc2)[0x7ff395b300b2]

The reason of the failure appears to be non-matching decrements for
  `xid_count_per_binlog::xid_count`
which can occur when a transaction is executed having its connection issued
`SET @@sql_log_bin=0`. In such case the xid count is not incremented but
its decrements still runs to turn `binlog_xid_count_list` into improper state
which the following FLUSH BINARY LOGS exposes through the crash.

*Note_1*: the regression test reuses an existing galera.sql_log_bin
which does not run stably (even in its base form) by mtr with --log-bin.

*Note_2*: 10.0-galera branch is free of this issue having missed MDEV-7205
fixes.

1100 of 297 results

Other repositories

Name Last Modified
lp:maria 2 hours ago
lp:~maria-captains/maria/+git/connector-c 2018-01-08
12 of 2 results
You can't create new repositories for MariaDB.