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

MariaDB has 18 active reviews.

Branches

Name Last Modified Last Commit
10.4-serg 2019-03-07 15:18:31 UTC 2019-03-07
ANALYZE SELECT with PS fix

Author: Oleksandr Byelkin
Author Date: 2019-03-07 15:18:31 UTC

ANALYZE SELECT with PS fix

bb-10.4-elenst-no-mdev371 2019-02-26 14:50:16 UTC 2019-02-26
MDEV-18719 Assertion (c.prtype ^ o->prtype) & ... failed on ALTER TABLE

Author: Marko Mäkelä
Author Date: 2019-02-25 13:35:00 UTC

MDEV-18719 Assertion (c.prtype ^ o->prtype) & ... failed on ALTER TABLE

The prtype & DATA_LONG_TRUE_VARCHAR flag only plays a role when
converting between InnoDB internal format and the MariaDB SQL layer
row format. Ideally this flag would never have been persisted in the
InnoDB data dictionary.

There were bogus assertion failures when an instant ADD, DROP, or
column reordering was combined with a change of extending a VARCHAR
from less than 256 bytes to more than 255 bytes. Such changes are
allowed starting with MDEV-15563 in MariaDB 10.4.3.

dict_table_t::instant_column(), dict_col_t::same_format(): Ignore
the DATA_LONG_TRUE_VARCHAR flag, because it does not affect the
persistent storage format.

bb-10.2-bar 2019-02-23 05:52:47 UTC 2019-02-23
Backporting MDEV-15597 Add class Load_data_outvar and avoid using Item::STRIN...

Author: Alexander Barkov
Author Date: 2018-03-20 09:02:44 UTC

Backporting MDEV-15597 Add class Load_data_outvar and avoid using Item::STRING_ITEM for Item_user_var_as_out_param detection

This is a part of "MDEV-18045 Backporting the MDEV-15497 changes to 10.2 branch"

10.4-MDEV-17805 2019-02-20 20:42:18 UTC 2019-02-20
WIP MDEV-17805: Remove InnoDB cache for temporary tables

Author: Marko Mäkelä
Author Date: 2019-02-20 20:42:18 UTC

WIP MDEV-17805: Remove InnoDB cache for temporary tables

The intention is to link dict_table_t to TABLE_SHARE.

FIXME: Implement ha_innobase::delete_table() for temporary tables.
FIXME: Implement rollback of ha_innobase::create() for temporary tables.

FIXME: Currently, DBUG_ASSERT(s) fails in ha_innobase::open() because
we fail to pass the InnoDB_share from ha_innobase::create().
This seems to happen for any ALTER TABLE that uses ALGORITHM=COPY

(Old note from December, maybe not true any more:)
An assignment to TABLE_SHARE::ha_share would not work either, because
create() and open() will use different TABLE_SHARE.

bb-10.3.11-xtrabackup_copy_logfile_failed-MDEV-18611 2019-02-19 09:13:56 UTC 2019-02-19
MDEV-18611: mariabackup silently ended during xtrabackup_copy_logfile()

Author: Vlad Lesin
Author Date: 2019-02-18 07:14:21 UTC

MDEV-18611: mariabackup silently ended during xtrabackup_copy_logfile()

log_t::files::read_log_seg() can return true without changing
*start_lsn, what can cause an error in xtrabackup_copy_logfile() retry logic.

bb-10.4-vicentiu 2019-02-18 21:48:07 UTC 2019-02-18
Cleanup statistics test

Author: Vicențiu Ciorbaru
Author Date: 2019-02-18 21:48:07 UTC

Cleanup statistics test

bb-10.4-mdev18608 2019-02-18 10:29:01 UTC 2019-02-18
MDEV-18608: Defaults for 10.4: histogram size should be set

Author: Sergey Petrunia
Author Date: 2019-02-18 10:29:01 UTC

MDEV-18608: Defaults for 10.4: histogram size should be set

Followup: update test results

bb-10.4-mdev16188 2019-02-15 19:31:58 UTC 2019-02-15
Merge branch '10.4' into bb-10.4-mdev16188

Author: Sergei Golubchik
Author Date: 2019-02-15 19:31:24 UTC

Merge branch '10.4' into bb-10.4-mdev16188

bb-10.2-mariabackup-remove-nolock 2019-02-14 07:45:25 UTC 2019-02-14
MDEV-18573: avoid backup inconsistency in 10.2

Author: Vlad Lesin
Author Date: 2019-02-13 13:01:38 UTC

MDEV-18573: avoid backup inconsistency in 10.2

--no-lock and --lock-ddl-per-table options deprecared, the corresponing
code is removed. aria_log_control is copied first and aria_log.# files last
under FTWRL.

bb-10.4-mdev17096 2019-02-13 22:59:34 UTC 2019-02-13
Merge branch '10.4' into bb-10.4-mdev17096

Author: Igor Babaev
Author Date: 2019-02-13 22:59:34 UTC

Merge branch '10.4' into bb-10.4-mdev17096

bb-10.4-wolfssl 2019-02-12 23:31:38 UTC 2019-02-12
WIP

Author: Vladislav Vaintroub
Author Date: 2019-02-12 23:31:38 UTC

WIP

10.4-vicentiu-histograms 2019-02-09 23:43:15 UTC 2019-02-09
Default Bernoulli Sampling implementation

Author: Vicențiu Ciorbaru
Author Date: 2019-02-09 23:43:15 UTC

Default Bernoulli Sampling implementation

bb-10.4-vicentiu-histograms 2019-02-09 23:43:15 UTC 2019-02-09
Default Bernoulli Sampling implementation

Author: Vicențiu Ciorbaru
Author Date: 2019-02-09 23:43:15 UTC

Default Bernoulli Sampling implementation

10.0-galera 2019-02-04 21:49:23 UTC 2019-02-04
bump the VERSION

Author: Daniel Bartholomew
Author Date: 2019-02-04 21:49:23 UTC

bump the VERSION

10.4-mdev16188 2019-02-03 20:25:17 UTC 2019-02-03
MDEV-16188: cleaup of the previous commit.

Author: Igor Babaev
Author Date: 2019-02-03 20:25:17 UTC

MDEV-16188: cleaup of the previous commit.

bb-14005-hf 2019-02-03 17:23:35 UTC 2019-02-03
MODIFY idx_read_map

Author: Alexey Botchkov
Author Date: 2019-02-03 17:23:35 UTC

MODIFY idx_read_map

bb-10.4-hf 2019-02-01 22:06:05 UTC 2019-02-01
MDEV-14005

Author: Alexey Botchkov
Author Date: 2019-02-01 22:06:05 UTC

MDEV-14005

5.5-galera 2019-02-01 15:47:27 UTC 2019-02-01
bump the VERSION

Author: Daniel Bartholomew
Author Date: 2019-02-01 15:47:27 UTC

bump the VERSION

