ROW_FORMAT=COMPRESSED I get the same results as
I previously poste, i.e. no difference in db size apart from when using lzma.
Cheers,
Rhys
From: Jan Lindström [mailto:jan.lindst...@mariadb.com]
Sent: 14 May 2015 06:14
To: Rhys Campbell
Cc: maria-discuss@lists.launchpad.net
Subject: Re: [Ma
: Re: [Maria-discuss] Innodb Page Compression
On Wed, May 13, 2015 at 6:00 PM, Rhys Campbell
mailto:rhys.campb...@tradingscreen.com>> wrote:
1. Why when trim is not used is the db size unchanged apart from lzma?
SET GLOBAL innodb_compression_algorithm effects only new tables, it do
Hello All,
I have compiled mariadb 10.1.4 from source to have a play with innodb page
compression. Not sure if these are bug or misunderstanding on my part, probably
a combination of both...
I am running in a CentOS 7 x64 VirtualBox VM 10.1.4-MariaDB-wsrep. The compile
support for page compres
3 matches
Mail list logo