- discuss - lists.mariadb.org

[Maria-discuss] Fix different gtid-positions on domain 0 in multi-master
by Reinder Cuperus 17 Mar '17

17 Mar '17

Hello, After moving half of the databases on our primary master-master-cluster to a different cluster, we have a problem on our backup-server which is now a slave of both servers. Topology before: master1 <-> master2 -> backup-slave Topology during migrations: master1 <-> master2 -> backup-slave <-> master3 <-> master4 Final topology: master1 <-> master2 -> backup-slave <- master3 <-> master master4 The gtid_domain_ids before/during the migration were: master1/master2 : 0 master3/master4 : 20 Replication-settings: master2 -> backup: Replicate_Do_Domain_Ids: 0 master3 -> backup: Replicate_Do_Domain_Ids: 20 backup->master3: Replicate_Do_DB: DbToMigrate1,DbToMigrate2,etc Server version: 10.1.9 So after the migration, a typical gtid_position would be on: master1/2: 0-1-12345 master3/4: 0-1-12345,20-21-5678 As long as I keep the connection backup->master running (safe, because no new transactions on the migrated databases are occurring anymore on master1/2), the position on domain 0 gets recorded on master3. The problem is, as soon as I stop that connection, that master2 and master3 have different gtid-positions for domain0, and stop/start on replication master3->backup results in the error: "Got fatal error 1236 from master when reading data from binary log: 'Error: connecting slave requested to start from GTID 0-1-3898746614, which is not in the master's binlog' I have tried moving master1/2 to domain_id:1, and removing the domain_id:0 from the gtid_slave_pos on backup, but starting the replication master2->backup results in the error: Got fatal error 1236 from master when reading data from binary log: 'Could not find GTID state requested by slave in any binlog files. Probably the slave state is too old and required binlog files have been purged.' I have tried to find a way to insert an empty transaction, with the last gtid on domain_id:0 on the master3, to bring master2/master3 in sync again on that domain, but I could not find a way to do that on MariaDB. I tried finding a way to purge domain:0 from master3/master4, but the only way sofar I have found is doing a "RESET MASTER" on master3, which would break replication between master3 and master4. Are there other ways to fix this issue, so I can have reliable replication master3->backup without having to keep the dummy replication backup->master3 indefinitely? Regards, Reinder Cuperus

2 2

[Maria-discuss] Partition a Huge table
by Suresh Rajagopal 15 Mar '17

15 Mar '17

Hi, What is the fastest approach to partition a huge table with 2 additional columns? How safe its to alter table on slave and promote slave as master? It takes 25 hours to alter the table for now on slave. MariaDB Version : 10.1.18OS : Centos 6 ThanksSuresh

4 6

[Maria-discuss] [Warning] WSREP: Send action {(nil), 785, TORDERED} returned -103 (Software caused connection abort)
by Robbi Nespu 10 Mar '17

10 Mar '17