bb-10.2-andrei 2019-02-01 15:27:50 UTC 2019-02-01
/binlog_mysqlbinlog_row_frag fixes.

Author: Andrei Elkin
Author Date: 2019-02-01 15:27:50 UTC

/binlog_mysqlbinlog_row_frag fixes.

bb-10.2-vicentiu 2019-02-01 13:47:05 UTC 2019-02-01
Fix is_check_constraints.result to be compatibile with 10.3

Author: Anel Husakovic
Author Date: 2019-01-24 11:06:56 UTC

Fix is_check_constraints.result to be compatibile with 10.3

The patch is done according to the original patch for MDEV 14474
1edd09c325525cba33152 and not one which is merged on server
d526679efd108478cc2af07578
This patch includes:
- Rename from `is_check_constraint` to `is_check_constraints` to tests
and results
- Change `get_check_constraints_record` to be consistent to `10.3`
- Change the order of fields in IS check_constraints table according to
the standard and MDEV 14474
- Original patch and one in `10.3` supports embedded server this patch doesn't
support (embedded not included in test) but could-TBD?

bb-10.2-compatibility-deadlock 2019-01-30 15:36:49 UTC 2019-01-30
fix the test for 2019

Author: Sergei Golubchik
Author Date: 2019-01-02 11:03:15 UTC

fix the test for 2019

bb-5.5-varun 2019-01-29 12:52:53 UTC 2019-01-29
MDEV-15950: LOAD DATA INTO compex_view crashed

Author: varun
Author Date: 2019-01-29 12:52:53 UTC

MDEV-15950: LOAD DATA INTO compex_view crashed

For multi-table views with LOAD, updates are not allowed, so
we should just throw an error.

10.4-blob-index-optimizer-serg 2019-01-28 21:06:49 UTC 2019-01-28
Fix optimizer

Author: Sachin Setiya
Author Date: 2019-01-28 21:06:49 UTC

Fix optimizer

bb-10.0-serg 2019-01-24 12:35:14 UTC 2019-01-24
Squashed commit of connect/10.0:

Author: Olivier Bertrand
Author Date: 2018-12-01 23:25:05 UTC

Squashed commit of connect/10.0:

commit 6a6a1f37798
Author: Olivier Bertrand <bertrandop@gmail.com>
Date: Fri Jan 4 12:31:52 2019 +0100

    - Fix a few bug mainly concerning discovery and call from OEM
      (and prepare new table types)

      modified: storage/connect/tabjson.cpp
      modified: storage/connect/tabjson.h
      modified: storage/connect/tabxml.cpp
      modified: storage/connect/tabxml.h

    - Fix wrong line estimate
      modified: storage/connect/mysql-test/connect/r/part_table.result
      modified: storage/connect/mysql-test/connect/t/part_table.test

commit bd7d2e912d9
Author: Olivier Bertrand <bertrandop@gmail.com>
Date: Tue Dec 4 23:35:09 2018 +0100

    Fix wrong version number

commit 4933680e7ab
Author: Olivier Bertrand <bertrandop@gmail.com>
Date: Sun Dec 2 00:25:05 2018 +0100

    - Make PlugSubAlloc to be exportable
      Suppress unused parameter from PlugSubSet
      modified: storage/connect/global.h
      modified: storage/connect/plugutil.cpp
      modified: storage/connect/jsonudf.cpp
      modified: storage/connect/tabjson.cpp
      modified: storage/connect/user_connect.cc

    - Fix a bug making column catalog XML tables fail
      modified: storage/connect/tabxml.cpp

    - Comment out wrong message
      modified: storage/connect/ha_connect.cc

    - Update error message when sorting an ODBC table fails
      modified: storage/connect/tabodbc.cpp

    - Add error message when gettting an address
      from an OEM fails.
      modified: storage/connect/reldef.cpp

    - Make some modifications useful for OEM module writting
      Export discovery functions for CSV, JDBC and XML
      Remove unuseful include from tabjson.h
      Move TDBXML::data_charset function from header file to source
      modified: storage/connect/tabfmt.h
      modified: storage/connect/tabjson.h
      modified: storage/connect/tabxml.cpp
      modified: storage/connect/tabxml.h

    - Update test result
      modified: storage/connect/mysql-test/connect/r/jdbc_oracle.result

bb-10.3-MDEV-17401 2019-01-24 09:43:27 UTC 2019-01-24
MDEV-17401: LOAD DATA from very big file into MyISAM table results in EOF err...

Author: Oleksandr Byelkin
Author Date: 2019-01-24 09:43:27 UTC

MDEV-17401: LOAD DATA from very big file into MyISAM table results in EOF error and corrupt index

fix of incorrect 10.3 merge

bb-5.5-vicentiu 2019-01-23 23:03:06 UTC 2019-01-23
MDEV-18360 Prevent set_max_open_files from allocating too many files

Author: Vicențiu Ciorbaru
Author Date: 2019-01-23 22:58:20 UTC

MDEV-18360 Prevent set_max_open_files from allocating too many files

If the rlimit.rlim_cur value returned by getrlimit is not the
RLIM_INFINITY magic constant, but a *very* large number, we can allocate
too many open files. Restrict set_max_open_files to only return at most
max_file_limit, as passed via its parameter.

hf-s25102 2019-01-23 19:26:06 UTC 2019-01-23
Support issue 25102.

Author: Alexey Botchkov
Author Date: 2019-01-23 19:26:06 UTC

Support issue 25102.

bb-10.0-andrei 2019-01-22 12:55:28 UTC 2019-01-22
MDEV-17803 Row-based event is not applied when table map id is greater

Author: Andrei Elkin
Author Date: 2019-01-10 14:32:56 UTC

MDEV-17803 Row-based event is not applied when table map id is greater
           32 bit int

Row-based slave applier could not parse correctly the table id when
the value exceeded the max of 32 bit unsigned int.
The reason turns out in that the being parsed value placeholder
was sized as 4 bytes.

The type is fixed to ulonglong.

Additionally the patch works around Rows_log_event::m_table_id 4 bytes
size on 32 bits platforms. In case of last_table_id value overflows
the 4 byte max, there won't be the zero value for m_table_id generated
and the first wrapped-around value is one, this is thanks to excluding
UINT_MAX32 + 1 from TABLE_SHARE::table_map_id.

bb-10.1-17588 2019-01-18 11:09:11 UTC 2019-01-18
mdev-17588

Author: Sachin Setiya
Author Date: 2019-01-18 11:09:11 UTC

mdev-17588

10.4-nss 2019-01-15 15:44:13 UTC 2019-01-15
fixup! Fixed compiler warnings from optimized builds

Author: Vladislav Vaintroub
Author Date: 2019-01-15 15:44:13 UTC

fixup! Fixed compiler warnings from optimized builds

bb-10.3-mdev15101 2019-01-11 20:57:11 UTC 2019-01-11
Apply this patch from Percona Server:

