[MDEV-21877] Enable snappy compression by default for InnoDB page compression Created: 2020-03-05  Updated: 2023-11-30

Status: Open
Project: MariaDB Server
Component/s: Packaging, Storage Engine - InnoDB
Fix Version/s: None

Type: New Feature Priority: Major
Reporter: Geoff Montee (Inactive) Assignee: Sergei Golubchik
Resolution: Unresolved Votes: 0
Labels: None

Issue Links:
Blocks
is blocked by MDEV-11068 Review which innodb_compression_algor... Closed
is blocked by MDEV-12933 sort out the compression library chaos Closed
Relates

 Description   

Snappy is one of the options for InnoDB page compression, but it is not usually enabled in our builds:

https://mariadb.com/kb/en/innodb-page-compression/#checking-supported-innodb-page-compression-algorithms

The MariaDB ColumnStore storage engine has libsnappy as a dependency:

$ sudo rpm -q --requires MariaDB-columnstore-engine | grep snappy
 
libsnappy.so.1()(64bit)
 
$ sudo rpm -qa | grep -i snappy
 
snappy-1.1.0-3.el7.x86_64

If one of our packages already has libsnappy as a dependency, then would it make sense to enable it by default for InnoDB page compression in some new GA version?

 Comments   
Comment by Elena Stepanova [ 2020-03-05 ]

Please note that it would mean propagating a dependency of a separate (and probably not widely used) package onto the main one. As I understand, we usually try hard to avoid it, which is why we have separate packages for components with extra dependencies.

Generated at Thu Feb 08 09:10:31 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.