Hi there, I need to ask a guide from here. I have 5 galera cluster using mariadb 10.1 on centos 7 hosted on VPS for a few month. It running well until a weeks ago, during my leave, our VPS hosting rebooted our server. I create a backups and reboot the clusters1 till cluster2 (I don't enable auto start services on my box). Then on galera cluster 1, I ran command "galera_new_cluster" and start services on others clusters. cluster 2 - cluster 5 are working great. But it seems, cluster1 has problem. I checked services status and I got lot of this message : Mar 10 15:04:05 galera1 mysqld[6628]: 2017-03-10 15:04:05 139929087744768 [Warning] WSREP: Send action {(nil), 520, TORDERED} returned -103 (Software caused connection abort) Mar 10 15:04:05 galera1 mysqld[6628]: 2017-03-10 15:04:05 139929087744768 [Warning] WSREP: Send action {(nil), 520, TORDERED} returned -103 (Software caused connection abort) I tried to connect mariadb galera on cluster 1, seem the data are not synced unlike the others 4 cluster. Anyone face the same problem? Any guideline for me to troubleshoot this problem is most appreciated.

1 0

[Maria-discuss] Multiple Mariadb 10.1 instances on Centos 7
by Sales 09 Mar '17

09 Mar '17

I don’t see a mariadb@.service file on centos 7. I need to install multiple instances of mariadb 10.1 though and have them run from systemd (on the same server). The doc page https://mariadb.com/kb/en/mariadb/systemd/ <https://mariadb.com/kb/en/mariadb/systemd/> says that it’s installed on “some” systems. Apparently, some does not include Centos 7. So, is there a way to obtain a copy of the relevant file(s) needed to run multiple instances? Perhaps from another distribution? Seems like it’s a much better starting point than trying to create all that myself. Or, will it simply not work? What is the best way then to run multiple instances on Centos 7? Steve

2 3

[Maria-discuss] Maria db read/write configuration issues
by Chaitanya Cheekate 09 Mar '17

09 Mar '17

Hi We have configured maxscale in our environment using the links http://karlssonondatabases.blogspot.in/2014/02/maxscale-for-rest-of-us-part…, 2, 3 . We have two slaves and one master and the replication between them is working well. But after configuring read/write split the select queries are being executed in master itself, not routing to the slaves. Please find the attached documents of maxscale configuration, maxscale commands maxscale log and. Please help with maxscale read/write split. Attached documentsdetails 1. maxsconf.txt from the location /etc/maxscale.cnf 2. maxscale-commands.txt, coomands like maxadmin -pmariadb list servers, maxadmin -pmariadb list services, maxadmin -pmariadb show service "Splitter Service", 3. maxscale-log.txt from /var/log/maxscale Thanks Chaitu -- Thanks.

4 4

[Maria-discuss] slave_compressed_protocol = 1 has no effect
by Phil Sweeney 09 Mar '17

09 Mar '17

Hi there, I've been trying to make use of the compressed replication protocol between two existing MariaDB 10.1.21 boxes. Replication itself has been working fine for a while. I do: SET GLOBAL slave_compressed_protocol = 1; On both master and slave. Then stop/start slave. However, when I monitor the network usage, I see no reduction in network traffic. However, I tried compression via an ssh tunnel and saw a big reduction (ssh doing the compression, not MariaDB). So the traffic is definitely compressible. I tried setting the param via my.cnf and also restarting both master and slave to see if that would make a difference - no luck. Have confirmed the global variable shows 'ON' after the change, and was 'OFF' before. Is there potentially an issue with this working with the MariaDB supplied binary tarball (e.g. some compression lib dependency?) I see nothing in error.log to show an issue. Any other useful ways to debug this? Thanks! Phil

2 1

[Maria-discuss] MariaDB 10.0.30 now available
by Daniel Bartholomew 08 Mar '17

08 Mar '17

The MariaDB project is pleased to announce the immediate availability of MariaDB 10.0.30. This is a stable (GA) release. See the Release Notes and Changelog for details. - - Links - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - MariaDB 10.0.30 - Release Notes: https://mariadb.com/kb/en/mdb-10030-rn/ - Changelog: https://mariadb.com/kb/en/mdb-10030-cl/ - Downloads: https://downloads.mariadb.org/mariadb/10.0.30 About MariaDB 10.0: - https://mariadb.com/kb/en/what-is-mariadb-100/ APT and YUM Repository Configuration Generator: - https://downloads.mariadb.org/mariadb/repositories/ - - MariaDB Webinars - - - - - - - - - - - - - - - - - - - - - - - - - There are several upcoming MariaDB-focused webinars and many previously held ones available to watch on an on-demand basis at: - https://mariadb.com/news-events/webinars - - MariaDB Books - - - - - - - - - - - - - - - - - - - - - - - - - - There is an ever-growing library of MariaDB books available to help you get the most out of MariaDB. See the MariaDB Books page for details and links: - https://mariadb.com/kb/en/mariadb/books/ - - 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 or my.ini file! See http://mariadb.com/kb/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 the MariaDB Foundation, please see the "contributing" and "donations" pages. We also have merchandise available in a cafepress store. All proceeds go to support the MariaDB Foundation. - https://mariadb.com/kb/en/contributing - https://mariadb.org/donate/ We hope you enjoy MariaDB! -- MariaDB Website - http://mariadb.org Twitter - http://twitter.com/mariadbfdn - http://twitter.com/mariadb Google+ - http://google.com/+mariadb Facebook - http://fb.com/MariaDB.dbms Knowledge Base - http://mariadb.com/kb

4 5

[Maria-discuss] Change to innodb_large_prefix with respect to creating long indexes
by Marco Nicosia 07 Mar '17

07 Mar '17

Hi there, We noticed a change between MariaDB 10.1.18 and 10.1.20, but I haven't been able to find anything in the changelogs or JIRA that would help me understand what changed, and why. On 10.1.18, if I set `innodb_large_prefix=OFF` I can create indexes with lengths greater than 767 bytes and MariaDB only issues a warning. If I configure `innodb_large_prefix=ON` I get an error and the index fails to create. This seems like a bug? On 10.1.20, mysql fails to create the index regardless of how innodb_large_prefix is configured. We think that the result is that in 10.1.20, tables must be created or altered to use `ROW_FORMAT DYNAMIC` or `ROW_FORMAT COMPRESSED` if they are to contain an index with greater than 767 bytes in it. Is this the desired behavior? Was there a bug in 10.1.18 (and maybe previous)? I'm trying to understand the context better so that when devs ask us why index creation is failing, we give them the correct answer for why it used to work, and what they should be doing differently now that we're on 10.1.20. Thanks! -- Marco Nicosia Pivotal Software, Inc.

4 3

[Maria-discuss] Replication-manager + Maxscale
by Karthick Subramanian 02 Mar '17

02 Mar '17

Hi Experts, I have a 2 db server with one as master and another one as slave. Maxscale implemented with below monitor config: *[MySQL Monitor]* *type=monitor* *module=mysqlmon* *servers=master1,slave1* *monitor_interval=500* *script=/usr/bin/replication-manager --user root:password --rpluser replusr:password * *--hosts $INITIATOR,$NODELIST --failover=force --interactive=false* *events=master_down* When I shutdown master, failover is not automated. MRM (Replication Manager) is not promoting the slave to master automatically. In maxscale log, I noticed below: *2017-03-02 03:33:36 notice : Executed monitor script '/usr/bin/replication-manager --user root:password --rpluser replusr:password --hosts $INITIATOR,$NODELIST --failover=force --interactive=false' on event 'master_down'.* *2017-03-02 03:33:36 error : No Master can be determined.* Is this because I didn't have the quorum (no slave) since its one master and one slave set-up. Is there any workaround. Regards, Kart

3 4

[Maria-discuss] latin1 to utf8 conversion
by Suresh Rajagopal 25 Feb '17

25 Feb '17

Hi, I have a database(MariaDB 10.1.18) with latin1 characterset and a table with utf8 characterset.I can query the data only if i set names to latin1. How to convert the data to utf8 ? I have tried export/import,iconv. But still data doesn't show up. show create database test;+----------+----------------------------------------------------------------+| Database | Create Database |+----------+----------------------------------------------------------------+| test | CREATE DATABASE `test` /*!40100 DEFAULT CHARACTER SET latin1 */ |+----------+----------------------------------------------------------------+1 row in set (0.00 sec) CREATE TABLE `Test` ( `id` int(11) NOT NULL AUTO_INCREMENT, `name` varchar(255) COLLATE utf8_unicode_ci NOT NULL) ENGINE=InnoDB AUTO_INCREMENT=4312 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci | set names utf8;Query OK, 0 rows affected (0.00 sec) SELECT * FROM Test WHERE name = '2%Ss 60°C';Empty set (0.00 sec) set names latin1;Query OK, 0 rows affected (0.00 sec) SELECT name FROM Test WHERE name = '2%Ss 60°C';+------------+| name |+------------+| 2%Ss 60°C|| 2%Ss 60°C|+------------+2 rows in set (0.01 sec) ThanksSuresh

1 0

[Maria-discuss] Upgrading From MySQL 5.6 to MariaDB 10.1
by Michael Caplan 24 Feb '17

24 Feb '17

Hi there, I'm not seeing any concise information in the MariaDB docs about the recommended upgrade plan from MySQL 5.6 to MariaDB 10.1. Should I install MariaDB 10.0 and then 10.1? Or can I run right to 10.1? I'm running an older version of Ubuntu (12.04 Precise). Looking at the repo, it looks like I can stick with Precise, and hand that upgrade later. Or are there recommended min version of Ubuntu I should hit first? Thanks! Mike

5 9

[Maria-discuss] timestamp with time zone support mariaDB 10.1.14
by Karthick Subramanian 23 Feb '17

23 Feb '17

Hi Experts, I got this error, not sure whether maria db supports time zone: MariaDB [devdb]> create table ts (dt datetime, tz timestamp with time zone); ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'time zone)' at line 1 My application team is looking for time zone support. Any thought please. reference: https://mariadb.com/kb/en/sql-99/temporal-data-types/#time-with-time-zone

3 3

[Maria-discuss] MariaDB 10.2.4 RC now available
by Daniel Bartholomew 17 Feb '17

17 Feb '17

The MariaDB project is pleased to announce the immediate availability of MariaDB 10.2.4 Release Candidate (RC). See the Release Notes and Changelog for details. - - Links - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - MariaDB 10.2.4 - Release Notes: https://mariadb.com/kb/en/mdb-1024-rn/ - Changelog: https://mariadb.com/kb/en/mdb-1024-cl/ - Downloads: https://downloads.mariadb.org/mariadb/10.2.4 About MariaDB 10.2: - https://mariadb.com/kb/en/what-is-mariadb-102/ APT and YUM Repository Configuration Generator: - https://downloads.mariadb.org/mariadb/repositories/ - - MariaDB Webinars - - - - - - - - - - - - - - - - - - - - - - - - - There are several upcoming MariaDB-focused webinars and many previously held ones available to watch on an on-demand basis at: - https://mariadb.com/news-events/webinars - - MariaDB Books - - - - - - - - - - - - - - - - - - - - - - - - - - There is an ever-growing library of MariaDB books available to help you get the most out of MariaDB. See the MariaDB Books page for details and links: - https://mariadb.com/kb/en/mariadb/books/ - - 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 or my.ini file! See http://mariadb.com/kb/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 the MariaDB Foundation, please see the "contributing" and "donations" pages. We also have merchandise available in a cafepress store. All proceeds go to support the MariaDB Foundation. - https://mariadb.com/kb/en/contributing - https://mariadb.org/donate/ We hope you enjoy MariaDB! -- MariaDB Website - http://mariadb.org Twitter - http://twitter.com/mariadbfdn - http://twitter.com/mariadb Google+ - http://google.com/+mariadb Facebook - http://fb.com/MariaDB.dbms Knowledge Base - http://mariadb.com/kb

1 0

Re: [Maria-discuss] 10.1.x: Got packet bigger than 'max_allowed_packet' bytes
by Reindl Harald 17 Feb '17

17 Feb '17

Am 17.02.2017 um 18:26 schrieb Chris Calender: > Hello, > > On 2/17/2017 9:51 AM, Reindl Harald wrote: >> Am 16.02.2017 um 10:04 schrieb Peter Laursen: >>> The particular error message "Got packet bigger than >>> 'max_allowed_packet' bytes" is returned from the client and not the >>> server. >>> >>> Both the server and the client has a "max_allowed_packet" setting. The >>> client-one is listed >>> here https://dev.mysql.com/doc/refman/5.7/en/mysql-command-options.html >> >> well, tell that "mysql_upgrade" (part of mariadb) and "myqltuner" >> (mysqtuner pretends "[!!] Attempted to use login credentials, but they >> were invalid" when this is ste in the [client] section >> >> mysql_upgrade >> /usr/bin/mysql_upgrade: unknown variable 'max_allowed_packet=200M' > > I'm sure you're already aware of this, but for anyone else out there > following along that does not know, cases like this are exactly what the > --loose- prefix is for. That way one should be able to prefix such > variables with --loose-, under say the [client] section, and then client > programs that understand the variable should work, and those that do not > *should* not fail (though I cannot comment specifically on mysqltuner, > as I've not used it before). But that is the general premise of the > --loose-* prefix. no, i am not aware of this and to be honest have zero understanding when client software from the same build don't understand and or at least just ignores options it don't understand we can dicsuss about server better safe than sorry, but frankly i am not a big fan of things not doing anything because they don't understand a future or removed config param > For instance, if you set: > > [client] > loose-max_allowed_packet=200M > > Then mysql_upgrade will only throw a warning and continue on: > > shell> mysql_upgrade -uroot -ppass -P3366 > Warning: mysql_upgrade: unknown variable 'loose-max_allowed_packet=200M' > Phase 1/6: Checking and upgrading mysql database > Processing databases > ... > >> so currently "mysql" is the only client which a) understands it and b) >> proceeeds it correctly - what a mess > > Also, mysqldump does read and process max_allowed_packet correctly. So > for anyone out there reading this strictly in regards to > max_allowed_packet, don't forget mysqldump needs it too (which it would > read it from [client], [mysqldump], or the command line invocation itself)

1 0

[Maria-discuss] 10.1.x: Got packet bigger than 'max_allowed_packet' bytes
by Reindl Harald 17 Feb '17

17 Feb '17

/etc/my.cnf (for many years now) max_allowed_packet = 200M how can it be that when the whole table file is 54MB large with a setting of 200MB that something is larger then 200MB while obviously it was not too large at insert time at 2016-10-06 but with MariaDB 10.0.x instead 10.1.x? PHP says mysqli_fetch_assoc() [<a href='http://at.php.net/manual/de/function.mysqli-fetch-assoc.php'>function.mysqli-fetch-assoc.php</a>]: Malformed server packet. Field length pointing 22 bytes after end of packet MariaDB [afi]> select * from cms1_docmgmt_entrys where doc_id=19; ERROR 2020 (HY000): Got packet bigger than 'max_allowed_packet' bytes MariaDB [afi]> show variables like 'max_allowed_packet'; +--------------------+-----------+ | Variable_name | Value | +--------------------+-----------+ | max_allowed_packet | 209715200 | +--------------------+-----------+ 1 row in set (0,00 sec) MariaDB [afi]> select doc_file_download_size from cms1_docmgmt_entrys where doc_id=19; +------------------------+ | doc_file_download_size | +------------------------+ | 15838399 | +------------------------+ 1 row in set (0,00 sec) -rw-rw---- 1 mysql mysql 9,3K 2017-02-04 15:39 cms1_docmgmt_entrys.frm -rw-rw---- 1 mysql mysql 54M 2017-02-10 04:05 cms1_docmgmt_entrys.MYD -rw-rw---- 1 mysql mysql 234K 2017-02-10 04:05 cms1_docmgmt_entrys.MYI

3 5

[Maria-discuss] mysqldump 10.1.16
by Karthick Subramanian 16 Feb '17

16 Feb '17

All, I got a replciation problem and planned to take master server dump using below command and tried to restore in slave server: mysqldump --skip-lock-tables --single-transaction --flush-logs --hex-blob --master-data=1 -A --routines > ~/dump.sql I got into this error: https://jira.mariadb.org/browse/MDEV-10119 Then I tried this method: http://lists.askmonty.org/pipermail/commits/2016-June/009504.html My question: Is it ok if the GIS procedure currently with definer as definer=`root@localhost` instead of blank as definer=`` for the following two procs in mysql: Slave_MariaDB [(none)]> select db, name, definer from mysql.proc; +---------+------------------------+-----------------+ | db | name | definer | +---------+------------------------+-----------------+ | mysql | AddGeometryColumn | root@localhost | | mysql | DropGeometryColumn | root@localhost | Master_MariaDB [(none)]> select db, name, definer from mysql.proc; +---------+------------------------+-----------------+ | db | name | definer | +---------+------------------------+-----------------+ | mysql | AddGeometryColumn | @ | | mysql | DropGeometryColumn | @ |

2 2

[Maria-discuss] LOAD DATA LOCAL INFILE
by Karthick Subramanian 15 Feb '17

15 Feb '17

HI All, Even after enabling --local-infile=1 at mysql user login, I couldn't load the file locally. mysql -u root --local-infile=1 LOAD DATA LOCAL INFILE ERROR 1148 (42000): The used command is not allowed with this MariaDB version show variables like '%local%'; +---------------+-------+ | Variable_name | Value | +---------------+-------+ | local_infile | OFF | +---------------+-------+ Even though i enable --local-infile=1, the local-infile still shows OFF. Pleaselet know how can I fix this.

3 4

[Maria-discuss] ROLE and DEFAULT DATABASE
by Karthick Subramanian 09 Feb '17

09 Feb '17

Hi, Can anyone assist me on this below: I have a database called appdb. I need to grant access to this db to different users say: api_user, app_user, portal_user. So I created a ROLE as APP_ROLE and GRANT as below: GRANT SELECT, INSERT, UPDATE, DELETE ON APPDB.* TO APP_ROLE; Later I assign the Role to user: GRANT APP_ROLE TO API_USER@'%' IDENTIFIED BY 'YOU'; SET DEFAULT ROLE APP_ROLE TO API_USER@'%'; But the problem now is: Application team want to choose the database when they establish connection. But they couldn't use APPDB. So they couldn't see any db objects listed in APPDB. Is there a way we can assign a default database also for user.

3 2

[Maria-discuss] default_tmp_storage_engine=NULL
by Ian Gilfillan 09 Feb '17

09 Feb '17

What is the purpose/effect of having MariaDB's default_tmp_storage_engine setting default to NULL instead of the default used in MySQL, Innodb? I can't see any obvious differences in behaviour.

3 3

Re: [Maria-discuss] R: default_tmp_storage_engine=NULL
by Federico Razzoli 09 Feb '17

09 Feb '17

Well, I can't think many cases where InnoDB is not the default engine. But, if it is not, why should you use it for temporary tables? If you mainly use TokuDB, maybe don't want to mix the engines. If you use MyISAM, maybe you don't want transactional temporary tables. I still think that MEMORY makes sense in all cases :) Federico -------------------------------------------- Gio 9/2/17, Ian Gilfillan <ian(a)mariadb.org> ha scritto: Oggetto: Re: [Maria-discuss] R: default_tmp_storage_engine=NULL A: "Maria Discuss" <maria-discuss(a)lists.launchpad.net> Data: Giovedì 9 febbraio 2017, 10:32 > I beleive that there is a difference if default_storage_engine != innodb, because in that case, default_tmp_storage_engine will not be InnoDB. Yes, that's the case. So why is this desirable in MariaDB as opposed to MySQL's implementation? _______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss(a)lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp

1 0

[Maria-discuss] R: default_tmp_storage_engine=NULL
by Federico Razzoli 09 Feb '17

09 Feb '17

Hi Ian I beleive that there is a difference if default_storage_engine != innodb, because in that case, default_tmp_storage_engine will not be InnoDB. It is much less clear to me why default_tmp_storage_engine doesn't default to MEMORY in both MariaDB and MySQL :) Federico -------------------------------------------- Gio 9/2/17, Ian Gilfillan <ian(a)mariadb.org> ha scritto: Oggetto: [Maria-discuss] default_tmp_storage_engine=NULL A: "Maria Discuss" <maria-discuss(a)lists.launchpad.net> Data: Giovedì 9 febbraio 2017, 09:23 What is the purpose/effect of having MariaDB's default_tmp_storage_engine setting default to NULL instead of the default used in MySQL, Innodb? I can't see any obvious differences in behaviour. _______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss(a)lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp

2 1

[Maria-discuss] 2017 MariaDB Developers Conference
by Ian Gilfillan 07 Feb '17

07 Feb '17

The 2017 MariaDB Developers Conference is taking place in New York City from 9-10 April. It's free to attend for everyone interested and you are welcome to sign up on the Meetup Group, as well to propose a topic, or vote for an existing topic. Details at https://mariadb.org/2017-developers-meetup-new-york/ M|17, the MariaDB User's Conference, is taking place directly afterwards, so if you're in the area, why not attend both :) https://m17.mariadb.com/

1 1

[Maria-discuss] CentOS7 Cassandra
by Ian Gilfillan 01 Feb '17

01 Feb '17

Can someone clarify the status of Cassandra in CentOS7? It appears to have been available in 6, but not in 7.

5 5

[Maria-discuss] MariaDB Fedora update - testing
by Michal Schorm 31 Jan '17

31 Jan '17

Hello everybody, I made a (form my POV) bigger change to how MariaDB is packed, and I would be grateful for any feedback. I separated all the non-essential utilities to a standalone sub-package "server-utils". It should be installed automaticly with the "server" package as a weak dendency, so regular user should not spot any change. For example, if you don't need Perl with your server, you can save about 20MB of the space with this update. Rawhide: https://koji.fedoraproject.org/koji/taskinfo?taskID=17426872 F25: https://bodhi.fedoraproject.org/updates/FEDORA-2017-0f44f2b8c8 F24: https://bodhi.fedoraproject.org/updates/FEDORA-2017-801e01d1ed Thanks for any feedback in an advance! -- Michal Schorm Core Services - Databases Team mail: mschorm(a)redhat.com Brno-IRC: mschorm

2 3

[Maria-discuss] 10.1.21 - tests: main.analyze_format_json w4 [ fail ]
by Reindl Harald 26 Jan '17

26 Jan '17

main.analyze_format_json w4 [ fail ] Test ended at 2017-01-21 16:23:31 CURRENT_TEST: main.analyze_format_json --- /usr/share/mysql-test/r/analyze_format_json.result 2017-01-17 20:38:20.000000000 +0100 +++ /usr/share/mysql-test/r/analyze_format_json.reject 2017-01-21 16:23:31.740853974 +0100 @@ -455,7 +455,7 @@ "r_loops": 1, "rows": 10, "r_rows": 10, - "r_total_time_ms": "REPLACED", + "r_total_time_ms": "REPLACED"e-4, "filtered": 100, "r_filtered": 20, "attached_condition": "(tbl2.a in (2,3))" mysqltest: Result length mismatch

2 1

[Maria-discuss] question about generating logs on MariaDB 10.1.21
by Chris Adams 25 Jan '17

25 Jan '17

Hello, I have just moved from a MySQL 5.6 server on CentOS 6.8 to a MariaDB 10.1.21 server on CentOS 7. It is installed and working. I would like to set up some logging, but it has not gone as expected. I have binary logging working. However, I can't generate general logs or error logs. Here is part of the /etc/my.cnf file: user=mysql port = 3306 socket = /var/lib/mysql/mysql.sock datadir = /mnt/mysqldbs log_error = /var/log/mysql/error.log general_log_file = /var/log/mysql/mysql.log general_log = 1 log_bin = /mnt/mysqldbs/logs/mysql-bin I assume that after a restart, the logs will be generated, then logged to as events happen. As it is, no log files are generated. Many thanks.

4 7

[Maria-discuss] MariaDB 10.1.x: tablespace does not exist or is just being dropped
by Reindl Harald 23 Jan '17

23 Jan '17

Hi that crap temp files never deleted are from years ago and a crash until now it was enough to keep that tempfiles, with 10.1.x mariadb don't start at all - *how to get rid of that crap* the idiotic warnings are one thing but the segfauls now... it's about a decade that it's not possible to cleanup such stuff http://grokbase.com/t/mysql/mysql/136kx5qp1w/how-can-i-drop-a-table-that-is… 2017-01-23 22:01:27 139913013700928 [ERROR] InnoDB: Trying to do i/o to a tablespace which exists without .ibd data file. i/o type 10, space id 545, page no 0, i/o length 8192 bytes 2017-01-23 22:01:27 7f40097b2940 InnoDB: Error: trying to access tablespace 545 page no. 0, InnoDB: but the tablespace does not exist or is just being dropped. 2017-01-23 22:01:27 139913013700928 [ERROR] InnoDB: tablespace id is 545 in the data dictionary but in file ./dbmail/#sql2-704-271.ibd it is 690! 2017-01-23 22:01:31 140380157278528 [ERROR] InnoDB: Trying to do i/o to a tablespace which exists without .ibd data file. i/o type 10, space id 545, page no 0, i/o length 8192 bytes 2017-01-23 22:01:31 7faccd687940 InnoDB: Error: trying to access tablespace 545 page no. 0, InnoDB: but the tablespace does not exist or is just being dropped. InnoDB: Error: Unable to read tablespace 545 page no 0 into the buffer pool after 100 attempts InnoDB: The most probable cause of this error may be that the table has been corrupted. InnoDB: You can try to fix this problem by using innodb_force_recovery. InnoDB: Please see reference manual for more details. InnoDB: Aborting... 2017-01-23 22:01:31 7faccd687940 InnoDB: Assertion failure in thread 140380157278528 in file buf0buf.cc line 3080 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 170123 22:01:31 [ERROR] mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. To report this bug, see https://mariadb.com/kb/en/reporting-bugs We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. Server version: 10.1.21-MariaDB key_buffer_size=33554432 read_buffer_size=131072 max_used_connections=0 max_threads=52 thread_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 53739 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0x0 thread_stack 0x48400 /usr/libexec/mysqld(my_print_stacktrace+0x29)[0x560568d7a139] /usr/libexec/mysqld(handle_fatal_signal+0x3ad)[0x5605689d780d] /lib64/libpthread.so.0(+0x10c30)[0x7faccb39cc30] /lib64/libc.so.6(gsignal+0x35)[0x7faccaffe765] /lib64/libc.so.6(abort+0x16a)[0x7faccb00036a] /usr/libexec/mysqld(+0x80a9b9)[0x560568cce9b9] /usr/libexec/mysqld(+0x85426d)[0x560568d1826d] /usr/libexec/mysqld(+0x8593ca)[0x560568d1d3ca] /usr/libexec/mysqld(+0x8440b8)[0x560568d080b8] /usr/libexec/mysqld(+0x7b8978)[0x560568c7c978] /usr/libexec/mysqld(+0x702902)[0x560568bc6902] /usr/libexec/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x5d)[0x5605689d999d] /usr/libexec/mysqld(+0x3dddfb)[0x5605688a1dfb] /usr/libexec/mysqld(_Z11plugin_initPiPPci+0x782)[0x5605688a2c32] /usr/libexec/mysqld(+0x353e75)[0x560568817e75] /usr/libexec/mysqld(_Z11mysqld_mainiPPc+0x35f)[0x56056881c1ef] /lib64/libc.so.6(__libc_start_main+0xf1)[0x7faccafea731] /usr/libexec/mysqld(_start+0x29)[0x560568812eb9] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash.

1 3

[Maria-discuss] 10.1.21 - tests: main.analyze_stmt_orderby 'xtradb' w4 [ fail ]
by Reindl Harald 23 Jan '17

23 Jan '17

main.analyze_stmt_orderby 'xtradb' w4 [ fail ] Test ended at 2017-01-21 18:43:58 CURRENT_TEST: main.analyze_stmt_orderby --- /usr/share/mysql-test/r/analyze_stmt_orderby.result 2017-01-17 20:38:20.000000000 +0100 +++ /usr/share/mysql-test/r/analyze_stmt_orderby.reject 2017-01-21 18:43:58.130938437 +0100 @@ -417,7 +417,7 @@ "r_loops": 1, "rows": 10, "r_rows": 10, - "r_total_time_ms": "REPLACED", + "r_total_time_ms": "REPLACED"e-3, "filtered": 100, "r_filtered": 100 }, @@ -486,7 +486,7 @@ "r_loops": 1, "rows": 7, "r_rows": 7, - "r_total_time_ms": "REPLACED", + "r_total_time_ms": "REPLACED"e-4, "filtered": 100, "r_filtered": 100 }, mysqltest: Result length mismatch