Author: Sergey Petrunia
Author Date: 2019-01-11 20:57:11 UTC

Apply this patch from Percona Server:

commit cd7201514fee78aaf7d3eb2b28d2573c76f53b84
Author: Laurynas Biveinis <laurynas.biveinis@gmail.com>
Date: Tue Nov 14 06:34:19 2017 +0200

    Fix bug 1704195 / 87065 / TDB-83 (Stop ANALYZE TABLE from flushing table definition cache)

    Make ANALYZE TABLE stop flushing affected tables from the table
    definition cache, which has the effect of not blocking any subsequent
    new queries involving the table if there's a parallel long-running
    query:

    - new table flag HA_ONLINE_ANALYZE, return it for InnoDB and TokuDB
      tables;
    - in mysql_admin_table, if we are performing ANALYZE TABLE, and the
      table flag is set, do not remove the table from the table
      definition cache, do not invalidate query cache;
    - in partitioning handler, refresh the query optimizer statistics
      after ANALYZE if the underlying handler supports HA_ONLINE_ANALYZE;
    - new testcases main.percona_nonflushing_analyze_debug,
      parts.percona_nonflushing_abalyze_debug and a supporting debug sync
      point.

    For TokuDB, this change exposes bug TDB-83 (Index cardinality stats
    updated for handler::info(HA_STATUS_CONST), not often enough for
    tokudb_cardinality_scale_percent). TokuDB may return different
    rec_per_key values depending on dynamic variable
    tokudb_cardinality_scale_percent value. The server does not have a way
    of knowing that changing this variable invalidates the previous
    rec_per_key values in any opened table shares, and so does not call
    info(HA_STATUS_CONST) again. Fix by updating rec_per_key for both
    HA_STATUS_CONST and HA_STATUS_VARIABLE. This also forces a re-record
    of tokudb.bugs.db756_card_part_hash_1_pick, with the new output
    seeming to be more correct.

bb-10.1-mdev17761 2018-12-30 08:36:37 UTC 2018-12-30
Better comment

Author: Sergey Petrunia
Author Date: 2018-12-30 08:36:37 UTC

Better comment

bb-10.4-MDEV-17520-2 2018-12-27 17:44:35 UTC 2018-12-27
Try to ensure that rollback of inserting metadata record works

Author: Marko Mäkelä
Author Date: 2018-12-05 18:14:24 UTC

Try to ensure that rollback of inserting metadata record works

We must use the original page format for inserting metadata records.
This is because in case the instant ALTER TABLE operation needs to
be rolled back (due to crash recovery), all pages must remain in
the original format.

btr_cur_optimistic_insert(): Avoid reorganize for inserting the
metadata record.

btr_cur_optimistic_update(): Initialize rec,offsets correctly
after possible page format conversion.

innobase_instant_try(): Do not store NULL values for those
metadata record columns that were originally declared NOT NULL.

dict_index_t::get_n_nullable(): Refer to dict_col_t::was_not_null()
in order to keep the original format intact.

lock_move_reorganize_page(): Allow the two pages to be in
different formats.

rec_convert_dtuple_to_rec_comp(), rec_convert_dtuple_to_rec_comp():
Also observe the DATA_WAS_NOT_NULL flag.

bb-10.1-15839 2018-12-19 23:16:10 UTC 2018-12-19
MDEV-15839 replicate-filter for a connection name with a dot

Author: Sachin Setiya
Author Date: 2018-12-19 23:14:04 UTC

MDEV-15839 replicate-filter for a connection name with a dot

In replication channel name we can have name like a.b.c.replicate_do_db
so instead of going for first '.' we should go for the '.' just before
 '=', Which is actual key_name

bb-10.1-MDEV-10963 2018-12-18 16:28:59 UTC 2018-12-18
MDEV-10963 Fragmented BINLOG query

Author: Andrei Elkin
Author Date: 2018-07-27 19:55:18 UTC

MDEV-10963 Fragmented BINLOG query

The problem was originally stated in
  http://bugs.mysql.com/bug.php?id=82212
The size of an base64-encoded Rows_log_event exceeds its
vanilla byte representation in 4/3 times.
When a binlogged event size is about 1GB mysqlbinlog generates
a BINLOG query that can't be send out due to its size.

It is fixed with fragmenting the BINLOG argument C-string into
(approximate) halves when the base64 encoded event is over 1GB size.
The mysqlbinlog in such case puts out

    SET @binlog_fragment_0='base64-encoded-fragment_0';
    SET @binlog_fragment_1='base64-encoded-fragment_1';
    BINLOG @binlog_fragment_0, @binlog_fragment_1;

to represent a big BINLOG.
For prompt memory release BINLOG handler is made to reset the BINLOG argument
user variables in the middle of processing, as if @binlog_fragment_{0,1} = NULL
is assigned.

Notice the 2 fragments are enough, though the client and server still may
need to tweak their @@max_allowed_packet to satisfy to the fragment
size (which they would have to do anyway with greater number of
fragments, should that be desired).

On the lower level the following changes are made:

Log_event::print_base64()
  remains to call encoder and store the encoded data into a cache but
  now *without* doing any formatting. The latter is left for time
  when the cache is copied to an output file (e.g mysqlbinlog output).
  No formatting behavior is also reflected by the change in the meaning
  of the last argument which specifies whether to cache the encoded data.

Rows_log_event::print_helper()
  is made to invoke a specialized fragmented cache-to-file copying function
  which is

copy_cache_to_file_wrapped()
  that takes care of fragmenting also optionally wraps encoded
  strings (fragments) into SQL stanzas.

my_b_copy_to_file()
  is refactored to into my_b_copy_all_to_file(). The former function
  is generalized
  to accepts more a limit argument to constraint the copying and does
  not reinitialize anymore the cache into reading mode.
  The limit does not do any effect on the fully read cache.

bb-10.4-MDEV-17520 2018-12-07 14:32:32 UTC 2018-12-07
Merge 10.4 into HEAD

Author: Marko Mäkelä
Author Date: 2018-12-07 14:32:32 UTC

Merge 10.4 into HEAD

bb-10.4-knielsen 2018-12-06 18:44:29 UTC 2018-12-06
Move deletion of old GTID rows to slave background thread

Author: Kristian Nielsen
Author Date: 2018-10-14 18:41:49 UTC

Move deletion of old GTID rows to slave background thread

This patch changes how old rows in mysql.gtid_slave_pos* tables are deleted.
Instead of doing it as part of every replicated transaction in
record_gtid(), it is done periodically (every @@gtid_cleanup_batch_size
transaction) in the slave background thread.

This removes the deletion step from the replication process in SQL or worker
threads, which could speed up replication with many small transactions. It
also decreases contention on the global mutex LOCK_slave_state. And it
simplifies the logic, eg. when a replicated transaction fails after having
deleted old rows.

