- 10 Nov, 2016 1 commit
-
-
Jan Lindström authored
Code calling mtflush threads to exit was too late.
-
- 09 Nov, 2016 2 commits
-
-
Jan Lindström authored
When we enter here wait_lock could be already gone i.e. NULL, that should be allowed.
-
Jan Lindström authored
This is not a fix, this is instrumentation to find the bug.
-
- 08 Nov, 2016 3 commits
-
-
Alexander Barkov authored
-
Hartmut Holzgraefe authored
-
Sergei Golubchik authored
-
- 07 Nov, 2016 12 commits
-
-
Nirbhay Choubey authored
-
Nirbhay Choubey authored
During total-order replication, Query_log_event's checksum_alg should be explicitly set to the current binlog_checksum as it is not set for DML queries. Note: wsrep_replicate_myisam enables replication of DMLs on MyISAM tables using TOI.
-
Francisco Biete authored
See https://github.com/MariaDB/server/pull/235 I submit this code under the BSD-new license.
-
Nirbhay Choubey authored
-
Nirbhay Choubey authored
thd->variables.option_bits need to be restored after plugin_thdvar_init() during post initialization of wsrep threads.
-
Nirbhay Choubey authored
Postfix: The pre-initialization of wsrep threads is not needed for mysqldump sst method.
-
Nirbhay Choubey authored
When a BF thread attempts to abort a victim thread's transaction, the victim thread is not locked and thus its not safe to rely on its data structures like htons registered for the trx. So, instead of getting the registered htons from victim, innodb's hton can be looked up directly from installed_htons[] and used to abort the transaction. (Same technique is used in older versions)
-
Nirbhay Choubey authored
Perform a post initialization of plugin-related variables of wsrep threads after their global counterparts have been initialized.
-
Nirbhay Choubey authored
The crash is caused due to a race condition where wsrep startup threads invoke ha_maria::implicit_commit() method while maria_hton is partially initialized. The fix is to skip this method if plugins are uninitialized.
-
Sergey Vojtovich authored
-
Jan Lindström authored
MDEV-9820 Added server variable compression_default, which if 1/ON sets compres…
-
Elena Stepanova authored
-
- 06 Nov, 2016 1 commit
-
-
Elena Stepanova authored
Do not include the suite into the default list until the tests are stable
-
- 04 Nov, 2016 2 commits
-
-
Vladislav Vaintroub authored
MDEV-11195: Correct enablement of NUMA in innodb/xtradb
-
Rasmus Johansson authored
Added server variable compression_default, which if 1/ON sets compression on for all new InnoDB/XtraDB tables by default by setting PAGE_COMPRESSED=1
-
- 03 Nov, 2016 7 commits
-
-
Kristian Nielsen authored
The .rdiff applied ok locally with my copy of patch, but failed with "misordered hunks" on a test host. Maybe that host has a more strict version of `patch`.
-
Oleksandr Byelkin authored
-
Sergey Vojtovich authored
With "WL#6047 - Do not allocate trx id for read-only transactions" m_prebuilt->trx->id is always 0 for read-only transactions. This makes it useless as an index for fuzzy counters. Use server thread id instead similarly to MySQL.
-
Kristian Nielsen authored
Conflicts: sql/share/errmsg-utf8.txt
-
Kristian Nielsen authored
BINLOG statement output by mysqlbinlog actually has the base64 of the non-compressed event. So remove my previous incorrect review change, which allowed compressed event types for BINLOG statement. Also add a couple test cases for this, running mysqlbinlog | mysql.
-
Sergey Vojtovich authored
for InnoDB tables" Don't use thr_lock.c locks for InnoDB tables. Below is list of changes that were needed to implement this: - HANDLER OPEN acquireis MDL_SHARED_READ instead of MDL_SHARED - HANDLER READ calls external_lock() even if SE is not going to be locked by THR_LOCK - InnoDB lock wait timeouts are now honored which are much shorter by default than server lock wait timeouts (1 year vs 50 seconds) - with @@autocommit= 1 LOCK TABLES disables autocommit implicitely, though user still sees @@autocommt= 1 - the above starts implicit transaction - transactions started by LOCK TABLES are now rolled back on disconnect (previously everything was committed due to autocommit) - transactions started by LOCK TABLES are now rolled back by ROLLBACK (previously everything was committed due to autocommit) - it is now impossible to change BINLOG_FORMAT under LOCK TABLES (at least to statement) due to running transaction - LOCK TABLES WRITE is additionally handled by MDL - ...in contrast LOCK TABLES READ protection against DML is pure InnoDB - combining transactional and non-transactional tables under LOCK TABLES may cause rolled back changes in transactional table and "committed" changes in non-transactional table - user may disable innodb_table_locks, which will cause LOCK TABLES to be noop basically Removed tests for BUG#45143 and BUG#55930 which cover InnoDB + THR_LOCK. To operate properly these tests require code flow to go through THR_LOCK debug sync points, which is not the case after this patch. These tests are removed by WL#6671 as well. An alternative is to port them to different storage engine.
-
Kristian Nielsen authored
.result file update for --embedded test run.
-
- 02 Nov, 2016 4 commits
-
-
Oleksandr Byelkin authored
(+ default values)
-
Darshan M N authored
Issue: ====== Currently the approach we take to find the chunk corresponding to a given pointer uses srv_buf_pool_chunk_unit based on the assumption that srv_buf_pool_chunk_unit is the total size of all pages in a buffer pool chunk. We first step back by srv_buf_pool_chunk_unit bytes and use std::map::upper_bound() to find the first chunk in the map whose key >= the resulting pointer. However, the real size of a chunk (and thus, the total size of its pages) may differ from the value configured with innodb_buffer_pool_chunk_size due to rounding up to the OS page size. So, in some cases the above logic gives us the wrong chunk. Fix: ==== We find out the chunk corresponding to the give pointer without using srv_buf_pool_chunk_unit. This is done by using std::map::upper_bound() to find the next chunk in the map which appears right after the pointer and decrementing the iterator, which would give us the chunk the pointer belongs to. Contribution by Alexey Kopytov. RB: 13347 Reviewed-by: Debarun Banerjee <debarun.banerjee@oracle.com>
-
Sergey Vojtovich authored
Let \H issue host name when connected to localhost via TCP/IP.
-
Daniel Black authored
Move common parts of {innodb,xtradb}/CmakeLists.txt to the macro.
-
- 01 Nov, 2016 2 commits
-
-
Otto Kekäläinen authored
MDEV-6284 - Partially merge downstream Debian/Ubuntu packaging into upstream MariaDB
-
Daniel Black authored
No -DHAVE_LIBNUMA=1 was passed to the source compile (and the global include/my_config.h wasn't used). This also is Linux only so corrected the cmake macro. Fixed indenting in cmake macro. Removed NUMA defination from include/my_config.h as its only in the storage engine. Thanks Elena Stepanova and Vladislav Vaintroub for the detailed list of bugs/questions. Signed-off-by: Daniel Black <daniel.black@au.ibm.com>
-
- 31 Oct, 2016 2 commits
-
-
Sergey Vojtovich authored
Clean-up nolock.h: it doesn't serve any purpose anymore. Appropriate code moved to x86-gcc.h and my_atomic.h. If gcc sync bultins were detected, we want to make use of them independently of __GNUC__ definition. E.g. XLC simulates those, but doesn't define __GNUC__. HS/Spider: According to AIX manual alloca() returns char*, which cannot be casted to any type with static_cast. Use explicit cast instead. MDL: Removed namemangling pragma, which didn't let MariaDB build with XLC. WSREP: _int64 seem to be conflicting name with XLC, replaced with _integer64. CONNECT: RTLD_NOLOAD is GNU extention. Removed rather meaningless check if library is loaded. Multiple dlopen()'s of the same library are permitted, and it never gets closed anyway. Except for error, which was a bug: it may close library, which can still be referenced by other subsystems. InnoDB: __ppc_get_timebase() is GNU extention. Only use it when __GLIBC__ is defined. Based on contribution by flynn1973.
-
Kristian Nielsen authored
-
- 29 Oct, 2016 3 commits
-
-
vinchen authored
1.Avoid overflowing buffers in case of corrupt events 2.Check the compressed algorithm.
-
Otto Kekäläinen authored
The control file contents must be correct from the start and cannot be modified at build time by CMake. Also all static Debian package analyzers will fail to see all manipulations by CMake later on. It is best to do all manipulations like these in autobake-deb.sh.
-
Otto Kekäläinen authored
On systems with unix socket authentication root could run these without any special maintenance accounts.
-
- 28 Oct, 2016 1 commit
-
-
Otto Kekäläinen authored
-