2 2

[Maria-discuss] LTO build fails likely because -static-libgcc
by Reindl Harald 22 Jan '17

22 Jan '17

why does MariaDB use "-g -static-libgcc" in "mysql_release.cmake" and so besides override -g0 break -flto builds?

2 4

[Maria-discuss] 10.1.21 - tests: main.multi_update 'xtradb' w8 [ fail ]
by Reindl Harald 21 Jan '17

21 Jan '17

i guess that below makes not much sense when running with "--binlog-format=row" /mysql-test-run.pl --parallel=8 --max-test-fail=0 --mysqld=--binlog-format=row main.multi_update 'xtradb' w8 [ fail ] Test ended at 2017-01-21 18:43:50 CURRENT_TEST: main.multi_update --- /usr/share/mysql-test/r/multi_update.result 2017-01-17 20:38:20.000000000 +0100 +++ /usr/share/mysql-test/r/multi_update.reject 2017-01-21 18:43:49.979037948 +0100 @@ -1055,7 +1055,6 @@ Warnings: Warning 1264 Out of range value for column 'field1' at row 1 Warning 1264 Out of range value for column 'field1' at row 2 -Note 1592 Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if any) rows are ignored. This order cannot be predicted and may differ on master and the slave. UPDATE (SELECT 128 as col1) x, table_11757486 SET field1=x.col1; ERROR 22003: Out of range value for column 'field1' at row 1 UPDATE table_11757486 SET field1=128; @@ -1069,7 +1068,6 @@ Warnings: Warning 1264 Out of range value for column 'field1' at row 1 Warning 1264 Out of range value for column 'field1' at row 2 -Note 1592 Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if any) rows are ignored. This order cannot be predicted and may differ on master and the slave. DROP TABLE table_11757486; SET SESSION SQL_MODE=default; end of 10.0 tests mysqltest: Result length mismatch