With this patch, the deletion of old GTID rows happens asynchroneously and
slightly non-deterministic. Thus the number of old rows in
mysql.gtid_slave_pos can temporarily exceed @@gtid_cleanup_batch_size. But
all old rows will be deleted eventually after sufficiently many new GTIDs
have been replicated.

bb-10.2gr 2018-12-05 16:36:34 UTC 2018-12-05
Windows fixes

Author: Georg Richter
Author Date: 2018-12-05 16:36:34 UTC

Windows fixes

bb_mdev14101 2018-12-03 12:55:20 UTC 2018-12-03
MDEV-14101: Provide option to specify tls_version for client tools

Author: Georg Richter
Author Date: 2018-12-03 12:55:20 UTC

MDEV-14101: Provide option to specify tls_version for client tools

bb-10.3-knielsen 2018-11-25 18:38:33 UTC 2018-11-25
Move deletion of old GTID rows to slave background thread

Author: Kristian Nielsen
Author Date: 2018-10-14 18:41:49 UTC

Move deletion of old GTID rows to slave background thread

This patch changes how old rows in mysql.gtid_slave_pos* tables are deleted.
Instead of doing it as part of every replicated transaction in
record_gtid(), it is done periodically (every @@gtid_cleanup_batch_size
transaction) in the slave background thread.

This removes the deletion step from the replication process in SQL or worker
threads, which could speed up replication with many small transactions. It
also decreases contention on the global mutex LOCK_slave_state. And it
simplifies the logic, eg. when a replicated transaction fails after having
deleted old rows.

With this patch, the deletion of old GTID rows happens asynchroneously and
slightly non-deterministic. Thus the number of old rows in
mysql.gtid_slave_pos can temporarily exceed @@gtid_cleanup_batch_size. But
all old rows will be deleted eventually after sufficiently many new GTIDs
have been replicated.

bb-10.4-MDEV-15073 2018-11-20 09:58:34 UTC 2018-11-20
MDEV-15073: Generic UDAF parser code in server for windows functions

Author: Oleksandr Byelkin
Author Date: 2018-11-20 09:58:34 UTC

MDEV-15073: Generic UDAF parser code in server for windows functions

Added support for usual agreggate UDF (UDAF)
Added remove() call support for more efficient window function processing
Added example of aggregate UDF with efficient windows function support

