[MDEV-22533] Documentation for Column Compression Created: 2020-05-12 Updated: 2020-05-22 Resolved: 2020-05-22 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Documentation, Documentation - Support, Server |
| Fix Version/s: | N/A |
| Type: | Task | Priority: | Major |
| Reporter: | Nuno | Assignee: | Ian Gilfillan |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
A few things: 1) The Command Line for this entry is incorrect: {{column_compression_zlib_level Needs to say "zlib-level" (I suppose). 2) Could it be added to the documentation of that page, or at least clarified here, Meaning, use "PAGE_COMPRESSED=1" and "COMPRESSED" on a blob column, at the same time on the same table, does that make sense, or would PAGE_COMPRESSED=1 be enough? 3) A big advantage of using PAGE_COMPRESSED is that the compressed data won't be cached in the buffer pool. What's the case for Column COMPRESSED? Thank you very much. |
| Comments |
| Comment by Ian Gilfillan [ 2020-05-22 ] |
|
https://mariadb.com/kb/en/storage-engine-independent-column-compression/#comparison-with-innodb-page-compression should answer your questions. Regarding 3), the compression is independent of the storage engine (and hence the InnoDB buffer pool), so treated as a regular blob, for example. |
| Comment by Nuno [ 2020-05-22 ] |
|
Thank you. Absolutely great. |