1 0

[Maria-discuss] for years failing tests
by Reindl Harald 21 Jan '17

21 Jan '17

shouldn't the testsuite at some point in time run without errors? "run STOP SLAVE '' first" - uhm did i start it? it's scripted by shipped scripts [root@testserver:~]$ cat /usr/local/bin/mysql-test.sh #!/usr/bin/dash /usr/bin/su -c 'cd /usr/share/mysql-test; ./mysql-test-run.pl --parallel=1 --max-test-fail=0 --mysqld=--binlog-format=mixed --force' mysql rm -rf /usr/share/mysql-test/var/* rpl.rpl_binlog_index 'row' [ fail ] Test ended at 2017-01-20 16:56:16 CURRENT_TEST: rpl.rpl_binlog_index mysqltest: In included file "./include/rpl_init.inc": included from ./include/master-slave.inc at line 38: included from /usr/share/mysql-test/suite/rpl/t/rpl_binlog_index.test at line 20: At line 165: query 'SET GLOBAL gtid_slave_pos= ""' failed: 1198: This operation cannot be performed as you have a running slave ''; run STOP SLAVE '' first The result from queries just before the failure was: include/master-slave.inc - saving '/usr/share/mysql-test/var/log/rpl.rpl_binlog_index-row/' to '/usr/share/mysql-test/var/log/rpl.rpl_binlog_index-row/' rpl.sec_behind_master-5114 'stmt' [ fail ] Test ended at 2017-01-20 16:58:33 CURRENT_TEST: rpl.sec_behind_master-5114 mysqltest: In included file "./include/rpl_init.inc": included from ./include/master-slave.inc at line 38: included from /usr/share/mysql-test/suite/rpl/t/sec_behind_master-5114.test at line 1: At line 165: query 'SET GLOBAL gtid_slave_pos= ""' failed: 1198: This operation cannot be performed as you have a running slave ''; run STOP SLAVE '' first The result from queries just before the failure was: include/master-slave.inc rpl.rpl_semi_sync_event_after_sync 'mix,xtradb' [ fail ] Test ended at 2017-01-20 16:59:24 CURRENT_TEST: rpl.rpl_semi_sync_event_after_sync mysqltest: At line 1: query 'set global rpl_semi_sync_master_wait_point=AFTER_SYNC' failed: 1193: Unknown system variable 'rpl_semi_sync_master_wait_point' The result from queries just before the failure was: set global rpl_semi_sync_master_wait_point=AFTER_SYNC; - saving '/usr/share/mysql-test/var/log/rpl.rpl_semi_sync_event_after_sync-mix,xtradb/' to '/usr/share/mysql-test/var/log/rpl.rpl_semi_sync_event_after_sync-mix,xtradb/'