bb-10.1-MDEV-17124 2018-11-13 09:10:09 UTC 2018-11-13
MDEV-17124: mariadb 10.1.34, views and prepared statements: ERROR 1615 (HY00...

Author: Oleksandr Byelkin
Author Date: 2018-11-13 09:10:09 UTC

MDEV-17124: mariadb 10.1.34, views and prepared statements: ERROR 1615 (HY000): Prepared statement needs to be re-prepared

The problem is that if table definition cache (TDC) is full of real tables which are in tables cache, view definition can not stay there so will me removed by its own underlying tables.
In situation above old mechanism of detection matching definition in PS and current version always require reprepare and so prevent executing the PS.
One work arount is to increase TDC, other - improve version check for views (which is done here).
Now in suspiciouse cases we check MD5 of the view to be sure that version really have chenged.

bb-10.4-ps 2018-11-12 08:27:41 UTC 2018-11-12
Make mysqltest to use --ps-protocol more

Author: Sergei Golubchik
Author Date: 2018-10-30 18:04:54 UTC

Make mysqltest to use --ps-protocol more

use prepared statements for everything that server supports
with the exception of CALL (for now).

Fix discovered test failures and bugs.

tests:
* PROCESSLIST shows Execute state, not Query
* SHOW STATUS increments status variables more than in text protocol
* multi-statements should be avoided (see tests with a wrong delimiter)
* performance_schema events have different names in --ps-protocol

mysqltest.cc:
* make sure run_query_stmt() doesn't crash if there's
  no active connection (in wait_until_connected_again.inc)

sql_acl.cc:
* extract the functionality of getting the user for SHOW GRANTS
  from check_show_access(), so that mysql_test_show_grants() could
  generate the correct column names in the prepare step

sql_class.cc:
* result->prepare() can fail, don't ignore its return value
* use the correct metadata when creating a column for ANALYZE SELECT.
  The actual value is always FLOAT(4,2), but the column was created
  as FLOAT(4,10), so --ps and text protocols were using different number
  of decimals.

sql_parse.cc:
* discard profiling for SHOW PROFILE. In text protocol it's done in
  prepare_schema_table(), but in --ps it is called on prepare only,
  so nothing was discarding profiling during execute.
* move the permission checking code for SHOW CREATE VIEW to
  mysqld_show_create_get_fields(), so that it would be called during
  prepare step too.
* only set sel_result when it was created here and needs to be
  destroyed in the same block. Avoid destroying lex->result.
* use the correct number of tables in check_show_access(). Saying
  "as many as possible" doesn't work when first_not_own_table isn't
  set yet.

sql_prepare.cc:
* use correct user name for SHOW GRANTS columns
* don't ignore verbose flag for SHOW SLAVE STATUS
* support preparing REVOKE ALL and ROLLBACK TO SAVEPOINT
* don't ignore errors from thd->prepare_explain_fields()

sql_show.cc:
* check grants for SHOW CREATE VIEW here, not in mysql_execute_command

sql_tvc.cc:
* allocate Type_holder and items in the correct arena

sql_view.cc:
* use the correct function to check privileges. Old code was doing
  check_access() for thd->security_ctx, which is invoker's sctx,
  not definer's sctx. Hide various view related errors from the invoker.

bb-10.3-mdev17518 2018-11-01 08:35:28 UTC 2018-11-01
MDEV-17518: Range optimization doesn't use ON expressions from nested outer j...

Author: Sergey Petrunia
Author Date: 2018-11-01 08:35:28 UTC

MDEV-17518: Range optimization doesn't use ON expressions from nested outer joins

Part#2: take into account that join nest that we are marking as constant
might already have constant tables in it. Don't count these tables twice.

bb-5.5-hf 2018-10-30 14:15:41 UTC 2018-10-30
MDEV-17256 Decimal field multiplication bug.

Author: Alexey Botchkov
Author Date: 2018-10-30 14:15:41 UTC

MDEV-17256 Decimal field multiplication bug.

We should clear trailing zeroes in frac part. Otherwise
that tail is growing quickly and forces unnecessary truncating of
arguments.

10.4-mdev-15562 2018-10-19 16:02:30 UTC 2018-10-19
Merge 10.4 into 10.4-mdev-15562

Author: Marko Mäkelä
Author Date: 2018-10-19 16:00:25 UTC

Merge 10.4 into 10.4-mdev-15562

This branch exists just for the record, for preserving the
development history, should it ever be needed.

bb-10.3-MDEV-15447 2018-10-18 16:46:00 UTC 2018-10-18
CTE tests

Author: Larysa Sherepa
Author Date: 2018-10-18 16:46:00 UTC

CTE tests

bb-5.5-svoj 2018-10-17 15:59:44 UTC 2018-10-17
BUG#19988193: ASSERTION `(*TABLES)->REGINFO.LOCK_TYPE >= TL_READ'

Author: Dyre Tjeldvoll
Author Date: 2015-04-30 10:56:33 UTC

BUG#19988193: ASSERTION `(*TABLES)->REGINFO.LOCK_TYPE >= TL_READ'
FAILED IN LOCK_EXTERNAL
BUG#21198646: ASSERTION FAILED: (*TABLES)->REGINFO.LOCK_TYPE >=
TL_READ FILE LOCK.CC, LINE 356

This patch addresses two related issues: Calling a procedure which
creates a view from a trigger (BUG#19988193), and creating a function
calling a procedure doing RENAME TABLE (BUG#21198646), could both, in
certain circumstances, trigger an assert.

Root cause was that prelocking of tables with lock_type==TL_IGNORE is
not supported, and so triggers an assert. TL_IGNORE is only used for
source tables in CREATE VIEW statements and the table of a RENAME TABLE
statement. It is very unusual for these statements to be part of
prelocking analysis, as both are implicit commit statements which are
not permitted in triggers and stored functions/procedures. But as the test
cases show; it is possible to have such statements contribute to the
prelocking set, but in both cases the statement is "meaningless", in
the sense that it will trigger an error during execution.

Fix: In mysql_make_view(), avoid adding the backing tables to view_ref
if view_ref->prelocking_placeholder==true and lock_type==TL_IGNORE. In
sp_head::add_used_tables_to_table_list() skip SP_TABLES which have
lock_type=TL_IGNORE.

Test: New test cases added to tablelock.test

bb-10.2-MDEV-17323 2018-10-14 17:54:52 UTC 2018-10-14
Merge branch 'MDEV1732_check_constraint_10.2_v1' of https://github.com/an3l/s...

Author: Vicențiu Ciorbaru
Author Date: 2018-10-14 17:54:52 UTC

Merge branch 'MDEV1732_check_constraint_10.2_v1' of https://github.com/an3l/server into an3l-MDEV1732_check_constraint_10.2_v1

bb-5.5-MDEV-16207 2018-10-12 18:47:22 UTC 2018-10-12
MDEV-16207: Sig 11 on RHEL7 on Azure

Author: Oleksandr Byelkin
Author Date: 2018-10-12 18:47:22 UTC

MDEV-16207: Sig 11 on RHEL7 on Azure

The problem was that Item_subselect::const_item was not checked correctly and can differ from used_tables result.
Which lead to the situation when Item_direct_view_ref pointing on subselect was constant but the subquery return
FALSE on const_item() request (which was an error).

Now both methods report the same.

10.4-vicentiu-feedback 2018-09-22 11:01:46 UTC 2018-09-22
Small change for feedback debug

Author: Vicențiu Ciorbaru
Author Date: 2018-09-22 11:01:46 UTC

Small change for feedback debug

bb-10.1-MDEV-17133 2018-09-18 20:21:18 UTC 2018-09-18
MDEV-17133 dump thread reads from a past position

Author: Andrei Elkin
Author Date: 2018-09-17 18:40:23 UTC

MDEV-17133 dump thread reads from a past position

bb-10.3-mdev-17144 2018-09-18 01:48:38 UTC 2018-09-18
MDEV-17144: Sample of spider_direct_sql cause crash

Author: Jacob Mathew
Author Date: 2018-09-18 01:39:16 UTC

MDEV-17144: Sample of spider_direct_sql cause crash

The crash occurs when the Spider node server attempts to create an error
message stating that the temporary table is not found. The function to
create the error message is called with incorrect parameters.

I fixed the crash by correcting the incorrect parameter values.

Author:
  Jacob Mathew.

Reviewer:
  Kentoku Shiba.

bb-10.4-multiple-user-binlog 2018-09-17 07:16:24 UTC 2018-09-17
multiple_user_binlog

Author: Sachin Setiya
Author Date: 2018-09-17 07:16:24 UTC

multiple_user_binlog

bb-5.5-5628 2018-09-06 07:55:06 UTC 2018-09-06
Mdev-5628 Assertion `! is_set()' fails on UPDATE on a partitioned table...

Author: Sachin Setiya
Author Date: 2018-09-06 07:43:52 UTC

Mdev-5628 Assertion `! is_set()' fails on UPDATE on a partitioned table...
with subquery (MySQL:71630)

In mysql_update after prune_partitions(thd, table, conds) we set thd->status
to ok , without considering that thd earlier might have got a error.

10.2-compatibility-debug 2018-09-05 17:20:16 UTC 2018-09-05
Added DBUG_ASSERT_AS_PRINTF to BUILD/..asan-max

Author: Monty
Author Date: 2018-09-05 17:20:16 UTC

Added DBUG_ASSERT_AS_PRINTF to BUILD/..asan-max

bb-10.4-otto 2018-09-02 19:36:14 UTC 2018-09-02
WIP: test 6

Author: Otto Kekäläinen
Author Date: 2018-09-02 19:36:14 UTC

WIP: test 6

bb-10.2-mariarocks-merge 2018-09-01 15:43:05 UTC 2018-09-01
Merge branch '10.2' of github.com:MariaDB/server into bb-10.2-mariarocks-merge

Author: Sergey Petrunia
Author Date: 2018-09-01 15:43:05 UTC

Merge branch '10.2' of github.com:MariaDB/server into bb-10.2-mariarocks-merge

bb-10.2-mariarocks-merge-pre 2018-09-01 12:10:50 UTC 2018-09-01
Trigger another BB run

Author: Sergey Petrunia
Author Date: 2018-09-01 12:10:50 UTC

Trigger another BB run

bb-10.3-monty 2018-08-31 07:47:18 UTC 2018-08-31
Fixed several issues with aria_chk

Author: Monty
Author Date: 2018-08-31 07:47:18 UTC

Fixed several issues with aria_chk

- Made output to be aligned in aria_chk -d
- Aria engine error texts are now written instead of "Undefined error"
- When running with --check --force, tables with wrong TRN's but otherwise
  correct are now zerofilled
- Fixed several bugs in check and recovery related to fulltext
- When doing recovery, store highest found TRID in aria_control_file
  Before this, the

bb-10.3-vicentiu 2018-08-25 14:03:20 UTC 2018-08-25
MDEV-14474 information_schema.check_constraints

Author: Anel Husakovic
Author Date: 2018-04-03 12:41:13 UTC

MDEV-14474 information_schema.check_constraints

Implement according to standard SQL specification 2008.
The check_constraints table is used for fetching metadata about
the constraints defined for tables in all databases.

bb-10.3-MDEV-16930 2018-08-16 11:55:36 UTC 2018-08-16
MDEV-16930: Crash when VALUES in derived table contains expressions

Author: Oleksandr Byelkin
Author Date: 2018-08-16 11:55:36 UTC

MDEV-16930: Crash when VALUES in derived table contains expressions

Give names to the value constructor columns as in SELECT-list.

bb-10.3-MDEV-16398 2018-08-09 07:04:09 UTC 2018-08-09
MDEV-16398: Spider Creates Query With Non-Existent Function

Author: Jacob Mathew
Author Date: 2018-08-09 07:04:09 UTC

MDEV-16398: Spider Creates Query With Non-Existent Function

The problem occurs because the statement generated by Spider used an
internal function name, ADD_TIME.

This problem has been corrected by the fix for bug MDEV-16878 within the
server, which enables Spider to generate the statement using the actual
SQL function name. I have made some additional changes within Spider to fix
related problems that I observed while testing.

Author:
  Jacob Mathew.

First Reviewer:
  Alexander Barkov.

Second Reviewer:
  Kentoku Shiba.

bb-5.5-MDEV-15475 2018-08-08 17:44:04 UTC 2018-08-08
MDEV-15475: Assertion `!table || (!table->read_set || bitmap_is_set(table->re...

Author: Oleksandr Byelkin
Author Date: 2018-08-06 13:50:22 UTC

MDEV-15475: Assertion `!table || (!table->read_set || bitmap_is_set(table->read_set, field_index))' failed on EXPLAIN EXTENDED with constant table and view

Print constant ISNULL fireld independent.
Fix of printing of view FRM and CREATE VIEW output

bb-10.3_cc 2018-08-05 14:15:03 UTC 2018-08-05
MDEV-16666: Partially revert "Deb: Update documentation and fix spelling errors"

Author: Otto Kekäläinen
Author Date: 2018-08-05 14:11:15 UTC

MDEV-16666: Partially revert "Deb: Update documentation and fix spelling errors"

This partially reverts commit 548ec3a088a2444881e1245a237f81cea1671969
by removing the misfixed misspellings.

bb-10.3-vicentiu-tmp-table 2018-07-30 16:21:13 UTC 2018-07-30
Fix tmp table patch

Author: Vicențiu Ciorbaru
Author Date: 2018-07-30 15:34:12 UTC

Fix tmp table patch

bb-10.1_MDEV-14014 2018-07-28 09:15:31 UTC 2018-07-28
MDEV-14014 Unittest extension to cover concurrent IO_CACHE read and write by ...

Author: Andrei Elkin
Author Date: 2018-07-28 09:15:05 UTC

MDEV-14014 Unittest extension to cover concurrent IO_CACHE read and write by the dump and user threads.

bb-10.4-MDEV-16246 2018-07-24 22:57:13 UTC 2018-07-24
MDEV-16246: insert timestamp into spider table from mysqldump gets wrong time...

Author: Jacob Mathew
Author Date: 2018-07-24 22:57:13 UTC

MDEV-16246: insert timestamp into spider table from mysqldump gets wrong time zone.

The problem occurred because the Spider node was incorrectly handling
timestamp values sent to and received from the data nodes.

The problem has been corrected as follows:
- Added logic to set and maintain the UTC time zone on the data nodes.
  To prevent timestamp ambiguity, it is necessary for the data nodes to use
  a time zone such as UTC which does not have daylight savings time.
- Removed the spider_sync_time_zone configuration variable, which did not
  solve the problem and which interfered with the solution.
- Added logic to convert to the UTC time zone all timestamp values sent to
  and received from the data nodes. This is done for both unique and
  non-unique timestamp columns. It is done for WHERE clauses, applying to
  SELECT, UPDATE and DELETE statements, and for UPDATE columns.
- Disabled Spider's use of direct update when any of the columns to update is
  a timestamp column. This is necessary to prevent false duplicate key value
  errors.
- Added a new test spider.timestamp to thoroughly test Spider's handling of
  timestamp values.

Author:
  Jacob Mathew.

Reviewer:
  Kentoku Shiba.

Merged:
  Commit 97cc9d3 on branch bb-10.3-MDEV-16246

bb-10.2-mdev16428 2018-07-13 13:23:04 UTC 2018-07-13
MDEV-16710, Issue#857: MyRocks: Incorrect behavior when miltiple statements f...

Author: Sergey Petrunia
Author Date: 2018-07-13 13:23:04 UTC

MDEV-16710, Issue#857: MyRocks: Incorrect behavior when miltiple statements fail inside a transaction

rollback_to_stmt_savepoint() calls do_rollback_to_savepoint(). This removes
the changes made by this statement, and also removes the set savepoint.

Before we start processing the next statement, we need to set the new
savepoint, so we will have something to rollback to if the next statement
fails.

Since rollback_to_stmt_savepoint always sets a new savepoint now,
m_n_savepoints is now redundant and is removed.

10.2-w-columnstore 2018-07-10 18:51:51 UTC 2018-07-10
MCOL-1532 Added accessors columnstore uses.

Author: Roman Nozdrin
Author Date: 2018-07-10 18:51:51 UTC

MCOL-1532 Added accessors columnstore uses.

bb-10.3-MDEV-16246 2018-07-09 21:25:37 UTC 2018-07-09
MDEV-16246: insert timestamp into spider table from mysqldump gets wrong time...

Author: Jacob Mathew
Author Date: 2018-07-09 21:25:37 UTC

MDEV-16246: insert timestamp into spider table from mysqldump gets wrong time zone.

The problem occurred because the Spider node was incorrectly handling
timestamp values sent to and received from the data nodes.

The problem has been corrected as follows:
- Added logic to set and maintain the UTC time zone on the data nodes.
  To prevent timestamp ambiguity, it is necessary for the data nodes to use
  a time zone such as UTC which does not have daylight savings time.
- Removed the spider_sync_time_zone configuration variable, which did not
  solve the problem and which interfered with the solution.
- Added logic to convert to the UTC time zone all timestamp values sent to
  and received from the data nodes. This is done for both unique and
  non-unique timestamp columns. It is done for WHERE clauses, applying to
  SELECT, UPDATE and DELETE statements, and for UPDATE columns.
- Disabled Spider's use of direct update when any of the columns to update is
  a timestamp column. This is necessary to prevent false duplicate key value
  errors.
- Added a new test spider.timestamp to thoroughly test Spider's handling of
  timestamp values.

Author:
  Jacob Mathew.

Reviewer:
  Kentoku Shiba.

bb-pr-774 2018-07-09 08:19:55 UTC 2018-07-09
MDEV-12914: Disable silently call of myisam

Author: Anel Husaković
Author Date: 2018-05-15 11:17:43 UTC

MDEV-12914: Disable silently call of myisam

bb-pr-689 2018-07-09 08:18:40 UTC 2018-07-09
MDEV-14474 information_schema.check_constraints

Author: Anel Husaković
Author Date: 2018-04-03 12:41:13 UTC

MDEV-14474 information_schema.check_constraints

Implement according to standard SQL specification 2008.
The check_constraints table is used for fetching metadata about
the constraints defined for tables in all databases.

There were some result files which failed after running mtr.
These files are updated with newly create record with mtr --record.

bb-10.3-findgssapi 2018-06-29 21:18:47 UTC 2018-06-29
MDEV-16596 : Windows - redo log does not work on native 4K sector disks.

Author: Vladislav Vaintroub
Author Date: 2018-06-29 21:18:47 UTC

MDEV-16596 : Windows - redo log does not work on native 4K sector disks.

Disks with native 4K sectors need 4K alignment and size for unbuffered IO
(i.e files opened with FILE_FLAG_NO_BUFFERING)

Innodb opens redo log with FILE_FLAG_NO_BUFFERING, but it does 512byte IOs
Thus, the IO fails, and Innodb is non-functional.

The fix is to check whether OS_FILE_LOG_BLOCK_SIZE is multiple of logical
sector size, and if it is not, reopen the redo log without
FILE_FLAG_NO_BUFFERING flag.

bb-10.3-MDEV-15058-2 2018-06-25 07:34:37 UTC 2018-06-25
MDEV-15058: Allocate buf_pool statically

Author: Marko Mäkelä
Author Date: 2018-02-23 20:26:26 UTC

MDEV-15058: Allocate buf_pool statically

buf_pool_t::create(): Replaces buf_pool_init().

buf_pool_t::close(): Replaces buf_pool_free().

FIXME: Do not add buf_pool_t::is_initialised()

bb-10.2-14472 2018-06-21 09:52:32 UTC 2018-06-21
MDEV-14472 Assertion `is_current_stmt_binlog_format_row()' failed...

Author: Sachin Setiya
Author Date: 2018-05-14 06:45:38 UTC

MDEV-14472 Assertion `is_current_stmt_binlog_format_row()' failed...
in THD::binlog_write_table_map

Problem:- So the issue is when the test case (mdev_14472) is run with debug
  build , Assert DBUG_ASSERT(is_current_stmt_binlog_format_row()); is fired
  in binlog_write_table_map.

Analysis:- When we lock table t1, and if t1 has some trigger which updates
  another table then all other tables are also locked. So in the case of lock
  t1(in mdev_14472 test case) we will lock t1, t2, t3 and t4. In next insert
  command (t2 insert), we call handler->check_table_row_based from
  write_locked_table_maps which updates the table handler
  check_table_binlog_row_based_done to 1 and check_table_binlog_row_based_result
  to 1 , it is set to one because this particular insert stmt is unsafe(because
  of trigger on t4). The next insert stmt(insert t3) is safe so we will write
  that in stmt format , but since we havent cleared the previous
  check_table_binlog_row_based_result so it is logged in row format while
  thd->is_current_stmt_binlog_format_row() is still 0, and this fires the
  assert. So the question is why check_table_binlog_row_based_result is not
  reseted because mark_used_tables_as_free_for_reuse skips locked tables

Solution:- We make mark_used_tables_as_free_for_reuse to reset
  check_table_binlog_row_based_result even when table is locked

bb-MDEV-15447 2018-06-18 09:00:58 UTC 2018-06-18
CTE tests (from MySQL 8.0)

Author: Larysa Sherepa
Author Date: 2018-06-18 09:00:58 UTC

CTE tests (from MySQL 8.0)

bb-10.1-vicentiu 2018-06-11 21:19:22 UTC 2018-06-11
Merge branch '10.0-galera' into bb-10.1-vicentiu

Author: Vicențiu Ciorbaru
Author Date: 2018-06-11 21:19:22 UTC

Merge branch '10.0-galera' into bb-10.1-vicentiu

bb-5.5-MDEV-15113 2018-06-11 15:50:20 UTC 2018-06-11
MDEV-15113: Hang in Aria loghandler

Author: Oleksandr Byelkin
Author Date: 2018-01-31 08:35:38 UTC

MDEV-15113: Hang in Aria loghandler

Added unregistering writers in case of log error.
Added more debugging control about adding/removing writers to the buffers.

bb-10.0-vicentiu 2018-06-11 15:49:48 UTC 2018-06-11
Merge branch '5.5' into 10.0

Author: Vicențiu Ciorbaru
Author Date: 2018-06-11 15:49:48 UTC

Merge branch '5.5' into 10.0

bb-10.3-svoj 2018-06-05 14:10:42 UTC 2018-06-05
MDEV-16371 - Fix for memory write order inversion

Author: Sergey Vojtovich
Author Date: 2018-06-05 08:54:06 UTC

MDEV-16371 - Fix for memory write order inversion

my_atomic implementation for interruptable waits.

bb-10.3-mdev-15578 2018-05-24 16:28:54 UTC 2018-05-24
MDEV-15578: MyRocks: support zstandard compression where the distro allows it

Author: Vicențiu Ciorbaru
Author Date: 2018-05-22 18:57:14 UTC

MDEV-15578: MyRocks: support zstandard compression where the distro allows it

Add libzstd-dev as a build dependency to the server and libzstd1 as a
runtime dependency for rocksdb. libzstd is practially a mandatory
compression library to ensure adequate performance for RocksDB.

bb-10.0-monty 2018-05-22 20:08:26 UTC 2018-05-22
MDEV-15308 Assertion `ha_alter_info->alter_info->drop_list.elements

Author: Monty
Author Date: 2018-05-22 20:05:01 UTC

MDEV-15308 Assertion `ha_alter_info->alter_info->drop_list.elements

Problem was that handle_if_exists_options() didn't correct
alter_info->flags when things was removed from the list.

bb-10.3-MDEV-12900 2018-05-22 00:30:39 UTC 2018-05-22
MDEV-12900: spider tests failed in buildbot with valgrind

Author: Jacob Mathew
Author Date: 2018-05-22 00:30:39 UTC

MDEV-12900: spider tests failed in buildbot with valgrind

The failures with valgrind occur as a result of Spider sometimes using the
wrong transaction for operations in background threads that send requests to
the data nodes. The use of the wrong transaction caused the networking to the
data nodes to use the wrong thread in some cases. Valgrind eventually
detects this when such a thread is destroyed before it is used to disconnect
from the data node by that wrong transaction when it is freed.

I have fixed the problem by correcting the transaction used in each of these
cases.

Author:
  Jacob Mathew.

Reviewer:
  Kentoku Shiba.

bb-10.2-MDEV-12465 2018-05-17 17:17:28 UTC 2018-05-17
MDEV-12465: Server crashes in my_scan_weight_utf8_bin upon collecting stats f...

Author: Oleksandr Byelkin
Author Date: 2018-05-17 17:17:28 UTC

MDEV-12465: Server crashes in my_scan_weight_utf8_bin upon collecting stats for RocksDB table

Do not use "only index read" in analyzing indices if there is a field which present in the index only partially.

10.3-MDEV-15855 2018-05-16 09:02:39 UTC 2018-05-16
MDEV-15855 Use MDL in FULLTEXT INDEX sync

Author: Thirunarayanan Balathandayuthapani
Author Date: 2018-05-07 11:33:47 UTC

MDEV-15855 Use MDL in FULLTEXT INDEX sync

- fts sync thread allows takes MDL lock on the table instead of
dict_operation_lock.

bb-10.2-mdev-13626 2018-05-15 05:46:51 UTC 2018-05-15
MDEV-13626 Merge InnoDB test cases from MySQL 5.7

Author: Thirunarayanan Balathandayuthapani
Author Date: 2018-05-15 05:46:51 UTC

MDEV-13626 Merge InnoDB test cases from MySQL 5.7

Imported the following test case from mysql to MariaDB

1) innodb.alter_kill
2) innodb.alter_foreign_crash
3) innodb.alter_rename_files
4) innodb.analyze_table
5) Appended the case in innodb-online-alter-gis

