[MDEV-16328] ALTER TABLE…page_compression_level should not rebuild table Created: 2018-05-30 Updated: 2021-03-17 Resolved: 2018-09-17 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - InnoDB, Storage Engine - XtraDB |
| Affects Version/s: | 10.1.0, 10.2.0, 10.3.0, 10.4.0 |
| Fix Version/s: | 10.3.10 |
| Type: | Bug | Priority: | Major |
| Reporter: | Marko Mäkelä | Assignee: | Marko Mäkelä |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | ddl, instant | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Description |
|
The InnoDB table options page_compressed and page_compression_level were introduced in MariaDB 10.1.0. An ALTER TABLE operation that changes these attributes unnecessarily causes a full table rebuild. Enabling page_compressed could be done instantaneously (not resulting in immediate space savings). The FORCE keyword could still be used to cause the table to be rebuilt. Disabling page_compressed must continue to require the table to be rebuilt. The page_compression_level basically matters for compression only, not for the decompression. It should be fine to change the compression level at any time, without any change. |
| Comments |
| Comment by Marko Mäkelä [ 2018-09-17 ] |
|
We will allow ALGORITHM=INSTANT for changing page_compression_level or setting the page_compressed attribute. |