summaryrefslogtreecommitdiff
path: root/storage/innobase
Commit message (Collapse)AuthorAgeFilesLines
* Merge remote-tracking branch 'origin/5.5-galera' into 10.0-galeraJan Lindström2018-05-072-39/+44
|\
| * Merge tag 'mariadb-5.5.60' into 5.5-galeraJan Lindström2018-04-2422-186/+132
| |\
| | * BUG#27216817: INNODB: FAILING ASSERTION: ↵Sergei Golubchik2018-04-192-0/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | PREBUILT->TABLE->N_MYSQL_HANDLES_OPENED == 1 disable online alter add primary key for innodb, if the table is opened/locked more than once in the current connection (see assert in ha_innobase::add_index())
| | * Merge branch 'mysql/5.5' into 5.5Sergei Golubchik2018-04-191-1/+3
| | |\
| | | * (no commit message)Karthik Kamath2018-02-141-1/+3
| | | |
| | * | honor alignment rules and xtradb tooEugene Kosov2018-03-201-1/+4
| | | |
| | * | MDEV-15030 Add ASAN instrumentationEugene Kosov2018-03-191-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Learn both valgrind and asan to catch this bug: mem_heap_t* heap = mem_heap_create(1024); byte* p = reinterpret_cast<byte*>(heap) + sizeof(mem_heap_t); *p = 123; Overflows of the last allocation in a block will be catched too. mem_heap_create_block(): poison newly allocated memory
| * | | MDEV-8743: O_CLOEXEC on innodb/xtradb temp filesDaniel Black2018-03-021-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Thread 1 "mysqld" hit Breakpoint 1, innobase_mysql_tmpfile () at /home/dan/repos/mariadb-server-5.5/storage/xtradb/handler/ha_innodb.cc:1639 1639 os_event_wait(srv_allow_writes_event); (gdb) p fd $2 = 7 (gdb) n 1682 fd2 = fcntl(fd, F_DUPFD_CLOEXEC, 0); (gdb) 1687 if (fd2 < 0) { (gdb) p fd2 $3 = 8 cat /proc/20448/fdinfo/{7,8} 2051972 0 -r-------- 1 dan dan 0 Mar 2 12:04 fdinfo/7 pos: 0 flags: 0100002 mnt_id: 82 2051973 0 -r-------- 1 dan dan 0 Mar 2 12:04 fdinfo/8 pos: 0 flags: 02100002 mnt_id: 82 So fd 8 has 02000000 hence CLOEXEC
| * | | MDEV-8743: use O_CLOEXEC (innodb/xtradb)Daniel Black2018-03-021-3/+3
| | | |
| * | | Merge tag 'mariadb-5.5.59' into 5.5-galeraJan Lindström2018-01-1915-49/+57
| |\ \ \
| * | | | MW-402 cascading FK issues (5.5 version)sjaakola2017-10-192-7/+6
| | | | | | | | | | | | | | | | | | | | | | | | | copied the fix for MW-402 from mysql-wsrep-bugs/MW-402-5.6 (note, this is not git merge)
| * | | | Merge tag 'mariadb-5.5.58' into 5.5-galeraJan Lindström2017-10-197-13/+16
| |\ \ \ \
| * | | | | Remove unneeded code.mariadb-galera-5.5.57Jan Lindström2017-07-241-18/+0
| | | | | |
| * | | | | Apply galera patches to XtraDB storage engine and remove one debug output.Jan Lindström2017-07-241-2/+0
| | | | | |
| * | | | | Fix regression on galera.partition test case by commenting the problematic ↵Jan Lindström2017-07-241-3/+12
| | | | | | | | | | | | | | | | | | | | | | | | condition.
| * | | | | MDEV-10379: Failing assertion: xid_seqno > trx_sys_cur_xid_seqnoJan Lindström2017-07-241-20/+0
| | | | | | | | | | | | | | | | | | | | | | | | Remove too strict debug assertion.
| * | | | | MW-369 FK fixessjaakola2017-07-201-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Skipping wsrep extra FK check for applier and replayer Signed-off-by: Jan Lindström <jan.lindstrom@mariadb.com>
| * | | | | MW-322 Fix compilation error with debug buildTeemu Ollakka2017-07-201-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | Signed-off-by: Jan Lindström <jan.lindstrom@mariadb.com>
| * | | | | Fix merge error and compiler warning.Jan Lindström2017-07-201-8/+5
| | | | | |
| * | | | | MW-369 - merged fix for FK issue from 5.6-v25 branchsjaakola2017-07-201-8/+13
| | | | | | | | | | | | | | | | | | | | | | | | Signed-off-by: Jan Lindström <jan.lindstrom@mariadb.com>
| * | | | | MW-322 - CTAS fix merged to 5.5-v25 branchsjaakola2017-07-201-27/+35
| | | | | | | | | | | | | | | | | | | | | | | | Signed-off-by: Jan Lindström <jan.lindstrom@mariadb.com>
| * | | | | Merge tag 'mariadb-5.5.57' into 5.5-galeraJan Lindström2017-07-201-6/+0
| |\ \ \ \ \
| * \ \ \ \ \ Merge tag 'mariadb-5.5.55' into bb-5.5-sachin-mergeSachin Setiya2017-04-1812-177/+159
| |\ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | Signed-off-by: Sachin Setiya <sachin.setiya@mariadb.com>
| * | | | | | | Fix compiler error on gcc 6.x and most of the compiler warnings.Jan Lindström2017-04-0528-95/+18
| | | | | | | |
| * | | | | | | Merge tag 'mariadb-5.5.54' into 5.5-galeramariadb-galera-5.5.54Nirbhay Choubey2016-12-271-11/+42
| |\ \ \ \ \ \ \
| * | | | | | | | MDEV-10544: Galera: Failing assertion: (lock->trx)->wait_lock == lockJan Lindström2016-11-091-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In Galera case this assertion is too strict as conflicting lock could be same as lock here.
| * | | | | | | | Merge tag 'mariadb-5.5.51' into 5.5-galeraNirbhay Choubey2016-08-109-25/+54
| |\ \ \ \ \ \ \ \
| * \ \ \ \ \ \ \ \ Merge tag 'mariadb-5.5.50' into 5.5-galeramariadb-galera-5.5.50Nirbhay Choubey2016-06-232-1/+74
| |\ \ \ \ \ \ \ \ \
| * \ \ \ \ \ \ \ \ \ Merge tag 'mariadb-5.5.49' into 5.5-galeraNirbhay Choubey2016-04-253-27/+27
| |\ \ \ \ \ \ \ \ \ \
| * \ \ \ \ \ \ \ \ \ \ Merge tag 'mariadb-5.5.48' into 5.5-galeraNirbhay Choubey2016-02-136-26/+83
| |\ \ \ \ \ \ \ \ \ \ \
| * | | | | | | | | | | | Refs codership/mysql-wsrep#221sjaakola2016-02-101-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - disabling certain IB atomic builtins, which caused complete hangs
| * | | | | | | | | | | | Merge tag 'mariadb-5.5.47' into 5.5-galeraNirbhay Choubey2015-12-104-77/+87
| |\ \ \ \ \ \ \ \ \ \ \ \
| * \ \ \ \ \ \ \ \ \ \ \ \ Merge tag 'mariadb-5.5.46' into 5.5-galeraNirbhay Choubey2015-10-137-68/+165
| |\ \ \ \ \ \ \ \ \ \ \ \ \
* | | | | | | | | | | | | | | MDEV-8743: where O_CLOEXEC is available, use for innodb buf_dumpDaniel Black2018-03-151-1/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As this is the only moderately critical fopened for writing file, create an alternate path to use open and fdopen for non-glibc platforms that support O_CLOEXEC (BSDs). Tested on Linux (by modifing the GLIBC defination) to take this alternate path: $ cd /proc/23874 $ more fdinfo/71 pos: 0 flags: 02100001 mnt_id: 24 $ ls -la fd/71 l-wx------. 1 dan dan 64 Mar 14 13:30 fd/71 -> /dev/shm/var_auto_i7rl/mysqld.1/data/ib_buffer_pool.incomplete
* | | | | | | | | | | | | | | MDEV-8743: ib_logfile0 Use O_CLOEXEC so galera SST scripts don't get fdDaniel Black2018-03-021-1/+1
| | | | | | | | | | | | | | |
* | | | | | | | | | | | | | | Merge tag 'mariadb-10.0.34' into 10.0-galeramariadb-galera-10.0.34Jan Lindström2018-02-0150-513/+421
|\ \ \ \ \ \ \ \ \ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: storage/innobase/lock/lock0lock.cc storage/xtradb/lock/lock0lock.cc storage/xtradb/lock/lock0wait.cc support-files/mysql.server.sh
| * | | | | | | | | | | | | | | Remove ut_win_init_time from innodbVicențiu Ciorbaru2018-01-253-32/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The patch was brought in from 5.6.39 merge and we don't need it in MariaDB
| * | | | | | | | | | | | | | | Fix innodb compilation failure on WindowsVicențiu Ciorbaru2018-01-253-21/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We don't need to print an error when loading kernel32.dll. If we can't load it we'll automatically crash. Reviewed by wlad@mariadb.com
| * | | | | | | | | | | | | | | Merge branch 'merge-innodb-5.6' into 10.0Vicențiu Ciorbaru2018-01-246-11/+72
| |\ \ \ \ \ \ \ \ \ \ \ \ \ \ \
| | * | | | | | | | | | | | | | | 5.6.39Vicențiu Ciorbaru2018-01-2310-50/+130
| | | | | | | | | | | | | | | | |
| * | | | | | | | | | | | | | | | Fix Innodb ASAN error on initVicențiu Ciorbaru2018-01-243-3/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Backport 7c03edf2fe66855a8ce8f2575c3aaf66af975377 from xtradb to innodb
| * | | | | | | | | | | | | | | | Merge remote-tracking branch '5.5' into 10.0Vicențiu Ciorbaru2018-01-2425-208/+140
| |\ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ | | | |_|_|_|_|_|_|_|_|_|_|_|_|/ / | | |/| | | | | | | | | | | | | |
| | * | | | | | | | | | | | | | | Add ASAN instrumentation (and more strict Valgrind) to InnoDBMarko Mäkelä2018-01-236-26/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | mem_heap_free_heap_top(): Remove UNIV_MEM_ASSERT_W() and unpoison the memory region first, because part of it may have been poisoned by an earlier mem_heap_free_top() call. Poison the address range at the end. mem_heap_block_free(): Poison the address range at the end. UNIV_MEM_ASSERT_AND_ALLOC(): Replace with UNIV_MEM_ALLOC(). We want to keep the address ranges poisoned (unaccessible) as long as possible. UNIV_MEM_ASSERT_AND_FREE(): Replace with UNIV_MEM_FREE().
| | * | | | | | | | | | | | | | | Silence -Wimplicit-fallthroughMarko Mäkelä2018-01-231-0/+1
| | | | | | | | | | | | | | | | |
| | * | | | | | | | | | | | | | | improve ASAN instrumentation: InnoDB/XtraDBSergei Golubchik2018-01-221-7/+10
| | | | | | | | | | | | | | | | |
| | * | | | | | | | | | | | | | | MDEV-7049 MySQL#74585 - InnoDB: Failing assertion: *mbmaxlen < 5 in file ↵Marko Mäkelä2018-01-2214-153/+87
| | | |_|_|_|_|_|_|_|_|_|_|_|/ / | | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ha_innodb.cc line 1904 InnoDB limited the maximum number of bytes per character to 4. But, the filename character set that was introduced in MySQL 5.1 uses up to 5 bytes per character. To allow InnoDB tables to be created with wider characters, let us split the mbminmaxlen fields into mbminlen, mbmaxlen, and increase the limit to 7 bytes per character. This will increase the payload size of dtype_t and dict_col_t by one bit. The storage size will be unchanged (54 bits and 77 bits will use the same number of bytes as the previous sizes 53 and 76 bits).
| | * | | | | | | | | | | | | | Merge branch 'mysql/5.5' into 5.5Sergei Golubchik2018-01-181-1/+1
| | |\ \ \ \ \ \ \ \ \ \ \ \ \ \ | | | | |_|_|_|_|_|_|_|_|_|_|_|/ | | | |/| | | | | | | | | | | |
| | | * | | | | | | | | | | | | Bug #24296076 INNODB REPORTS WARNING WHILE INNODB_UNDO_LOG_TRUNCATE IS ENABLEDAditya A2017-11-171-7/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | PROBLEM ------- This warning message is printed when trx_sys->rseg_history_len is greater than some arbitrary magic number (2000000). By seeing the reproducing scenario where we keep a read view open and do a lot of transactions on table which increases the hitsory length it is entirely possible that trx_sys->rseg_history_len can exceed 2000000. So this is not a bug due to corruption of history length.The warning message was just added to test some scenario and not removed. FIX --- 1.Print this warning message only for debug versions. 2.Modified the warning message with more detailed information. 3.Don't crash even in debug versions. [#rb 17929 Reviewed by jimmy and satya]
| * | | | | | | | | | | | | | | MDEV-12173 "Error: trying to do an operation on a dropped tablespace"Marko Mäkelä2018-01-224-22/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | InnoDB is issuing a 'noise' message that is not a sign of abnormal operation. The only issuers of it are the debug function lock_rec_block_validate() and the change buffer merge. While the error should ideally never occur in transactional locking, we happen to know that DISCARD TABLESPACE and TRUNCATE TABLE and possibly DROP TABLE are breaking InnoDB table locks. When it comes to the change buffer merge, the message simply is useless noise. We know perfectly well that a tablespace can be dropped while a change buffer merge is pending. And the code is prepared to handle that, which is demonstrated by the fact that whenever the message was issued, InnoDB did not crash. fil_inc_pending_ops(): Remove the parameter print_err.
| * | | | | | | | | | | | | | | Make row_mysql_table_id_reassign() staticMarko Mäkelä2018-01-182-14/+2
| | | | | | | | | | | | | | | |
View Lorry Controller Status