3 11

[Maria-discuss] 10.1.21 - tests: main.compound w5 [ fail ]
by Reindl Harald 21 Jan '17

21 Jan '17

main.compound w5 [ fail ] Test ended at 2017-01-21 16:21:47 CURRENT_TEST: main.compound --- /usr/share/mysql-test/r/compound.result 2017-01-17 20:38:20.000000000 +0100 +++ /usr/share/mysql-test/r/compound.reject 2017-01-21 16:21:47.413144793 +0100 @@ -28,13 +28,16 @@ include/show_binlog_events.inc Log_name Pos Event_type Server_id End_log_pos Info master-bin.000001 # Gtid # # BEGIN GTID #-#-# -master-bin.000001 # Query # # use `test`; INSERT INTO t1 VALUES (4) +master-bin.000001 # Table_map # # table_id: # (test.t1) +master-bin.000001 # Write_rows_v1 # # table_id: # flags: STMT_END_F master-bin.000001 # Query # # COMMIT master-bin.000001 # Gtid # # BEGIN GTID #-#-# -master-bin.000001 # Query # # use `test`; INSERT INTO t1 VALUES (5) +master-bin.000001 # Table_map # # table_id: # (test.t1) +master-bin.000001 # Write_rows_v1 # # table_id: # flags: STMT_END_F master-bin.000001 # Query # # COMMIT master-bin.000001 # Gtid # # BEGIN GTID #-#-# -master-bin.000001 # Query # # use `test`; INSERT INTO t1 VALUES (6) +master-bin.000001 # Table_map # # table_id: # (test.t1) +master-bin.000001 # Write_rows_v1 # # table_id: # flags: STMT_END_F master-bin.000001 # Query # # COMMIT DROP TABLE t1| CREATE DATABASE mysqltest1| @@ -144,12 +147,17 @@ execute stmt using @a, @b, @c| include/show_binlog_events.inc Log_name Pos Event_type Server_id End_log_pos Info -master-bin.000001 # Gtid # # GTID #-#-# -master-bin.000001 # Query # # use `test`; SELECT `test`.`fn`(9) -master-bin.000001 # Gtid # # GTID #-#-# -master-bin.000001 # Query # # use `test`; SELECT `test`.`fn`(1) master-bin.000001 # Gtid # # BEGIN GTID #-#-# -master-bin.000001 # Query # # use `test`; insert t1 values( NAME_CONST('a',4)+3) +master-bin.000001 # Table_map # # table_id: # (test.t1) +master-bin.000001 # Write_rows_v1 # # table_id: # flags: STMT_END_F +master-bin.000001 # Query # # COMMIT +master-bin.000001 # Gtid # # BEGIN GTID #-#-# +master-bin.000001 # Table_map # # table_id: # (test.t1) +master-bin.000001 # Write_rows_v1 # # table_id: # flags: STMT_END_F +master-bin.000001 # Query # # COMMIT +master-bin.000001 # Gtid # # BEGIN GTID #-#-# +master-bin.000001 # Table_map # # table_id: # (test.t1) +master-bin.000001 # Write_rows_v1 # # table_id: # flags: STMT_END_F master-bin.000001 # Query # # COMMIT drop function fn| drop table t1| mysqltest: Result length mismatch

1 0

[Maria-discuss] 10.1.21 - tests: main.commit_1innodb 'xtradb' w6 [ fail ]
by Reindl Harald 21 Jan '17

21 Jan '17

main.commit_1innodb 'xtradb' w6 [ fail ] Test ended at 2017-01-21 16:21:39 CURRENT_TEST: main.commit_1innodb --- /usr/share/mysql-test/r/commit_1innodb.result 2017-01-17 20:38:20.000000000 +0100 +++ /usr/share/mysql-test/r/commit_1innodb.reject 2017-01-21 16:21:39.268245094 +0100 @@ -710,12 +710,12 @@ # drop temporary table t2; call p_verify_status_increment(1, 0, 1, 0); -SUCCESS - +ERROR +Expected commit increment: 1 actual: 0 commit; call p_verify_status_increment(1, 0, 1, 0); -SUCCESS - +ERROR +Expected commit increment: 1 actual: 0 # 26. Verify that SET AUTOCOMMIT issues an implicit commit # insert t1 set a=3; @@ -831,8 +831,8 @@ Note 1050 Table 't2' already exists # Sic: first commits the statement, and then the transaction. call p_verify_status_increment(0, 0, 0, 0); -SUCCESS - +ERROR +Expected commit increment: 0 actual: 2 create table t3 select a from t2; call p_verify_status_increment(2, 0, 4, 4); SUCCESS mysqltest: Result length mismatch

1 0

[Maria-discuss] what about cleanly deprecation of config options
by Reindl Harald 20 Jan '17

20 Jan '17

what about spit some warnings in 10.0.x releases instead after update to 10.1.x service not starting and you can look what confdig options needs to be removed 2017-01-20 16:34:36 140555676232000 [ERROR] /usr/libexec/mysqld: unknown option '--skip-federated' 2017-01-20 16:34:36 140555676232000 [ERROR] Aborting

3 9

[Maria-discuss] -DWITH_INNODB_DISALLOW_WRITES=OFF and still generated files
by Reindl Harald 20 Jan '17

20 Jan '17

10.1.21 - first try build 10.1.x -DWITH_INNODB_DISALLOW_WRITES=OFF and the stuff below is still built - why? Fehler beim Bauen des RPM: Installierte (aber nicht gepackte) Datei(en) gefunden: /usr/bin/wsrep_sst_common /usr/bin/wsrep_sst_mysqldump /usr/bin/wsrep_sst_rsync /usr/bin/wsrep_sst_xtrabackup /usr/bin/wsrep_sst_xtrabackup-v2 /usr/share/mysql/wsrep.cnf /usr/share/mysql/wsrep_notify

2 2

[Maria-discuss] sanity check: mysql_upgrade MariaDB 5.5 straight to 10.1
by mike bayer 19 Jan '17

19 Jan '17

