Storage-Engine Independent Column Compression
You are viewing an old version of this article. View
the current version here.
MariaDB starting with 10.3.2
Storage-engine independent support for column compression was introduced in MariaDB 10.3.2
Contents
Storage-engine independent column compression enables TINYBLOB, BLOB, MEDIUMBLOB, LONGBLOB, TINYTEXT, TEXT, MEDIUMTEXT, LONGTEXT, VARCHAR and VARBINARY columns to be compressed.
This is performed by means of a new COMPRESSED column attribute:
COMPRESSED[=<compression_method>]
Field Length
When using COMPRESSED attribute, check that FIELD LENGTH is reduced by 1, for example VARCHAR(255) have 255 length, and VARCHAR(255) COMPRESSED have 254 length, more info check MDEV-15592
New System Variables
column_compression_threshold
- Description: Minimum column data length eligible for compression.
- Commandline:
--column-compression-threshold=# - Scope: Global, Session
- Dynamic: Yes
- Data Type:
numeric - Default Value:
100 - Range:
0to4294967295
column_compression_zlib_level
- Description: zlib compression level (1 gives best speed, 9 gives best compression).
- Commandline:
--column-compression-threshold=# - Scope: Global, Session
- Dynamic: Yes
- Data Type:
numeric - Default Value:
6 - Range:
1to9
column_compression_zlib_strategy
- Description: The strategy parameter is used to tune the compression algorithm. Use the value
DEFAULT_STRATEGYfor normal data,FILTEREDfor data produced by a filter (or predictor),HUFFMAN_ONLYto force Huffman encoding only (no string match), orRLEto limit match distances to one (run-length encoding). Filtered data consists mostly of small values with a somewhat random distribution. In this case, the compression algorithm is tuned to compress them better. The effect ofFILTEREDis to force more Huffman coding and less string matching; it is somewhat intermediate betweenDEFAULT_STRATEGYandHUFFMAN_ONLY.RLEis designed to be almost as fast asHUFFMAN_ONLY, but give better compression for PNG image data. The strategy parameter only affects the compression ratio but not the correctness of the compressed output even if it is not set appropriately.FIXEDprevents the use of dynamic Huffman codes, allowing for a simpler decoder for special applications. - Commandline:
--column-compression-zlib_strategy=# - Scope: Global, Session
- Dynamic: Yes
- Data Type:
enum - Default Value:
DEFAULT_STRATEGY - Valid Values:
DEFAULT_STRATEGY,FILTERED,HUFFMAN_ONLY,RLE,FIXED
column_compression_zlib_wrap
- Description: If set to
1(0is default), generate zlib header and trailer and compute adler32 check value. It can be used with storage engines that don't provide data integrity verification to detect data corruption. - Commandline:
--column-compression-zlib-wrap{=0|1} - Scope: Global, Session
- Dynamic: Yes
- Data Type:
boolean - Default Value:
OFF
New Status Variables
Column_compressions
- Description: Incremented each time field data is compressed.
- Scope: Global, Session
- Data Type:
numeric
Column_decompressions
- Description: Incremented each time field data is decompressed.
- Scope: Global, Session
- Data Type:
numeric
Limitations
- The only supported method currently is zlib.
- The CSV storage engine stores data uncompressed on-disk even if the COMPRESSED attribute is present.
- It is not possible to create indexes over compressed columns.
Examples
CREATE TABLE cmp (i TEXT COMPRESSED); CREATE TABLE cmp2 (i TEXT COMPRESSED=zlib);
Comments
Comments loading...
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.