January 2013 - discuss - lists.mariadb.org

[Maria-discuss] testing Galera
by Jan Kirchhoff 12 Feb '13

12 Feb '13

Hi, I'd like to evaluate mariadb-galera on some test databases. Our load is at least 90% writes coming from a datastream and I would try to set up a real-world situation and test with real data. Most of the work load is "insert ... on duplicate key update" mass-inserts (actually updates) of about 4MB/10000 rows each. 99% of these run onto 3-4 tables (each around 10GB/7 million rows of size). Total database size is around 800 GB. We have a traditional statement-based master-slave replication, but all these mass-inserts run over a proxy with SET SQL_LOG_BIN=0 in parallel on all systems - no way to process this amount of data single-threaded on the slaves. I was hoping galera would make this easier and make our proxies obsolete. I have some servers I could use for galera as a first step. I wanted to do this for 4 months now but never got into it, I read your request to test the RC and think I should start now hoping to be able to give some valuable feedback: After reading through the documentation and some blogs I have some doubts, but my idea was to do the following: I'd clone the database of an existing slave to a new machine with mariadb-galera (name the host "testgalera1" and rsync the database or use mysqldump). I'd then set up this one as a "normal" statement based slave connected to one of our masters? Afterwards, the next host "testgalera2" would have to be added to the galera-cluster? And after that, I'd set up one of our older database servers and add that to the cluster, too. My idea was to take an older, slower system to see how much this slowes the cluster down and get an idea how much headroom I'd have when I leave those old machines out (the old machines have only 64GB of RAM and slower CPUs). I'd then modify my proxy for all the incoming inserts and add a writer-thread to one of the hosts in the cluster, that data should be replicated by galera to all other galera hosts. All other data should be coming in via the "traditional" replication thread of testgalera1. This should give me a 95-99% real world write situation on the cluster. Adding a host to a running cluster would mean cloning the whole database (of course), but this also means the host I copy from would have to block write access to its tables and buffer all modifications in memory (at least that's how I read the documentation) during the copy process. Looking at the database size and amount of inserts, I am afraid adding a host to the cluster without taking everything down would be impossible - or even if it works fine now it could cause trouble once the database gets just a little bit larger or my load increases a bit. before I start with this - is galera an insane idea regarding my load? Or is it worth a try? Jan some numbers of some of the old databases: innodb_buffer_pool_size between 60-120 GB depending on server memory configuration. db5: Uptime: 8052248 Threads: 44 Questions: 1413881794 Slow queries: 160049 Opens: 683779 Flush tables: 2 Open tables: 1024 Queries per second avg: 175.588 db6: Uptime: 8070552 Threads: 6 Questions: 873413218 Slow queries: 3208 Opens: 336584 Flush tables: 1 Open tables: 578 Queries per second avg: 108.222 db7: Uptime: 4175032 Threads: 28 Questions: 639627677 Slow queries: 139337 Opens: 522673 Flush tables: 1 Open tables: 2016 Queries per second avg: 153.203 db7# mysql -e 'show global status like "%com\_%" ' |grep -v '\s0$' Variable_name Value Com_admin_commands 289127 Com_alter_table 6269 Com_analyze 725 Com_begin 3712141 Com_change_db 80112 Com_commit 3999309 Com_create_db 1 Com_create_table 253849 Com_create_trigger 10 Com_create_view 68 Com_delete 12365037 Com_delete_multi 7 Com_drop_table 310771 Com_drop_trigger 10 Com_drop_view 65 Com_empty_query 509 Com_flush 48 Com_grant 36 Com_insert 314280963 Com_insert_select 613565 Com_kill 214 Com_lock_tables 85 Com_optimize 1 Com_purge 2320 Com_rename_table 11 Com_repair 1 Com_replace 14240825 Com_replace_select 29920 Com_revoke 8 Com_rollback 13 Com_select 178540996 Com_set_option 6886915 Com_show_binlogs 69960 Com_show_charsets 1542 Com_show_collations 1544 Com_show_create_db 28 Com_show_create_func 195 Com_show_create_table 53282 Com_show_create_trigger 1 Com_show_databases 43584 Com_show_events 3 Com_show_fields 131874 Com_show_function_status 45 Com_show_grants 335 Com_show_keys 2582 Com_show_master_status 142 Com_show_plugins 7224 Com_show_procedure_status 45 Com_show_processlist 116918 Com_show_slave_status 83193 Com_show_status 155732 Com_show_storage_engines 25 Com_show_table_status 7439 Com_show_tables 1973739 Com_show_triggers 538 Com_show_variables 85034 Com_show_warnings 766 Com_stmt_close 363 Com_stmt_execute 363 Com_stmt_prepare 363 Com_truncate 452 Com_unlock_tables 79 Com_update 34496744 Com_update_multi 408212

5 10

[Maria-discuss] MariaDB 5.5.29, 5.3.12, 5.2.14, 5.1.67 now available
by Daniel Bartholomew 31 Jan '13

31 Jan '13

The MariaDB project is pleased to announce the immediate availability of the following new MariaDB versions: 5.5.29, 5.3.12, 5.2.14, & 5.1.67 Appologies in advance for the length of this email but we'd rather send out just one combined announce email instead of an email for each of these releases. - - Links - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - MariaDB 5.5.29 Stable (GA) - Release Notes: https://kb.askmonty.org/en/mariadb-5529-release-notes - Changelog: https://kb.askmonty.org/en/mariadb-5529-changelog - Downloads: https://downloads.mariadb.org/mariadb/5.5.29 MariaDB 5.3.12 Stable (GA) - Release Notes: https://kb.askmonty.org/en/mariadb-5312-release-notes - Changelog: https://kb.askmonty.org/en/mariadb-5312-changelog - Downloads: https://downloads.mariadb.org/mariadb/5.3.12 MariaDB 5.2.14 Stable (GA) - Release Notes: https://kb.askmonty.org/en/mariadb-5214-release-notes - Changelog: https://kb.askmonty.org/en/mariadb-5214-changelog - Downloads: https://downloads.mariadb.org/mariadb/5.2.14 MariaDB 5.1.67 Stable (GA) - Release Notes: https://kb.askmonty.org/en/mariadb-5167-release-notes - Changelog: https://kb.askmonty.org/en/mariadb-5167-changelog - Downloads: https://downloads.mariadb.org/mariadb/5.1.67 - - Other Links - - - - - - - - - - - - - - - - - - - - - - - - - - - APT and YUM Repository Configuration Generator: https://downloads.mariadb.org/mariadb/repositories/ Overview of MariaDB 5.5: https://kb.askmonty.org/en/what-is-mariadb-55 Overview of MariaDB 5.3: https://kb.askmonty.org/en/what-is-mariadb-53 Overview of MariaDB 5.2: https://kb.askmonty.org/en/what-is-mariadb-52 Overview of MariaDB 5.1: https://kb.askmonty.org/en/what-is-mariadb-51 - - Security Updates - - - - - - - - - - - - - - - - - - - - - - - - - These releases are "bug fix" releases and they include, among other things, fixes for the following security vulnerabilities: - A buffer overflow that can cause a server crash or arbitrary code execution (a variant of CVE-2012-5611) http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-5611 - CVE-2012-5627/MDEV-3915 fast password brute-forcing using the "change user" command http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-5627 https://mariadb.atlassian.net/browse/MDEV-3915 - CVE-2012-5615/MDEV-3909 information leakage about existing user accounts via the protocol handshake http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-5615 https://mariadb.atlassian.net/browse/MDEV-3909 - fixes for DoS attacks - crashes and server lockups https://mariadb.atlassian.net/browse/MDEV-4029 https://mariadb.atlassian.net/browse/MDEV-729 These releases of MariaDB also include all applicable upstream security fixes from MySQL, such as fix for a CVE-2012-5612/MDEV-3908 and other crashes. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-5612 https://mariadb.atlassian.net/browse/MDEV-3908 - - New Packages - - - - - - - - - - - - - - - - - - - - - - - - - - - MariaDB 5.5.29 includes packages for Fedora 18 "Spherical Cow" and Ubuntu 12.10 "Quantal Quetzal". Visit the Repository Configurator to generate the necessary commands to easily install MariaDB on these and many other distributions. We've also extended the repository configuration tool to provide instructions for distributions which include MariaDB. We've started with Mageia and will be adding others soon. https://downloads.mariadb.org/mariadb/repositories/ - - Discontinued Builds - - - - - - - - - - - - - - - - - - - - - - - Along with the news of new package builds is the news that some old distributions will be deprecated. The MariaDB project tries to support as many different operating systems and Linux distributions as possible. However, when a distribution or OS stops receiving upstream security and other updates it becomes difficult to provide packages for that platform. In such cases, our policy is to deprecate that platform and stop building binary packages for it in our build system. As of 1 Feb 2013, we will stop building and testing packages for the following: - Fedora 16 "Verne" - Debian 5 "Lenny" - Ubuntu 10.10 "Maverick" - Ubuntu 11.04 "Natty" Even after your chosen Linux distribution is deprecated, packages and support are still available. Companies such as SkySQL and Monty Program (among others) provide paid support for all versions of MariaDB and back to even very old MySQL versions. This includes packaged binaries. More information on our deprecation policy can be found at: https://kb.askmonty.org/en/mariadb-deprecation-policy/ - - Archived Releases - - - - - - - - - - - - - - - - - - - - - - - - From the beginning of the MariaDB project in 2009 we've kept all of our old releases online via our network of mirrors. Doing this is great for those few who are interested in old releases, but the disk space required to host all of our old releases is over 130 Gigabytes at present and grows by several gigabytes with each new release. This is too much for some of our mirrors to handle. So, starting with this round of releases our primary mirror will only host the most recent few releases in each series (5.5, 10.0, 5.3, and so on). Mirrors are, of course, free to keep archiving every release, but the primary mirror that they pull from will not. Old releases do have value, so for those that are interested in old releases, we are setting up a simple, no frills, archive server which will host them. Once the server is up and running, links to archived releases on https://downloads.mariadb.org will point at the archive server. During the transition period, links to some old releases may disappear for a short time, but don't worry, they haven't been deleted, they're just being moved! If you have hundreds of spare gigabytes on a fast connection and would also like to host the complete MariaDB archive, contact us at mirror at mariadb.org and we'll include a link your mirror from our archive server. (see https://kb.askmonty.org/en/mirroring-mariadb/ for more information about becoming a mirror) - - User Feedback plugin - - - - - - - - - - - - - - - - - - - - - - - MariaDB includes a User Feedback plugin. This plugin is disabled by default. If enabled, it submits basic, completely anonymous MariaDB usage information. This information is used by the developers to track trends in MariaDB usage to better guide development efforts. If you would like to help make MariaDB better, please add "feedback=ON" to your my.cnf (my.ini on Windows) file! See http://kb.askmonty.org/en/user-feedback-plugin for more information. - - Quality - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - The project always strives for quality, but in reality, nothing is perfect. Please take time to report any issues you encounter at: http://mariadb.org/jira - - Support MariaDB - - - - - - - - - - - - - - - - - - - - - - - - - - If you would like to contribute to MariaDB, please see our "contributing" and "donations" pages. We also have merchandise available in a cafepress store. - https://kb.askmonty.org/en/contributing - https://mariadb.org/en/donate/ - http://www.cafepress.com/mariadb We hope you enjoy MariaDB! -- MariaDB: An Enhanced Drop-in Replacement for MySQL Website - http://mariadb.org Twitter - http://twitter.com/mariadb Google+ - http://google.com/+mariadb Facebook - http://fb.com/MariaDB.dbms Knowledgebase - http://kb.askmonty.org Monty Program - http://montyprogram.com

1 0

Re: [Maria-discuss] noinstall package for MariaDB
by Vineet Deodhar 25 Jan '13

25 Jan '13

Thank you. I really appreciate the fast & helpful response on this mailing list. --- Vineet --- On Fri, 25/1/13, Vladislav Vaintroub <wlad(a)montyprogram.com> wrote: From: Vladislav Vaintroub <wlad(a)montyprogram.com> Subject: RE: [Maria-discuss] noinstall package for MariaDB To: "'Vineet Deodhar'" <d_vineet(a)yahoo.com> Date: Friday, 25 January, 2013, 15:10 >Thanks Vladislav. >If I get you right, I should copy & paste the directories EXCEPT the data directory. >Is that correct? This is correct, and this is what you also should normally do when updating zips, even if you are not switching MySQL variants. >I am using Windows at present, but going to switch over to Ubuntu 12.04 LTS soon. :-) >Can you pl. share the mariadb download url for linux? Everything is on https://downloads.mariadb.org/mariadb . For example https://downloads.mariadb.org/mariadb/5.5.28a/#os_group=linux_generic would be tar.gz (if you favor non-install packages, like on Windows, those are the right ones)