Hi all - I believe I know the answer to this question, however hoping someone can confirm all the assumptions (looks like there are three) are correct. Basically if one installs mariadb-10.1 on top of a data directory that's currently 5.5, and we run mysql_upgrade, is it as good/compatible/safe as if we had upgraded first to 10.0 in the interim? Per mariadb's documentation: https://mariadb.com/kb/en/mariadb/upgrading-from-mariadb-55-to-mariadb-100/ "There are no changes in table or index formats between MariaDB 5.5 and MariaDB 10.0" https://mariadb.com/kb/en/mariadb/upgrading-from-mariadb-100-to-101/, "There are no changes in table or index formats between MariaDB 10.0 and MariaDB 10.1" So assumption 1, transitively we can conclude there are no changes in table or index formats between 5.5 and 10.1. Next, mysql_upgrade seems like it alters some tables in the mysql database, and runs mysqlcheck --check-upgrade --auto-repair, which itself is mainly running CHECK TABLE. assumption 2 is then: the table changes in mysql_upgrade work against a 5.5 database going straight to 10.1. This would mean that if there were some tables/column changes in 5.5->10.0, and some more in 10.0->10.1, the mysql_upgrade command encapsulates both sets of changes as shipped in 10.1. It looks like this step comes from the .sql files in scripts/ by way of concatenating them into the "comp_sql" tool. Doing a diff of these scripts between 10.0.28 and 10.1.18 seems like only mysql_system_tables_fix.sql has the important bits (we don't use the performance schema stuff) and it looks like it only adds ALTER statements for more columns, the new columns from the 10.0 script are maintained. Not to mention it documents in a very open-ended way "This part converts any old privilege tables to privilege tables suitable for current version of MySQL". assumption 3 is, the Mariadb 10.1 engine running CHECK TABLE against a 5.5 database is fully compatible. The schema changes seem to be straightforward and as CHECK TABLE seems to regard the table and index formats which in assumption 1 have not changed, this should be totally fine as well. Note that I'm being kind of vague about what mysql_upgrade and mysqlcheck do, as I've only read the public documentation, browsed the source code a bit and am hoping this is all there is to it. There are a few blog posts on the web that illustrate a 5.5->10.1 direct upgrade, but these are not "official". Thanks for any guidance people can offer here!

1 0

[Maria-discuss] MariaDB 10.1.21 and other releases now available
by Daniel Bartholomew 18 Jan '17

18 Jan '17

The MariaDB project is pleased to announce the immediate availability of MariaDB 10.1.21, MariaDB 10.0.29, MariaDB Galera Cluster 10.0.29, MariaDB Connector/J 1.5.7, MariaDB Connector/C 2.3.2, and MariaDB Connector/C 3.0.1 Beta. Apart from Connector/C 3.0.1 Beta, these are all stable (GA) releases. See the Release Notes and Changelogs for details. - - Links - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - MariaDB 10.1.21 - Release Notes: https://mariadb.com/kb/en/mdb-10121-rn/ - Changelog: https://mariadb.com/kb/en/mdb-10121-cl/ - Downloads: https://downloads.mariadb.org/mariadb/10.1.21 About MariaDB 10.1: - https://mariadb.com/kb/en/what-is-mariadb-101/ APT and YUM Repository Configuration Generator: - https://downloads.mariadb.org/mariadb/repositories/ MariaDB 10.0.29 - Release Notes: https://mariadb.com/kb/en/mdb-10029-rn/ - Changelog: https://mariadb.com/kb/en/mdb-10029-cl/ - Downloads: https://downloads.mariadb.org/mariadb/10.0.29 About MariaDB 10.0: - https://mariadb.com/kb/en/what-is-mariadb-100/ APT and YUM Repository Configuration Generator: - https://downloads.mariadb.org/mariadb/repositories/ MariaDB Galera Cluster 10.0.29 - Release Notes: https://mariadb.com/kb/en/mgc-10029-rn/ - Changelog: https://mariadb.com/kb/en/mgc-10029-cl/ - Downloads: https://downloads.mariadb.org/mariadb-galera/10.0.29 About MariaDB Galera Cluster: - https://mariadb.com/kb/en/what-is-mariadb-galera-cluster/ APT and YUM Repository Configuration Generator: - https://downloads.mariadb.org/mariadb/repositories/ MariaDB Connector/J 1.5.7 - Release Notes: https://mariadb.com/kb/en/mcj-157-rn/ - Changelog: https://mariadb.com/kb/en/mcj-157-cl/ - Downloads: https://downloads.mariadb.org/connector-java/1.5.7/ About MariaDB Connector/J: - https://mariadb.com/kb/en/about-mariadb-connector-j/ MariaDB Connector/C 2.3.2 - Release Notes: https://mariadb.com/kb/en/mcc-232-rn/ - Changelog: https://mariadb.com/kb/en/mcc-232-cl/ - Downloads: https://downloads.mariadb.org/connector-c/2.3.2/ About MariaDB Connector/C: - https://mariadb.com/kb/en/about-mariadb-connector-c/ MariaDB Connector/C 3.0.1 Beta - Release Notes: https://mariadb.com/kb/en/mcc-301-rn/ - Changelog: https://mariadb.com/kb/en/mcc-301-cl/ - Downloads: https://downloads.mariadb.org/connector-c/3.0.1/ About MariaDB Connector/C: - https://mariadb.com/kb/en/about-mariadb-connector-c/ - - MariaDB Webinars - - - - - - - - - - - - - - - - - - - - - - - - - There are several upcoming MariaDB-focused webinars and many previously held ones available to watch on an on-demand basis at: - https://mariadb.com/news-events/webinars - - MariaDB Books - - - - - - - - - - - - - - - - - - - - - - - - - - There is an ever-growing library of MariaDB books available to help you get the most out of MariaDB. See the MariaDB Books page for details and links: - https://mariadb.com/kb/en/mariadb/books/ - - 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 or my.ini file! See http://mariadb.com/kb/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 the MariaDB Foundation, please see the "contributing" and "donations" pages. We also have merchandise available in a cafepress store. All proceeds go to support the MariaDB Foundation. - https://mariadb.com/kb/en/contributing - https://mariadb.org/donate/ We hope you enjoy MariaDB! -- MariaDB Website - http://mariadb.org Twitter - http://twitter.com/mariadbfdn - http://twitter.com/mariadb Google+ - http://google.com/+mariadb Facebook - http://fb.com/MariaDB.dbms Knowledge Base - http://mariadb.com/kb

1 0

[Maria-discuss] Handlersocket and stale data
by Sales 15 Jan '17

15 Jan '17

Is it still the case that Handlersocket may return stale data when the underlying structure is updated? Since there is still no memcached plugin in Mariadb, hoping stale data is not an issue. Steve

1 0

[Maria-discuss] ON update timestamp replication
by Artem Kuchin 14 Jan '17

14 Jan '17

Hello! Both master and slave run: Server version: 10.1.14-MariaDB FreeBSD Ports Replication is based on mixed format. Slave is used for backups without locking and going off line. I have a script that runs once a day and checksums all tables, so all tables are 100% in match (it wait for sync, locks and checksums). One table is very often out of sync. ON MASTER: show create table Message193; CREATE TABLE `Message193` ( `Message_ID` int(11) NOT NULL AUTO_INCREMENT, `User_ID` int(11) NOT NULL, `Subdivision_ID` int(11) NOT NULL, `Sub_Class_ID` int(11) NOT NULL, `Priority` int(11) NOT NULL DEFAULT '0', `Keyword` char(255) NOT NULL, `ncTitle` varchar(255) DEFAULT NULL, `ncKeywords` varchar(255) DEFAULT NULL, `ncDescription` text, `ncSMO_Title` varchar(255) DEFAULT NULL, `ncSMO_Description` text, `ncSMO_Image` char(255) DEFAULT NULL, `Checked` tinyint(4) NOT NULL DEFAULT '1', `IP` char(15) DEFAULT NULL, `UserAgent` char(255) DEFAULT NULL, `Parent_Message_ID` int(11) NOT NULL DEFAULT '0', `Created` datetime NOT NULL, `LastUpdated` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, `LastUser_ID` int(11) NOT NULL, `LastIP` char(15) DEFAULT NULL, `LastUserAgent` char(255) DEFAULT NULL, `Type` char(255) DEFAULT NULL, `Title` char(255) DEFAULT NULL, `Background` char(255) DEFAULT NULL, `Link` char(255) DEFAULT NULL, PRIMARY KEY (`Message_ID`), UNIQUE KEY `Sub_Class_ID` (`Sub_Class_ID`,`Message_ID`,`Keyword`), KEY `User_ID` (`User_ID`), KEY `LastUser_ID` (`LastUser_ID`), KEY `Subdivision_ID` (`Subdivision_ID`), KEY `Parent_Message_ID` (`Parent_Message_ID`), KEY `Priority` (`Priority`,`LastUpdated`), KEY `Checked` (`Checked`), KEY `Created` (`Created`) ) ENGINE=MyISAM AUTO_INCREMENT=5 DEFAULT CHARSET=utf8 | ON SLAVE CREATE TABLE `Message193` ( `Message_ID` int(11) NOT NULL AUTO_INCREMENT, `User_ID` int(11) NOT NULL, `Subdivision_ID` int(11) NOT NULL, `Sub_Class_ID` int(11) NOT NULL, `Priority` int(11) NOT NULL DEFAULT '0', `Keyword` char(255) NOT NULL, `ncTitle` varchar(255) DEFAULT NULL, `ncKeywords` varchar(255) DEFAULT NULL, `ncDescription` text, `ncSMO_Title` varchar(255) DEFAULT NULL, `ncSMO_Description` text, `ncSMO_Image` char(255) DEFAULT NULL, `Checked` tinyint(4) NOT NULL DEFAULT '1', `IP` char(15) DEFAULT NULL, `UserAgent` char(255) DEFAULT NULL, `Parent_Message_ID` int(11) NOT NULL DEFAULT '0', `Created` datetime NOT NULL, `LastUpdated` timestamp NOT NULL, `LastUser_ID` int(11) NOT NULL, `LastIP` char(15) DEFAULT NULL, `LastUserAgent` char(255) DEFAULT NULL, `Type` char(255) DEFAULT NULL, `Title` char(255) DEFAULT NULL, `Background` char(255) DEFAULT NULL, `Link` char(255) DEFAULT NULL, PRIMARY KEY (`Message_ID`), UNIQUE KEY `Sub_Class_ID` (`Sub_Class_ID`,`Message_ID`,`Keyword`), KEY `User_ID` (`User_ID`), KEY `LastUser_ID` (`LastUser_ID`), KEY `Subdivision_ID` (`Subdivision_ID`), KEY `Parent_Message_ID` (`Parent_Message_ID`), KEY `Priority` (`Priority`,`LastUpdated`), KEY `Checked` (`Checked`), KEY `Created` (`Created`) ) ENGINE=MyISAM AUTO_INCREMENT=5 DEFAULT CHARSET=utf8 | Notice that `LastUpdated` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, on slave becomes `LastUpdated` timestamp NOT NULL, This is already bad enough because if master is lost then slave will not be the same as master, trigger are not restored. Now check records: MASTER MariaDB [anapolisdom_ru]> select * from Message193 limit 1\G *************************** 1. row *************************** Created: 2016-11-25 13:25:09 LastUpdated: 2016-11-25 13:25:09 MariaDB [anapolisdom_ru]> select * from Message193 limit 1\G Created: 2016-11-25 13:25:09 LastUpdated: 0000-00-00 00:00:00 As you see lastupdated field is not replicated at all. Two questions, problems: 1) How to replicate default value and on update part for this field? 2) How to make it replicate the timestamp value? Artem

