Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-18338

Merge new release of InnoDB 5.7.25 to 10.2

    Details

      Description

      MySQL 5.7.25 includes the following InnoDB changes:

      Applicable to MariaDB 10.2

      Bug #22990029 GCOLS: INCORRECT BEHAVIOR AFTER DATA INSERTED WITH IGNORE KEYWORD
      This is a crash with DML operations on a table that has indexed virtual columns (MDEV-5800). MariaDB is affected.

      Applicable to earlier InnoDB versions than MySQL 5.7 or MariaDB 10.2

      Bug#28867993: POSSIBLE ISSUE WITH MYSQL SERVER RESTART
      We will fix this by merging a simpler fix in MariaDB 10.0.

      Bug#27309336 Backport to 5.7
      MDEV-18349 implements this in a simpler way.

      Bug#19730200: EXCHANGE PARTITION FOR PARTITION WITH DATA DIRECTORY
      This fixes a feature request to allow EXCHANGE PARTITION to work even when there is a mismatch on the DATA DIRECTORY attribute between the table and the partition. Unlike MariaDB, MySQL 5.7 implements native partitioning, and only for the InnoDB storage engine. The change would be different for MariaDB. We will not merge this.

      Not applicable to MariaDB

      Bug #28470805 DELETE CASCADE CRASHES AS FOREIGN TABLE'S VIRT COL DATA NOT UPDATED ON RESTART
      There is no test case, but the description is clear enough to write one. I verified the bug on MySQL 5.7.24 with my own test case. In preparation for MDEV-5800, we added proper pre-opening of FOREIGN KEY child tables. This bug does not affect MariaDB at all, because the child tables would always be opened when opening the parent table.

      Bug #26636815 OS0FILE.CC ASSERTION FAILED 'OFFSET > 0' IN OS_FILE_IO_COMPLETE
      This fixes some type mismatch in the I/O handling code in MySQL 5.7 that limited the maximum InnoDB data file size to 4 GiB on 32-bit systems. MariaDB is already using proper data types.

      Bug#28448853 - ASSERTION FAILURE: ROW0LOG.CC:2153 ROW_LOG_TABLE_APPLY
      Ever since MariaDB 10.2.11, (MDEV-13795/MDEV-14332 Corruption during online table-rebuilding ALTER when VIRTUAL columns exist), MariaDB is logging nothing for non-indexed virtual columns when rebuilding a table. The test case does not fail on MariaDB, even with AddressSanitizer.

      Bug #28491099 MEMORY BLOCK IS INVALID; ASSERTION FAILURE: UT0UT.CC:670
      This one probably applies to the native partitioning in MySQL 5.7 only (not present in MariaDB). The test case does not fail on MariaDB, even with AddressSanitizer.

      Bug#28693568 MEMORY LEAK IN EMBEDDED SERVER
      This appears to fix a memory leak in something that MDEV-17532 fixed differently. MariaDB is not affected.

      Bug #27968952 INNODB CRASH/CORRUPTION WITH TEXT PREFIX INDEXES
      The code change that this patch adds was already added in MDEV-17548. The MariaDB test suite does not report any heap-use-after-free in the server. This change does not apply to MariaDB.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                marko Marko Mäkelä
                Reporter:
                marko Marko Mäkelä
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: