MariaDB - TokuDB storage engine


I maintain MariaDB.
There is a subpackage containing TokuDB storage engine. (available only for

However the TokuDB can't be build against Jemalloc 5, but on F>=28 there is
no older jemalloc version.
The build without jemalloc is not supported too.

Is it OK to drop the subpackage on F28 and later until the upstream adds
the Jemalloc 5 support?
I'm ready to drop such update to Bodhi.

Here's a bugzilla for this issue:
<a href="" title=""></a>


Re: MariaDB - TokuDB storage engine

By Kevin Kofler at 05/30/2018 - 17:30

Michal Schorm wrote:
IMHO, if it works (well enough that nobody is complaining), just keep
shipping it that way. It's better than to break dependencies (if you don't
Obsolete the subpackage) or silently drop functionality (if you do) in an
update (which will probably even be a security update) to a stable release.

Kevin Kofler

Re: MariaDB - TokuDB storage engine

By Michal Schorm at 05/31/2018 - 07:18

On Wed, May 30, 2018 at 11:30 PM, Kevin Kofler <kevin. ... at chello dot at>

The biggest problem for me is, that as a maintainer, I have no idea, how
wide, skilled or satisfied the user base is.

If something is obviously broken, I get bugzilla filed or Bodhi update
But other than that, I don't know if - for example in TokuDB - are problems
present, but there is some workarounds, which skilled DB admins use but it
doesn work for them by default.

So I just hope "silence means yes - it works".