Darshan M N 16ed1f9c31 BUG#25053705 INVALID I/O ON TABLE AFTER TRUNCATE ... Issue: ====== The issue is that if a fts index is present in a table the space size is incorrectly calculated in the case of truncate which results in a invalid read. Fix: ==== Have a different space size calculation in truncate if fts indexes are present. RB:14755 Reviewed-by: Shaohua Wang <shaohua.wang@oracle.com>		2017-04-26 23:03:30 +03:00
..
buf0buddy.cc	MDEV-12271 Port MySQL 8.0 Bug#23150562 REMOVE UNIV_MUST_NOT_INLINE AND UNIV_NONINL	2017-03-17 12:42:07 +02:00
buf0buf.cc	Bug#25048573: STD::MAP INSTANTIATIONS CAUSE STATIC ASSERT FAILURES ON FREEBSD 11	2017-04-26 23:03:29 +03:00
buf0checksum.cc	Merge InnoDB 5.7 from mysql-5.7.14.	2016-09-08 15:49:03 +03:00
buf0dblwr.cc	Minor cleanup	2017-04-26 23:03:28 +03:00
buf0dump.cc	MDEV-11840 InnoDB: "Cannot open <ib_buffer_pool file>" should not be an error	2017-04-05 10:16:11 +03:00
buf0flu.cc	MDEV-12545 Reduce the amount of fil_space_t lookups	2017-04-21 18:12:10 +03:00
buf0lru.cc	Bug#24346574 PAGE CLEANER THREAD, ASSERT BLOCK->N_POINTERS == 0	2017-04-26 23:03:27 +03:00
buf0mtflu.cc	MDEV-11707: Fix incorrect memset() for structures containing	2017-02-06 15:40:17 +02:00
buf0rea.cc	BUG#25053705 INVALID I/O ON TABLE AFTER TRUNCATE	2017-04-26 23:03:30 +03:00