Commit graph

6 commits

Author SHA1 Message Date
Thirunarayanan Balathandayuthapani
dcb59373d5 - Fixing innodb.purge_secondary test case failure 2018-03-26 17:36:41 +05:30
Thirunarayanan Balathandayuthapani
7003067a09 - Fixing innodb.purge_secondary test case. 2018-03-23 13:27:33 +05:30
Thirunarayanan Balathandayuthapani
b0c43d0c38 MDEV-15384 buf_flush_LRU_list_batch() always reports n->flushed=0, n->evicted=0
MDEV-14545 Backup fails due to MLOG_INDEX_LOAD record

- Changed the unsupported_redo test case to avoid checkpoint
- Inserting more rows in purge_secondary test case to display evict monitor.
2018-03-16 12:30:36 +05:30
Thirunarayanan Balathandayuthapani
8c8028ca68 MDEV-15384 buf_flush_LRU_list_batch() always reports n->flushed=0, n->evicted=0
- Work around for MDEV-13942: Drop spatial index to avoid possible hang
2018-03-15 19:15:09 +05:30
Thirunarayanan Balathandayuthapani
76ae6e725d MDEV-15384 buf_flush_LRU_list_batch() always reports n->flushed=0, n->evicted=0
- buf_flush_LRU_list_batch() initializes the count to zero and updates them
correctly.
2018-03-13 15:25:38 +05:30
Marko Mäkelä
d361401bc2 Merge 10.1 into 10.2, with some MDEV-14799 fixups
trx_undo_page_report_modify(): For SPATIAL INDEX, keep logging
updated off-page columns twice, so that
the minimum bounding rectangle (MBR) will be logged.
Avoiding the redundant logging would require larger changes
to the undo log format.

row_build_index_entry_low(): Handle SPATIAL_UNKNOWN more robustly,
by refusing to purge the record from the spatial index.
We can get this code when processing old undo log from 10.2.10 or
10.2.11 (the releases affected by MDEV-14799, which was a regression
from MDEV-14051).
2018-01-03 11:56:24 +02:00