29 Jun
2017
29 Jun
'17
10:18 a.m.
Hey Quote from https://mariadb.com/kb/en/mariadb/compression/ This approach differs significantly from legacy InnoDB compressed tables using row_format=compressed, where both uncompressed and compressed pages can be in the buffer pool. Any details why this is legacy? Should not be used? With a search engine I found a very old blog posting "InnoDB compression woes" from Percona. row_format=compressed is attractive when you pay your DBaaS per GB (storage based usage). Any insides? Lukas