1 0

[Maria-discuss] noinstall package for MariaDB
by Vineet Deodhar 25 Jan '13

25 Jan '13

Hi ! At present, I am using MySQL noinstall version (which doesn't require ANY installation). Just copy & paste the folder & start. Is there any way to use MariaDB without installing? (Maybe replace MySQL folder containing the binaries with MariaDB folder? If yes, from where to get the noinstall folder for MariaDB?) Thanks, Vineet

2 2

[Maria-discuss] Compatibility problems switching Glassfish application from MySQL to MariaDB
by Guido Winkelmann 24 Jan '13

24 Jan '13

Hi, I'm having some problems switching one of our Java/Glassfish-based web applications over from MySQL to to MariaDB. Since the MariaDB project advertises the software as a fully compatible drop- in replacement for MySQL, the first thing I did was simply stop the MySQL server, uninstall it, and then install and start MariaDB (5.5.28a, from Gentoo portage). We have got several C/C++ based application that access our MySQL databases. Those took a recompile, but afterwards continued to work as if nothing had happened. I didn't have as much luck with our glassfish-based web frontend though. The first problem was that the existing MySQL connector is apparently unable to connect to MariaDB, so I deleted the existing JDBC Connection Pools and replaced them with new ones using the MariaDB Java Client instead. This worked on the surface, however now I'm getting a lot of exceptions whenever I'm accessing parts of the application that make use of BINARY type columns. According to the developer (of the web application on question), this is because either MariaDB itself or the connector are returning binary columns as type string, causing the persistance layer to attempt to convert them to a string object. Since the binary columns in question contain various unprintable characters, including zero-bytes, this fails. Can someone please help me with these problems? Guido

2 2

[Maria-discuss] 10.0.0 msi pack fails first start
by Federico Razzoli 24 Jan '13

24 Jan '13

Hi I tried to install MariaDB 10.0.0 on Windows XP, MSI package. Apparently the installation worked, but the server fails to start. I paste here the log until the first shutdown, just in case you don't know about this problem. Federico 130124 10:49:47 InnoDB: The InnoDB memory heap is disabled 130124 10:49:47 InnoDB: Mutexes and rw_locks use Windows interlocked functions 130124 10:49:47 InnoDB: Compressed tables use zlib 1.2.3 130124 10:49:47 InnoDB: CPU does not support crc32 instructions 130124 10:49:47 InnoDB: Initializing buffer pool, size = 128.0M 130124 10:49:47 InnoDB: Completed initialization of buffer pool InnoDB: The first specified data file .\ibdata1 did not exist: InnoDB: a new database to be created! 130124 10:49:47 InnoDB: Setting file .\ibdata1 size to 10 MB InnoDB: Database physically writes the file full: wait... 130124 10:49:47 InnoDB: Log file .\ib_logfile0 did not exist: new to be created InnoDB: Setting log file .\ib_logfile0 size to 5 MB InnoDB: Database physically writes the file full: wait... 130124 10:49:48 InnoDB: Log file .\ib_logfile1 did not exist: new to be created InnoDB: Setting log file .\ib_logfile1 size to 5 MB InnoDB: Database physically writes the file full: wait... 130124 10:49:48 InnoDB: Doublewrite buffer not found: creating new 130124 10:49:48 InnoDB: Doublewrite buffer created 130124 10:49:49 InnoDB: 128 rollback segment(s) are active. InnoDB: Creating foreign key constraint system tables InnoDB: Foreign key constraint system tables created 130124 10:49:49 InnoDB: Waiting for the background threads to start 130124 10:49:49 InnoDB: 1.2.0 started; log sequence number 0 130124 10:49:49 [Note] Plugin 'FEEDBACK' is disabled. 130124 10:49:56 InnoDB: FTS optimize thread exiting. 130124 10:49:56 InnoDB: Starting shutdown... 130124 10:49:58 InnoDB: Shutdown completed; log sequence number 1602824 130124 10:50:00 InnoDB: The InnoDB memory heap is disabled 130124 10:50:00 InnoDB: Mutexes and rw_locks use Windows interlocked functions 130124 10:50:00 InnoDB: Compressed tables use zlib 1.2.3 130124 10:50:00 InnoDB: CPU does not support crc32 instructions 130124 10:50:01 InnoDB: Initializing buffer pool, size = 31.0M 130124 10:50:01 InnoDB: Completed initialization of buffer pool 130124 10:50:01 InnoDB: Log file .\ib_logfile0 did not exist: new to be created InnoDB: Setting log file .\ib_logfile0 size to 31 MB InnoDB: Database physically writes the file full: wait... 130124 10:50:02 InnoDB: Log file .\ib_logfile1 did not exist: new to be created InnoDB: Setting log file .\ib_logfile1 size to 31 MB InnoDB: Database physically writes the file full: wait... 130124 10:50:03 InnoDB: highest supported file format is Barracuda. InnoDB: The log sequence number in ibdata files does not match InnoDB: the log sequence number in the ib_logfiles! 130124 10:50:03 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... 130124 10:50:03 InnoDB: 128 rollback segment(s) are active. 130124 10:50:03 InnoDB: Waiting for the background threads to start 130124 10:50:03 InnoDB: 1.2.0 started; log sequence number 1603084 130124 10:50:03 [Note] Plugin 'FEEDBACK' is disabled. 130124 10:50:03 [Note] Event Scheduler: Loaded 0 events 130124 10:50:03 [Note] C:\Programmi\MariaDB 10.0\bin\mysqld.exe: ready for connections. Version: '10.0.0-MariaDB' socket: '' port: 3306 Source distribution 130124 11:03:13 InnoDB: The InnoDB memory heap is disabled 130124 11:03:13 InnoDB: Mutexes and rw_locks use Windows interlocked functions 130124 11:03:13 InnoDB: Compressed tables use zlib 1.2.3 130124 11:03:13 InnoDB: CPU does not support crc32 instructions 130124 11:03:13 InnoDB: Initializing buffer pool, size = 128.0M 130124 11:03:13 InnoDB: Completed initialization of buffer pool InnoDB: Error: log file .\ib_logfile0 is of different size 32505856 bytes InnoDB: than specified in the .cnf file 5242880 bytes! 130124 11:03:14 [ERROR] Plugin 'InnoDB' init function returned error. 130124 11:03:14 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 130124 11:03:15 [Note] Plugin 'FEEDBACK' is disabled. 130124 11:03:16 [ERROR] Unknown/unsupported storage engine: InnoDB 130124 11:03:16 [ERROR] Aborting 130124 11:03:17 [Note] C:/Programmi/MariaDB 10.0/bin/mysqldd: Shutdown complete

1 1

[Maria-discuss] Trouble installing MariaDB 5.5 on Ubuntu 12.04 (& 12.10)
by Aaron Anderson 23 Jan '13

23 Jan '13

Gang, I've installed MariaDB on several Debian/Ubuntu systems in the past few months, without any issues. ~2 days ago on an Unbuntu 12.10 system did an apt-get update/upgrade/dist-upgrade. I believe that MariaDB was updated in that process. After the updates, mysql was "gone" My apps couldn't find it, it wasn't running, etc. I was in a hurry so I had to fall back to the standard mysql package so not a lot of into there. I built a new Ubuntu 12.04 LTS server, added the Maria repo, did an apt-get update/ugprade/dist-upgrade. Rebooted. Here's some output... I'm stuck in this loop. root@nn01:~# apt-get install mariadb-server Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: mariadb-server : Depends: mariadb-server-5.5 but it is not going to be installed E: Unable to correct problems, you have held broken packages. root@nn01:~# apt-get install mariadb-server-5.5 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: mariadb-server-5.5 : Depends: mariadb-client-5.5 (>= 5.5.28-mariadb-a1~precise) but it is not going to be installed Depends: mariadb-server-core-5.5 (>= 5.5.28-mariadb-a1~precise) but it is not going to be installed E: Unable to correct problems, you have held broken packages. root@nn01:~# apt-get install mariadb-client-5.5 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: mariadb-client-5.5 : Depends: libdbd-mysql-perl (>= 1.2202) but it is not going to be installed Depends: mariadb-common but it is not going to be installed Depends: libmariadbclient18 (>= 5.5.28-mariadb-a1~precise) but it is not going to be installed Depends: mariadb-client-core-5.5 (>= 5.5.28-mariadb-a1~precise) but it is not going to be installed E: Unable to correct problems, you have held broken packages. root@nn01:~#

2 2

[Maria-discuss] KB Question: Issues with ignore-db-dir
by Daniel Bartholomew 23 Jan '13

23 Jan '13

The following question has been posted to the Knowledgebase: https://kb.askmonty.org/en/issues-with-ignore-db-dir/ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Issues with ignore-db-dir Hello, I see that the ignore-db-dir option has been available since Maria 5.3.9 ( https://kb.askmonty.org/en/mariadb-539-changelog/ ) , however I am finding that MariaDB 5.5.27 is not recognizing the option. When I put "ignore-db-dir=lost+found" in the mysqld section of the my.cnf file or when I attempt to start mysqld with "/etc/init.d/mysql start --ignore-db-dir=lost+found", both times mysql fails to start with the following message: 130111 17:08:57 [ERROR] /usr/sbin/mysqld: unknown variable 'ignore-db-dir=lost+found' 130111 17:08:57 [ERROR] Aborting Is there a patch that I was supposed to apply but haven't ? Or maybe I am misunderstanding how or where to specify the ignore-db-dir option. For reference, the full version as reported by mysqld is: $ mysqld --version mysqld Ver 5.5.27-MariaDB for Linux on x86_64 (MariaDB Server) Thanks, -Said - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -- Daniel Bartholomew Google+ - http://gplus.to/dbart Twitter - http://twitter.com/daniel_bart MariaDB: An Enhanced Drop-in Replacement for MySQL Website - http://mariadb.org Twitter - http://twitter.com/mariadb Google+ - http://google.com/+mariadb Facebook - http://fb.com/MariaDB.dbms Knowledgebase - http://kb.askmonty.org Monty Program - http://montyprogram.com

1 0

[Maria-discuss] Fwd: [debian-mysql] Bug#688505: MariaDB packaging.
by Colin Charles 19 Jan '13

19 Jan '13

A good wishlist. I think more should vote for this, quite clearly! cheers, -colin Begin forwarded message: > Resent-From: Robert de Bath <robert$(a)debath.co.uk> > From: Robert de Bath <robert$(a)debath.co.uk> > Subject: [debian-mysql] Bug#688505: MariaDB packaging. > Date: 23 September 2012 16:25:39 GMT+08:00 > Resent-To: debian-bugs-dist(a)lists.debian.org > To: submit(a)bugs.debian.org > Resent-Cc: Debian MySQL Maintainers <pkg-mysql-maint(a)lists.alioth.debian.org> > Reply-To: Robert de Bath <robert$(a)debath.co.uk>, 688505(a)bugs.debian.org > > Package: mysql-server > Version: 5.5.24+dfsg-8 > Severity: wishlist > > My very technically savvy webhost has recently switched from MySQL to > MariaDB and claim it's for both technical and political reasons. > > Both of these reasons (better performance and better licensing) appear > to be good reasons for the software to be packaged as a Debian package > and I expect it's getting to the point that someone will do it themselves. > > BUT the software is technically still not a forked variant of MySQL > but a patched version where the maintainers continually resync to the > Oracle releases. For this reason I would like to see it treated as just > a simple MySQL version within Debian. This way the users (ie: me) can > simply switch by prodding apt in the right way. > > For this to work seamlessly (unlike, for example, the recent multimedia > troubles) the MariaDB package should be packaged identically to MySQL, > which IMO is best done by the same Debian maintainers. > > So my request is that you package the MariaDB as a secondary version of > MySQL in such a way that the two packages can be seamlessly switched within the Debian system. > > -- > Rob. (Robert de Bath <robert$ @ debath.co.uk>) > <http://www.debath.co.uk/> > > _______________________________________________ > pkg-mysql-maint mailing list > pkg-mysql-maint(a)lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint -- Colin Charles, http://bytebot.net/blog/ | twitter: @bytebot | skype: colincharles MariaDB: Community developed. Feature enhanced. Backward compatible. Download it at: http://www.mariadb.org/ Open MariaDB/MySQL documentation at the Knowledgebase: http://kb.askmonty.org/

3 3

[Maria-discuss] MariaDB Java Client 1.1.0 Released
by Daniel Bartholomew 16 Jan '13

16 Jan '13

The MariaDB Java Client 1.1.0 has been released. You can download it here: https://downloads.mariadb.org/client-java/1.1.0/ This version focused on fixing all known database metadata bugs and ConnnectorJ incompatibilities. Specific fixes include: - Consistent, compatible with ConnectorJ handling of JDBC catalogs vs schemas vs databases - Implementation of several missing methods in DatabaseMetaData - Better handling of statement timeouts - OSGi-specific entries have been added to MANIFEST.MF so it can be used in OSGi environments - Added support for dumpQueriesOnException=true in the JDBC URL - Added support for IPv6 addresses in the connector - Added SSL support - and more... See the Release Notes and Changelog for more information: - https://kb.askmonty.org/en/mariadb-java-client-110-release-notes - https://kb.askmonty.org/en/mariadb-java-client-110-changelog See also the "About the MariaDB Java Client" page: - https://kb.askmonty.org/en/about-the-mariadb-java-client -- MariaDB: An Enhanced Drop-in Replacement for MySQL Website - http://mariadb.org Twitter - http://twitter.com/mariadb Google+ - http://google.com/+mariadb Facebook - http://fb.com/MariaDB.dbms Knowledgebase - http://kb.askmonty.org Monty Program - http://montyprogram.com

1 0