Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Won't Do
Description
Between 2004 and 2007, when I designed and implemented ROW_FORMAT=COMPRESSED in the InnoDB Plugin for MySQL 5.1 based on Heikki Tuuri’s rough idea, it might have been a good idea to trade some CPU cycles for I/O bandwidth. Nowadays, with fast solid-state storage being a commodity, it is less so. ROW_FORMAT=COMPRESSED is introducing quite a bit of complexity to the buffer pool and crash recovery. We could make the server much faster if we removed write support.
The format is also too rigid to support innodb_page_size larger than 16 KiB or things like instant ADD COLUMN (MDEV-11369) or per-record transaction identifiers (MDEV-17598).
To allow users to upgrade from old databases, we must retain read support at least for a few major versions.
Attachments
Issue Links
- relates to
-
MDEV-23497 make ROW_FORMAT=COMPRESSED read-only by default
- Closed
-
MDEV-27058 Buffer page descriptors are too large
- Closed
-
MDEV-12152 KEY_BLOCK_SIZE strangeness in ALTER TABLE
- Open
-
MDEV-17598 InnoDB index option for per-record transaction ID
- Open
-
MDEV-21727 Optimize redo logging for ROW_FORMAT=COMPRESSED
- Open
-
MDEV-23835 InnoDB: Failing assertion: bpage->buf_fix_count == 0 in buf_relocate
- Closed
-
MDEV-24797 Column Compression - ERROR 1265 (01000): Data truncated for column
- Closed
-
MDEV-26400 ALTER TABLE does not remove KEY_BLOCK_SIZE for non-Compressed InnoDB tables
- Stalled
-
MDEV-30563 Failure 1478: Table storage engine 'InnoDB' does not support the create option 'ROW_TYPE' upon OPTIMIZE TABLE after Recovery
- Open
- links to