Hi, Otto Kekäläinen <o...@seravo.fi> writes:
> I'd vote for this. Let's put at least all the big plugins in their own
> packages. The main mariadb-server-10.0 could include only the plugins
> that are loaded by default or that are just really small.
Actually, none of these plugins are enabled by default AFAIK. On my
laptop, here is what I have:
MariaDB [(none)]> SELECT COUNT(*) FROM information_schema.ALL_PLUGINS WHERE
PLUGIN_LIBRARY IS NOT NULL;
+----------+
| COUNT(*) |
+----------+
| 54 |
+----------+
=> Number of plugins.
MariaDB [(none)]> SELECT COUNT(*) FROM information_schema.ALL_PLUGINS WHERE
PLUGIN_LIBRARY IS NOT NULL AND PLUGIN_STATUS='ACTIVE';
+----------+
| COUNT(*) |
+----------+
| 1 |
+----------+
=> Number of plugins enabled, here I have only 1, namely mroonga, that I
have enabled manually.
> File size listing:
>
> /usr/lib/mysql/plugin$ ll -h | awk '{ print $5 "\t" $9}' | sort -hr
> 2,8M ha_mroonga.so
> 2,4M ha_innodb.so
> 1,9M ha_tokudb.so
> 1,3M ha_cassandra.so
> 858K ha_spider.so
> 238K handlersocket.so
> 116K ha_sphinx.so
> 49K server_audit.so
> 40K semisync_master.so
> 39K ha_sequence.so
> 15K semisync_slave.so
> 11K sql_errlog.so
> 11K query_response_time.so
> 11K query_cache_info.so
> 11K metadata_lock_info.so
> 11K auth_pam.so
> 10K dialog.so
> 6,4K locales.so
> 6,1K auth_socket.so
> 5,9K mysql_clear_password.so
>
> Motivated to have in their own packages: mroonga, tokudb, cassandra,
> spider. Connect and oqgraph are already. Do we want to keep Sphinx
> built-in maybe?
I don't really see why Sphinx would be kept builtin and not mroonga?
What about defining a size limit instead? Such as 50K or so?
> I am actually no expert in all of these plugins and I don't even know
> what e.g. sql_errorlog or semisync_master actually do.
>
> TokuDB is a special case because it only works on arch amd64, and that
> is good to reflect in packaging.
Indeed.
Cheers,
--
Arnaud Fontaine
signature.asc
Description: PGP signature