bb-10.3-MDEV-13134 2018-05-14 07:45:15 UTC 2018-05-14
MDEV-15874 CREATE TABLE creates extra transaction

Author: Thirunarayanan Balathandayuthapani
Author Date: 2018-05-14 07:45:15 UTC

MDEV-15874 CREATE TABLE creates extra transaction

InnoDB does not allow FOREIGN KEY constraints to exist for TEMPORARY TABLE.
InnoDB introduced a dedicated tablespace for temporary tables, and actually
stopped creating persistent metadata and data for temporary tables.

row_table_add_foreign_constraints(): Do not create a persistent
transaction.

dict_create_foreign_constraints_low(): Add the persistent transaction to
the update the foreign key relation in dictionary.

dict_create_foreign_constraints_low(): Remove a duplicated check for
partitioned tables.

bb-mdev-14472 2018-05-14 06:47:17 UTC 2018-05-14
MDEV-14472 Assertion `is_current_stmt_binlog_format_row()' failed...

Author: Sachin Setiya
Author Date: 2018-05-14 06:45:38 UTC

MDEV-14472 Assertion `is_current_stmt_binlog_format_row()' failed...
in THD::binlog_write_table_map

try 1 patch

bb-10.2-mariarocks 2018-05-11 11:50:36 UTC 2018-05-11
Tentatively enable a few myrocks tests

