[MDEV-6113] merge 5.7 innodb Created: 2014-04-15  Updated: 2019-09-11  Resolved: 2016-09-19

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Fix Version/s: 10.2.2

Type: Task Priority: Major
Reporter: Sergei Golubchik Assignee: Jan Lindström (Inactive)
Resolution: Fixed Votes: 10
Labels: None

Attachments: File i5714.diff     File i579.diff    
Issue Links:
Blocks
blocks MDEV-6697 Improve foreign keys warnings/errors Closed
blocks MDEV-9820 global option to enable page compress... Closed
blocks MDEV-11000 Compatibility issues between 10.2 and... Closed
PartOf
includes MDEV-4697 UPDATE_TIME field for XtraDB / InnoDB Closed
includes MDEV-6614 Merge InnoDB: fix index->lock content... Closed
includes MDEV-7455 Speed up crash recovery Closed
includes MDEV-8923 [PATCH] port innodb_buffer_pool_dump_... Closed
includes MDEV-9311 Make innodb_buffer_pool_size dynamic Closed
includes MDEV-9330 Make 5.7 InnoDB compile with MariaDB ... Closed
includes MDEV-9476 Fix merge errors on merge 5.7 InnoDB ... Closed
Relates
relates to MDEV-15223 Document that InnoDB's native partiti... Closed
relates to MDEV-19294 Remove TABLESPACE-related commands Closed
relates to MDEV-20562 btr_cur_open_at_rnd_pos() fails to re... Closed
relates to MDEV-10813 Clean-up InnoDB atomics, memory barri... Closed
relates to MDEV-12309 Test migration from MySQL 5.7 with na... Stalled
Sprint: 10.2.0-1, 10.2.0-8, 10.2.0-9, 5.5.51 & 10.2.2, 10.1.17-1, 10.2.2-1, 10.2.2-2, 10.2.2-3, 10.2.2-4

 Description   

merge 5.7 innodb and xtradb, preferably both at the same time.

 Comments   
Comment by Geoff Montee (Inactive) [ 2015-04-13 ]

Will this merge include online truncation of InnoDB undo tablespaces? Would that be included in 10.1 or 10.2?

http://mysqlserverteam.com/online-truncate-of-innodb-undo-tablespaces/

Comment by Sergey Vojtovich [ 2015-11-13 ]

Please note that 5.7.9 InnoDB is unstable on Power8. We'll likely have to fix it again.

Comment by Sergei Golubchik [ 2015-11-17 ]

Question: what to do with Boost.Geometry

Comment by Daniel Black [ 2016-04-21 ]

svoj, I've started to look for them. https://github.com/linux-on-ibm-power/mysql-server/tree/5.7-POWER_FIXES has the ones I've need to make 5.7 stable though honestly most are ones you've found already and fixed.

http://bugs.mysql.com/bug.php?id=79378 might be one that applies though I haven't reproduced it on MariaDB yet.

Comment by Sergey Vojtovich [ 2016-04-21 ]

danblack, thanks for looking for them. Let's hope these fixes will be accepted by mysql.

Comment by Geoff Montee (Inactive) [ 2016-07-08 ]

Will this merge include the fix for this upstream bug?

https://jira.mariadb.org/browse/MDEV-4697

Comment by Michiel Hazelhof [ 2016-08-03 ]

There seem to be quite a few improvements noted in: https://blogs.oracle.com/mysqlinnodb/entry/innodb_5_7_performance_improvements
Are all these planned to be included?

Comment by Jan Lindström (Inactive) [ 2016-09-09 ]

Attached server changes I have done while merged 5.7.9 and 5.7.14.

Comment by Sergei Golubchik [ 2016-09-14 ]

GieltjE, most will be. All changes inside InnoDB will be included. If there will be optimizations that don't work without corresponding server changes — they might not work (we will merge some correspondent server changes, but not all).

Comment by Geoff Montee (Inactive) [ 2016-12-07 ]

Did this merge include "ALTER TABLE ...

{DISCARD|IMPORT}

PARTITION" for InnoDB tables?

https://jira.mariadb.org/browse/MDEV-10568

Generated at Thu Feb 08 07:09:27 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.