3 5

[Maria-discuss] Enabling Github integration with JIRA
by jocelyn fournier 13 Jan '17

13 Jan '17

Hi all, Currently there's no way when a JIRA ticket is closed to have a direct access to the associated commits in Github. GitHub integration with JIRA is available, and quite easy to configure, so it would be great to have it enabled on MariaDB Server. Do you think it's possible? Thanks! -- Jocelyn Fournier Founder M : +33 6 51 21 54 10 https://www.softizy.com Softizy - At your side to Optimize your PHP / MySQL applications

3 2

[Maria-discuss] Issue with MariaDB-server-5.5.54-1.el6.x86_64
by Clint Dilks 05 Jan '17

05 Jan '17

Hi, Today I have updated a CentOS 6.8 system that has MariaDB-server installed from http://yum.mariadb.org/5.5/centos6-amd64 and found that I had an SELinux issue when I tried to restart the service. Using the information at https://wiki.centos.org/HowTos/SELinux I have created a local policy that seems to fix things module marialocal 1.0; require { type mysqld_safe_t; class capability { setuid setgid }; } #============= mysqld_safe_t ============== allow mysqld_safe_t self:capability setgid; allow mysqld_safe_t self:capability setuid; This seems to fix things for me, but I thought I had better see if others are experiencing the same problem ? It may be useful to know that the particular rpms are MariaDB-server-5.5.54-1.el6.x86_64 and selinux-policy-3.7.19-292.el6_8.2.noarch. If it is a bigger issue than just myself, should I report this somewhere else to see if we can get a fix added to the next MariaDB-server rpm ? Thanks

2 2

[Maria-discuss] limiting memory use by mariadb?
by l vic 05 Jan '17

05 Jan '17

Is there some way to set hard limit for use of RAM by mariaDB server? Thanks, -V

4 16

[Maria-discuss] Fwd: Update of RPM layout
by Michal Schorm 05 Jan '17

05 Jan '17

Hello all, I went through an idea [1] to lighten the server package. I tested it, and I found out, I can save about 40MB of space, if I'd move all Perl utilites to a standalone subpackage. It would make sense to move them, so the users don't need to install Perl with the server package. Especially in technologies like containers (or cloud images) size matters. It all depends on how often are those utilities [2] used together with the server, sice we don't want to displace importatnt scripts. In case, it would look like a good idea, there is also option to move to this subpackage other - infrequently used - utilities. -> Q: Hey, Users and Admins, which utilities do you think are essential for the server? Note: It can be solved by soft dependencies, so those utils would be installed with the server by default. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1205082 [2] mysql_find_rows mysqlaccess mysql_convert_table_format mysql_fix_extensions mysql_setpermission mysql_zap mysqldumpslow mysqld_multi mysqlhotcopy -- Michal Schorm Core Services - Databases Team mail: mschorm(a)redhat.com Brno-IRC: mschorm

3 3

[Maria-discuss] nofile and nproc settings for mysql user in /etc/security/limits.conf
by Kaushal Shriyan 30 Dec '16

30 Dec '16

Hi, What should be the recommended nproc and nofile settings for mariadb or mysql user in /etc/security/limits.conf or /etc/my.cnf? I am running CentOS Linux version 6.8 Any help will be highly appreciable. Regards, Kaushal

2 1

[Maria-discuss] possible bug? #innodb-encryption-threads
by lejeczek 27 Dec '16

27 Dec '16

hi everyone I'm having a peculiar situation, a problem here with my config, which config is pretty galera-vanilla. Namely, if I set these: plugin-load-add = file_key_management.so file-key-management file-key-management-filename = /var/lib/mysql/.keys.txt innodb_file_per_table = 1 innodb-encrypt-log innodb-encryption-threads = 4 <= # this ! one here I get constant load on four cores, it would fluctuate just under %400 CPU (24*7). I'd assume that innodb-encryption-threads value causes it, and whatever the value might be it will be reflected in CPU usage. I wonder if you too see it. I my case I think it does something more to one system, it crashes the bloody thing to the extent where cold reboot is needed. MariaDB-client-10.1.19-1.el7.centos.x86_64 MariaDB-shared-10.1.19-1.el7.centos.x86_64 MariaDB-common-10.1.19-1.el7.centos.x86_64 MariaDB-server-10.1.19-1.el7.centos.x86_64 best, L

3 2

[Maria-discuss] error on show status query
by l vic 26 Dec '16

26 Dec '16

Have the following error trace from running SHOW STATUS LIKE 'wsrep_%' Any idea what could cause it? 2016-12-21 3:39:24 139668819036928 [Note] InnoDB: Online DDL : End of applying row log 2016-12-21 3:39:24 139668819036928 [Note] InnoDB: Online DDL : Completed 2016-12-21 3:43:29 139668818733824 [Note] InnoDB: Online DDL : Start 2016-12-21 3:43:29 139668818733824 [Note] InnoDB: Online DDL : Start reading clustered index of the table and create temporary files 2016-12-21 03:43:29 7f072e53ab00 InnoDB: Error: Write to file (merge) failed at offset 0. InnoDB: 1048576 bytes should have been written, only 901120 were written. InnoDB: Operating system error number 12. InnoDB: Check that your OS and file system support files of this size. InnoDB: Check also that the disk is not full or a disk quota exceeded. InnoDB: Error number 12 means 'Cannot allocate memory'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html 2016-12-21 3:43:29 139668818733824 [Note] InnoDB: Online DDL : End of reading clustered index of the table and create temporary files java.sql.SQLNonTransientConnectionException: (conn:17945) Could not read resultset: unexpected end of stream, read 0 bytes from 4 Query is : SHOW STATUS LIKE 'wsrep_%' at org.mariadb.jdbc.internal.util.ExceptionMapper.get(ExceptionMapper.java:132) at org.mariadb.jdbc.internal.util.ExceptionMapper.getException(ExceptionMapper.java:101) at org.mariadb.jdbc.internal.util.ExceptionMapper.throwAndLogException(ExceptionMapper.java:77) at org.mariadb.jdbc.MariaDbStatement.executeQueryEpilog(MariaDbStatement.java:224) at org.mariadb.jdbc.MariaDbStatement.executeInternal(MariaDbStatement.java:258) at org.mariadb.jdbc.MariaDbStatement.executeQuery(MariaDbStatement.java:371) at com.verizon.mesos.Dbcheck.getStatus(Dbcheck.java:153) at com.verizon.mesos.Dbcheck.run(Dbcheck.java:103) at com.verizon.mesos.MariadbTask.handleHealthCheck(MariadbTask.java:310) at com.verizon.mesos.MariadbTask.executeCmd(MariadbTask.java:384) at com.verizon.mesos.MariadbTask.run(MariadbTask.java:450) at com.verizon.mesos.ExecutorTask.executeCmd(ExecutorTask.java:50) at com.verizon.mesos.ExecutorTask.run(ExecutorTask.java:115) at java.lang.Thread.run(Thread.java:745)

