| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The assert was caused due to incorrect handling of --tc-heuristic-recover=ROLLBACK
and --innodb-read-only=1 option combination. Innodb attempted
rollback of a prepared transaction having no right to do so because of
the latter option.
Fixed with making Innodb to respect the read-only flag by
innobase_{commit,rollback}_by_xid (Marko's contribution).
LOCK_log mutex lock/unlock had to be added to cover MDEV-1438 "child" issue.
The measure is confirmed by mysql sources as well.
For testing of the conflicting option combination, mysql-test-run is
made to export a new $MYSQLD_LAST_CMD. It holds the very last value
generated by mtr.mysqld_start(). Even though the options have been
also always stored in $mysqld->{'started_opts'} there were no access
to them beyond the automatic server restart by mtr through the expect
file interface.
Effectively therefore $MYSQLD_LAST_CMD represents a more general interface to
$mysqld->{'started_opts'} which can be used in wider scopes including
server launch with incompatible options.
Notice another existing method to restart the server with incompatible
options relying on $MYSQLD_CMD is is aware of $mysqld->{'started_opts'} (the actual
options that the server is launched by mtr). In order to use this
method they would have to be provided manually.
Note, at merging to 10.2 an added search++ macro should be renamed
"back" to normal. It's being backparted to 10.0 "temporarily".
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem was that if column was created in alter table when
it was refered again it was not tried to find from list
of current columns.
mysql_prepare_alter_table:
There is two cases
(1) If alter table adds a new column and then later alter
changes the field definition, there was no check from
list of new columns, instead an incorrect error was given.
(2) If alter table adds a new column and then later alter
changes the default, there was no check from list of
new columns, instead an incorrect error was given.
|
| |
|
|
| |
also fix innodb
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
Revert the following change, because Memcached is not present
in MariaDB Server. We had better avoid adding dead code.
commit d9bc5e03d788b958ce8c76e157239953db60adb2
Author: Aakanksha Verma <aakanksha.verma@oracle.com>
Date: Thu May 18 14:31:01 2017 +0530
Bug #24605783 MYSQL GOT SIGNAL 6 ASSERTION FAILURE
|
| | |
|
| |\
| |
| |
| | |
Includes Percona XtraDB and TokuDB 5.6.36-82.1
|
| | |
| |
| |
| |
| | |
We need to pull rpl config files from MySQL before these tests can be
run.
|
| | |\ |
|
| | | | |
|
| | | | |
|
| | |\ \
| | |/ |
|
| | | | |
|
| | |\ \ |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| |/ / /
| | |
| | |
| | |
| | |
| | | |
Problem was a memory overflow in MRR
Reviewed by Sergei Petruna. Testcase by Elena
|
| | | |
| | |
| | |
| | |
| | | |
Squash all connect/10.0's commits into one and keep only
changes from storage/connect directory.
|
| | | |
| | |
| | |
| | | |
Fix storage_engine test results
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Diagnostics_area::message() ; connect.xml* tests fail in buildbot
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
remove ~15 years old print_lock_error() function, use
handler::print_error() instead
Backport from 10.1
|
| | | |
| | |
| | |
| | | |
Test fixed for IA64.
|
| | | |
| | |
| | |
| | | |
Calculation of the polygon's centroid fixed.
|
| |\ \ \ |
|
| | | | | |
|
| |\ \ \ \ |
|
| | | | | | |
|
| | | | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Following merge from 5.6.36, this merge also rejects changes that
collided with the rejection of 6ca4f693c1ce472e2b1bf7392607c2d1124b4293.
We initially rejected 6ca4f693c1ce472e2b1bf7392607c2d1124b4293 because
it was introducing a new storage engine API method.
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
One query was removed due to inconsistent behaviour with subquery cache
enabled vs disabled. MDEV-13399 has been created to track this change
and fix.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
slave_skip_counter must not be reset to 0 during purge_relay_logs. See
MDEV-4937 as to when this change happened.
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| |\ \ \ \ \ \ |
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Problem
rpl.rpl_mdev-11092 fails in buildbot because after starting slave in
wait_for_slave_sql_error_and_skip.inc slave is started but there may be
chances that we have not skipped the last error and Last_SQL_Errno is
still not zero untill the end of rpl_end.inc , which will compare
Last_SQL_Errno to 0. So in this this case rpl_mdev-11092 fails.
Solution
After starting slave in wait_for_slave_sql_error_and_skip.inc we will wait for
Last_SQL_Errno to become 0.
|
| | |\ \ \ \ \ \ |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Inspired by: https://github.com/devexp-db/mariadb/blob/f27/mariadb-covscan-stroverflow.patch
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Signed-off-by: Daniel Black <daniel.black@au.ibm.com>
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
test case
|
