ourdelta-developers team mailing list archive

[Kristian Nielsen <knielsen@xxxxxxxxxxxxxxx>]

 On 19/10/2009, at 6:08 AM, Mark Callaghan wrote:
> Why have the built-in and plug-in versions of InnoDB been disabled?  
> Disabled means I cannot compile them with MariaDB.

> And why does XtraDB use the plugin name 'innobase' rather than  
> 'xtradb' or 'xtradb_plugin'?
> Built-in InnoDB uses the name 'innobase' and plug-in InnoDB uses the  
> name 'innodb_plugin'.

Yes.

When I merged XtraDB, the idea was to replace built-in innodb with
XtraDB. Users should not have to do anything to switch to XtraDB.

This is based on the assumption that XtraDB will work at least as well as
built-in innodb for everybody. If this is not the case we of course need to
revisit the decision.

Also, when XtraDB was merged there was no facilities to have multiple versions
of InnoDB plugins in the source with multiple names. This was introduced later
with the merge of MySQL 5.1.39. We have been in a bit of a scramble to get
these two changes merged, and things are clearly not as elegant as they could
be.

One problem is the test suite. There are a number of tests that do not produce
the same result with built-in innodb and the innodb plugin / xtradb. I think
you will find that in MySQL 5.1.39, the innodb plugin is not well supported
and has very few tests run. In MariaDB it is vice versa, xtradb is fully
supported, and built-in innodb is not.

In the end, it's about limited resources. If we can just maintain xtradb, we
can use more time for other important stuff. If there is a need for keeping
built-in innodb going, we will have to put priority on that over something
else.

 - Kristian.