Author: Sergey Petrunia
Author Date: 2018-05-11 11:50:36 UTC

Tentatively enable a few myrocks tests

bb-10.3-MDEV-13024 2018-04-26 17:58:43 UTC 2018-04-26
MDEV-13024: Server crashes in my_store_ptr upon DELETE from sequence in multi...

Author: Oleksandr Byelkin
Author Date: 2018-04-26 17:58:43 UTC

MDEV-13024: Server crashes in my_store_ptr upon DELETE from sequence in multi-table format

Make operation possition() dummy for sequences (should not be used really)

bb-10.3-MDEV-7914 2018-04-04 01:41:39 UTC 2018-04-04
MDEV-7914: spider/bg.ha, spider/bg.ha_part crash server sporadically in buildbot

Author: Jacob Mathew
Author Date: 2018-04-02 22:25:08 UTC

MDEV-7914: spider/bg.ha, spider/bg.ha_part crash server sporadically in buildbot

The crash occurs when a thread that is closing its connection attempts to
access Spider transaction information when another thread has freed that memory
while processing Spider plugin deinit. This occurs because Spider does not
adjust the plugin's reference count when it sets a transaction information
pointer for the plugin.

The fix I implemented changes the way Spider sets the transaction information
pointer to use thd_set_ha_data() so that Spider's plugin reference counter is
adjusted as well.

