[MDEV-20565] Assertion failure on CHANGE COLUMN…SYSTEM VERSIONING Created: 2019-09-12 Updated: 2019-09-12 Resolved: 2019-09-12 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Data Definition - Alter Table, Storage Engine - InnoDB |
| Affects Version/s: | 10.4.3 |
| Fix Version/s: | 10.4.9 |
| Type: | Bug | Priority: | Major |
| Reporter: | Marko Mäkelä | Assignee: | Marko Mäkelä |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | crash, instant | ||
| Issue Links: |
|
||||||||
| Description |
|
The following will trigger a debug assertion failure in InnoDB:
The assertion failure is as follows:
This is the first affected revision, found by nikitamalyavin. |
| Comments |
| Comment by Marko Mäkelä [ 2019-09-12 ] |
|
This is a bogus debug assertion. The DATA_VERSIONED bits in dict_col_t::prtype do not affect the storage format. The assertion would fail whenever adding or removing the SYSTEM VERSIONING attribute of a column and renaming the column at the same time. If the column is a VARCHAR that is being instantly extended, the assertion would not fail for extending the VARCHAR, renaming the column, and changing the SYSTEM VERSIONING attribute. |
| Comment by Marko Mäkelä [ 2019-09-12 ] |
|
This was a bogus debug assertion, with no impact for release builds. |