Hello,
I maintain MariaDB. There is a subpackage containing TokuDB storage engine. (available only for x86_64)
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: https://bugzilla.redhat.com/show_bug.cgi?id=1538870
--
So far, on F>=28 the TokuDB was build without jemalloc. It may be risky to rely on, yet no one complained.
That's why I'm asking users mailing list too, to get a feedback for such pontential users, i would be otherwise unable to reach.
--
Michal Schorm Associate Software Engineer Core Services - Databases Team Red Hat
Michal Schorm wrote:
So far, on F>=28 the TokuDB was build without jemalloc. It may be risky to rely on, yet no one complained.
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
On Wed, May 30, 2018 at 11:30 PM, Kevin Kofler kevin.kofler@chello.at wrote:
Michal Schorm wrote:
So far, on F>=28 the TokuDB was build without jemalloc. It may be risky to rely on, yet no one complained.
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.
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 commented. 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".
--
Michal Schorm Associate Software Engineer Core Services - Databases Team Red Hat