Author:
  Jacob Mathew.

Reviewer:
  Kentoku Shiba.

vice-1 2018-04-02 21:36:01 UTC 2018-04-02
Force rebuild

Author: Vicențiu Ciorbaru
Author Date: 2018-04-02 21:36:01 UTC

Force rebuild

vicentiu-docker 2018-04-02 21:07:58 UTC 2018-04-02
Force build?

Author: Vicențiu Ciorbaru
Author Date: 2018-04-02 21:07:58 UTC

Force build?

10.3-table-on 2018-03-27 06:42:31 UTC 2018-03-27
Walking throuch query tables ON expression added.

Author: Oleksandr Byelkin
Author Date: 2018-03-27 06:42:31 UTC

Walking throuch query tables ON expression added.

10.3-fix-test-suite 2018-03-20 14:31:55 UTC 2018-03-20
Added flush tables to acl_load_mutex-5170.test

Author: Michael Widenius
Author Date: 2018-03-15 10:31:59 UTC

Added flush tables to acl_load_mutex-5170.test

This is needed as otherwise a lot of MyISAM tables may be marked
as crashed, depending on in which order tests are run

bb-10.2-compatibility-mdev15509-debug 2018-03-14 22:32:09 UTC 2018-03-14
Apply this commit to bb-10.2-compatibility-mdev15509-debug:

Author: Sergey Petrunia
Author Date: 2018-03-14 22:32:09 UTC

Apply this commit to bb-10.2-compatibility-mdev15509-debug:

commit 5511e8ed5941e3b5a7687f87a1fb4fa75815ee7b
Author: Oleksandr Byelkin <sanja@mariadb.com>
Date: Mon Mar 5 17:43:30 2018 +0100

    MDEV-15328: MariaDB 10.2.13 Crashes upon CALL PROCEDURE PARAM LAST_INSERT_ID ()

    There is not current SELECT during assigning SP parameters, do not use it if current_select is empty.

bb-10.2-ext 2018-03-13 10:22:28 UTC 2018-03-13
Merge pull request #652 from halfspawn/bb-10.2-ext

Author: Alexander Barkov
Author Date: 2018-03-13 10:22:28 UTC

Merge pull request #652 from halfspawn/bb-10.2-ext

MDEV-10574 / SUBSTR - sql_mode=Oracle: return null instead of empty string

bb-10.1-elenst 2018-03-11 21:49:57 UTC 2018-03-11
MDEV-13968 sst fails with "WSREP_SST_OPT_PORT: readonly variable"

Author: Sergei Golubchik
Author Date: 2017-10-24 18:59:54 UTC

MDEV-13968 sst fails with "WSREP_SST_OPT_PORT: readonly variable"

followup for 4c2c057d404

fix broken script (set -u)

bb-10.2-mdev15245 2018-03-08 10:43:55 UTC 2018-03-08
MDEV-15245: Assertion `false' failed in myrocks::ha_rocksdb::position

Author: Sergey Petrunia
Author Date: 2018-03-08 10:43:55 UTC

MDEV-15245: Assertion `false' failed in myrocks::ha_rocksdb::position

Don't call handler->position() if the last call to read a row did
not succeed.

201300 of 403 results

Other repositories

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