2 4

[Maria-discuss] MariaDB 10.2.3 and 5.5.54 now available
by Daniel Bartholomew 24 Dec '16

24 Dec '16

The MariaDB project is pleased to announce the immediate availability of MariaDB 10.2.3 beta and MariaDB 5.5.54 stable (GA). See the Release Notes and Changelogs for details. - - Links - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - MariaDB 10.2.3 - Release Notes: https://mariadb.com/kb/en/mdb-1023-rn/ - Changelog: https://mariadb.com/kb/en/mdb-1023-cl/ - Downloads: https://downloads.mariadb.org/mariadb/10.2.3 About MariaDB 10.2: - https://mariadb.com/kb/en/what-is-mariadb-102/ APT and YUM Repository Configuration Generator: - https://downloads.mariadb.org/mariadb/repositories/ MariaDB 5.5.54 - Release Notes: https://mariadb.com/kb/en/mdb-5554-rn/ - Changelog: https://mariadb.com/kb/en/mdb-5554-cl/ - Downloads: https://downloads.mariadb.org/mariadb/5.5.54 About MariaDB 5.5: - https://mariadb.com/kb/en/what-is-mariadb-55/ APT and YUM Repository Configuration Generator: - https://downloads.mariadb.org/mariadb/repositories/ - - MariaDB Webinars - - - - - - - - - - - - - - - - - - - - - - - - - There are several upcoming MariaDB-focused webinars and many previously held ones available to watch on an on-demand basis at: - https://mariadb.com/news-events/webinars - - MariaDB Books - - - - - - - - - - - - - - - - - - - - - - - - - - There is an ever-growing library of MariaDB books available to help you get the most out of MariaDB. See the MariaDB Books page for details and links: - https://mariadb.com/kb/en/mariadb/books/ - - 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 or my.ini file! See http://mariadb.com/kb/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 the MariaDB Foundation, please see the "contributing" and "donations" pages. We also have merchandise available in a cafepress store. All proceeds go to support the MariaDB Foundation. - https://mariadb.com/kb/en/contributing - https://mariadb.org/donate/ We hope you enjoy MariaDB! -- MariaDB Website - http://mariadb.org Twitter - http://twitter.com/mariadbfdn - http://twitter.com/mariadb Google+ - http://google.com/+mariadb Facebook - http://fb.com/MariaDB.dbms Knowledge Base - http://mariadb.com/kb

1 0

[Maria-discuss] aria engine error
by Roberto Spadim 22 Dec '16

22 Dec '16

hi guys i got a crash and aria engine don't startup, any help? 161222 03:41:13 mysqld_safe Starting mysqld daemon with databases from /home/mysql/data/local/ 2016-12-22 3:41:13 139878188566400 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release. 2016-12-22 3:41:13 139878188566400 [Note] /usr/mariadb/mariadb/bin//mysqld (mysqld 10.1.5-MariaDB-log) starting as process 19217 ... 2016-12-22 3:41:13 139878188566400 [Note] mysqld: Aria engine: starting recovery recovered pages: 0% 3082852397% 0%161222 3:41:13 [ERROR] mysqld got signal 11 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. To report this bug, see http://kb.askmonty.org/en/reporting-bugs We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. Server version: 10.1.5-MariaDB-log key_buffer_size=629145600 read_buffer_size=4194304 max_used_connections=0 max_threads=52 thread_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1041422 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0x0 thread_stack 0x48000 mysys/stacktrace.c:247(my_print_stacktrace)[0x7f37ee645b0b] sql/signal_handler.cc:153(handle_fatal_signal)[0x7f37ee1dfdb5] /lib64/libpthread.so.0(+0x10d00)[0x7f37ecd72d00] maria/ma_recovery.c:2142(exec_REDO_LOGREC_CLR_END)[0x7f37ee5683b7] maria/ma_recovery.c:588(display_and_apply_record)[0x7f37ee56985d] maria/ma_recovery.c:350(maria_apply_log)[0x7f37ee56d45c] maria/ma_recovery.c:242(maria_recovery_from_log)[0x7f37ee56df1e] maria/ha_maria.cc:3594(ha_maria_init)[0x7f37ee546c2d] sql/handler.cc:512(ha_initialize_handlerton(st_plugin_int*))[0x7f37ee1e2518] sql/sql_plugin.cc:1403(plugin_initialize)[0x7f37ee089e65] sql/sql_plugin.cc:1675(plugin_init(int*, char**, int))[0x7f37ee08add2] sql/mysqld.cc:5064(init_server_components)[0x7f37edfc37e8] sql/mysqld.cc:5659(mysqld_main(int, char**))[0x7f37edfc61ca] /lib64/libc.so.6(__libc_start_main+0xf0)[0x7f37ec3a79f0] /usr/mariadb/mariadb/bin//mysqld(+0x39dbad)[0x7f37edfbabad]

1 2

[Maria-discuss] restore problem with xtrabackup
by l vic 21 Dec '16

21 Dec '16

i have installed mariadb 1.10.13 cluster with user "root", password "pass" I have created test database "galeratest": CREATE DATABASE galeratest;USE galeratest;CREATE TABLE test_table ( id INT PRIMARY KEY AUTO_INCREMENT, msg TEXT ) ENGINE=InnoDB;INSERT INTO test_table (msg) VALUES ("Hello cluster."); backup: xtrabackup --user=root --password=pass --backup --target-dir=/media 161219 21:06:00 version_check Connecting to MySQL server with DSN 'dbi:mysql:;mysql_read_default_group=xtrabackup;port=3306;mysql_socket=/var/run/mysqld/mysqld.sock' as 'root' (using password: YES). 161219 21:06:00 version_check Connected to MySQL server 161219 21:06:00 version_check Executing a version check against the server... ... ok .. At this point i drop my database : DROP DATABASE galeratest; and trying to restore: xtrabackup --user=root --password=pass --prepare --target-dir=/media cd /media/ rsync -rvt --exclude 'xtrabackup_checkpoints' --exclude 'xtrabackup_logfile' \ ./ /var/lib/mysql chown -R mysql:mysql /var/lib/mysql/ MariaDB [galeratest]> show tables; +----------------------+ | Tables_in_galeratest | +----------------------+ | test_table | +----------------------+ 1 row in set (0.00 sec) MariaDB [galeratest]> select * from test_table; *ERROR 1932 (42S02): Table 'galeratest.test_table' doesn't exist in engine* *Any idea what the problem is? * Thanks,

2 2

[Maria-discuss] MariaDB 10.1.20 now available
by Daniel Bartholomew 15 Dec '16

15 Dec '16

The MariaDB project is pleased to announce the immediate availability of MariaDB 10.1.20. This is a stable (GA) release. See the Release Notes and Changelog for details. - - Links - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - MariaDB 10.1.20 - Release Notes: https://mariadb.com/kb/en/mdb-10120-rn/ - Changelog: https://mariadb.com/kb/en/mdb-10120-cl/ - Downloads: https://downloads.mariadb.org/mariadb/10.1.20 About MariaDB 10.1: - https://mariadb.com/kb/en/what-is-mariadb-101/ APT and YUM Repository Configuration Generator: - https://downloads.mariadb.org/mariadb/repositories/ - - MariaDB Webinars - - - - - - - - - - - - - - - - - - - - - - - - - There are several upcoming MariaDB-focused webinars and many previously held ones available to watch on an on-demand basis at: - https://mariadb.com/news-events/webinars - - MariaDB Books - - - - - - - - - - - - - - - - - - - - - - - - - - There is an ever-growing library of MariaDB books available to help you get the most out of MariaDB. See the MariaDB Books page for details and links: - https://mariadb.com/kb/en/mariadb/books/ - - 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 or my.ini file! See http://mariadb.com/kb/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 the MariaDB Foundation, please see the "contributing" and "donations" pages. We also have merchandise available in a cafepress store. All proceeds go to support the MariaDB Foundation. - https://mariadb.com/kb/en/contributing - https://mariadb.org/donate/ We hope you enjoy MariaDB! -- MariaDB Website - http://mariadb.org Twitter - http://twitter.com/mariadbfdn - http://twitter.com/mariadb Google+ - http://google.com/+mariadb Facebook - http://fb.com/MariaDB.dbms Knowledge Base - http://mariadb.com/kb

1 0