The following features have been added to MySQL 5.7:

The backup files created by the mysqldump utility are basically a set of SQL statements that can be used to recreate the original database. The mysqldump command can also generate files in CSV and XML format.

You can also use the mysqldump utility to transfer your MySQL database to another MySQL server.

If you don't backup your databases, a software bug or a hard-drive failure could be disastrous. To help save you lots of time and frustration, it is strongly recommended that you take the precaution of regularly backing up your MySQL databases.

Mysqldump Command Syntax

Before going into how to use the mysqldump command, let's start by reviewing the basic syntax.

The mysqldump utility expressions take the following form:

mysqldump [options] > file.sql

• options - The mysqldump options
• file.sql - The dump (backup) file

To use the mysqldump command the MySQL server must be accessible and running.

Backup a Single MySQL Database

The most common use case of the mysqldump tool is to backup a single database.

For example, to create a backup of the database named database_name using the user root and save it to a file named database_name.sql you would run the following command:

mysqldump -u root -p database_name > database_name.sql

You will be prompted to enter the root password. After successful authentication, the dump process will start. Depending on the database size, the process can take some time.

If you are logged in as the same user that you are using to perform the export and that user does not require a password, you can omit the -u and -p options:

mysqldump database_name > database_name.sql

Backup Multiple MySQL Databases

To backup multiple MySQL databases with one command you need to use the --database option followed by the list of databases you want to backup. Each database name must be separated by space.

mysqldump -u root -p --databases database_name_a database_name_b > databases_a_b.sql

The command above will create a dump file containing both databases.

Backup All MySQL Databases

Use the --all-databases option to back up all the MySQL databases:

mysqldump -u root -p --all-databases > all_databases.sql

Same as with the previous example the command above will create a single dump file containing all the databases.

Backup all MySQL databases to separate files

The mysqldump utility doesn't provide an option to backup all databases to separate files but we easily achieve that with a simple bash FOR loop:

for DB in $(mysql -e 'show databases' -s --skip-column-names); do
    mysqldump $DB > "$DB.sql";
done

The command above will create a separate dump file for each database using the database name as the filename.

Create a Compressed MySQL Database Backup

If the database size is very large it is a good idea to compress the output. To do that simply pipe the output to the gzip utility, and redirect it to a file as shown below:

mysqldump database_name | gzip > database_name.sql.gz

Create a Backup with Timestamp

If you want to keep more than one backup in the same location, then you can add the current date to the backup filename:

mysqldump  database_name > database_name-$(date +%Y%m%d).sql

The command above will create a file with the following format database_name-20180617.sql

Restoring a MySQL dump

You can restore a MySQL dump using the mysql tool. The command general syntax is as follows:

mysqld  database_name < file.sql

In most cases you'll need to create a database to import into. If the database already exists, first you need to delete it.

In the following example the first command will create a database named database_name and then it will import the dump database_name.sql into it:

mysql -u root -p -e "create database database_name";mysql -u root -p database_name < database_name.sql

Restore a Single MySQL Database from a Full MySQL Dump

If you backed up all your databases using the -all-databases option and you want to restore a single database from a backup file which contains multiple databases use the --one-database option as shown below:

mysql --one-database database_name < all_databases.sql

Export and Import a MySQL Database in One Command

Instead of creating a dump file from one database and then import the backup into another MySQL database you can use the following one-liner:

mysqldump -u root -p database_name | mysql -h remote_host -u root -p remote_database_name

The command above will pipe the output to a mysql client on the remote host and it will import it into a database named remote_database_name. Before running the command, make sure the database already exists on the remote server.

Automate Backups with Cron

Automating the process of backing up the databases is as simple as creating a cron job what will run the mysqldump command at specified time.

To set up automated backups of a MySQL database using cronjob, follow the steps below:

1. Create a file named .my.cnf in your user home directory:

   sudo nano ~/.my.cnf

   Copy and paste the following text into the .my.cnf file.

   [client]
   user = dbuser
   password = dbpasswd

   Copy

   Do not forget to replace dbuser and dbpasswdwith the database user and user's password.

2. Restrict permissions of the credentials file so that only your user has access to it:

   chmod 600 ~/.my.cnf

3. Create a directory to store the backups:

   mkdir ~/db_backups

4. Open your user crontab file:

   crontab -e

   Add the following cron job that will create a backup of a database name mydb every day at 3am:

   0 3 * * * /usr/bin/mysqldump -u dbuser mydb > /home/username/db_backups/mydb-$(date +%Y%m%d).sql

   Do not forget to replace username with your actual user name.

You can also create another cronjob to delete any backups older than 30 days:

find /path/to/backups -type f -name "*.sql" -mtime +30 -delete

Of course, you need to adjust the command according to your backup location and file names. To learn more about the find command check our How to Find Files in Linux Using the Command Line guide.

Conclusion

This tutorial covers only the basics, but it should be a good starting for anyone who wants to learn how to create and restore MySQL databases from the command line using the mysqldump utility.

mysql_full_unicode_support#File_format
this test must pass

Your database uses Antelope as the file format. Full UTF-8 support in MySQL and MariaDB requires the Barracuda file format. Please switch to the Barracuda file format. See the documentation MySQL full unicode support for details.
Check
mysql_full_unicode_support#Large_prefix
this test must pass

For full support of UTF-8 both MySQL and MariaDB require you to change your MySQL setting 'innodb_large_prefix' to 'ON'. See the documentation for further details.

[/code[

in that case there are various approaches to a solution

[mysqld]
innodb_file_format = Barracuda
innodb_large_prefix = 1
innodb_file_per_table = ON

https://stackoverflow.com/questions/35847015/mysql-change-innodb-large-prefix

Here is what we were trying to do: copy the production database to the staging database so we could properly configure and test everything before pushing the new site live. Pretty simple right? It was, until we noticed a bunch of weird character encoding issues on the staging site.

It turned out that while the database tables were set to a Latin-1 (latin1), the content that populated those tables was encoded as UTF-8 (utf8). A variety of attempts to fix this failed, but what succeeded was as follows:

1. Export the data as Latin-1. Because MySQL knows that the table is already using a Latin-1 encoding, it will do a straight export of the data without trying to convert the data to another character set. If you try to export as UTF-8, MySQL appears to attempt to convert the (supposedly) Latin-1 data to UTF-8 – resulting in double encoded characters (since the data was actually already UTF-8).
2. Change the character set in the exported data file from ‘latin1’ to ‘utf8’. Since the dumped data was not converted during the export process, it’s actually UTF-8 encoded data.
3. Create your new table as UTF-8 If your CREATE TABLE command is in your SQL dump file, change the character set from ‘latin1’ to ‘utf8’.
4. Import your data normally. Since you’ve got UTF-8 encoded data in your dump file, the declared character set in the dump file is now UTF-8, and the table you’re importing into is UTF-8, everything will go smoothly.

I can confirm that a half-dozen or so variations on the above do not work. This includes INSERT INTO newdb.newtable SELECT * FROM olddb.oldtable;.

Also, if you’re doing this for a WordPress¹ site (like we were), keep in mind that copying over the production database will generally mean that WP-Cache is enabled. You’ll want to remember to turn that off. Yeah.

1. This is a fairly common issue in older WordPress installs because the MySQL database default is commonly Latin-1, and older versions of WordPress did not specify the character set when creating the database tables (so they would default to Latin-1) and the default encoding in the WordPress settings is UTF-8. [back]

http://alexking.org/blog/2008/03/06/mysql-latin1-utf8-conversion

https://stackoverflow.com/questions/42385099/1273-unknown-collation-utf8mb4-unicode-520-ci

MariaDB 10.1.33 is a Stable (GA) release.

For an overview of MariaDB 10.1 see the What is MariaDB 10.1? page.

Notable Changes

• PCRE updated to 8.42
• The embedded server library now supports SSL when connecting to remote servers.
• ALTER TABLE fixes: MDEV-14693, MDEV-16080, MDEV-15937
• encryption fixes: MDEV-15937, MDEV-16092, MDEV-15752, MDEV-15566
• systemd and shutdown fixes: MDEV-14705
• As per the MariaDB Deprecation Policy, this will be the last release of MariaDB 10.1 for Debian 7 Wheezy
• In this release experimental Ubuntu 18.04 "bionic" packages are present in the MariaDB 10.1 repository. However, because Ubuntu includes MariaDB 10.1 in its main repositories we recommend using the Ubuntu provided MariaDB 10.1 packages for general use.

Security Fixes
Fixes for the following security vulnerabilities:

• CVE-2018-2782
• CVE-2018-2784
• CVE-2018-2787
• CVE-2018-2766
• CVE-2018-2755
• CVE-2018-2819
• CVE-2018-2817
• CVE-2018-2761
• CVE-2018-2781
• CVE-2018-2771
• CVE-2018-2813

https://mariadb.org/mariadb-10-1-33-and-mariadb-galera-cluster-10-0-35-now-available/

MySQL adds NoSQL and many new enhancements to the world’s most popular open source database:

1. NoSQL Document Store gives developers the flexibility of developing traditional SQL relational applications and NoSQL, schema-free document database applications. This eliminates the need for a separate NoSQL document database.
2. SQL Window functions, Common Table Expressions, NOWAIT and SKIP LOCKED, Descending Indexes, Grouping, Regular Expressions, Character Sets, Cost Model, and Histograms.
3. JSON Extended syntax, new functions, improved sorting, and partial updates. With JSON table functions you can use the SQL machinery for JSON data.
4. GIS Geography support. Spatial Reference Systems (SRS), as well as SRS aware spatial datatypes, spatial indexes, and spatial functions.
5. Reliability DDL statements have become atomic and crash safe, meta-data is stored in a single, transactional data dictionary
6. Observability Performance Schema, Information Schema, Invisible Indexes, Error Logging.
7. Manageability Persistent Configuration Variables, Undo tablespace management, Restart command, and New DDL.
8. High Availability InnoDB Cluster delivers an integrated, native, HA solution for your databases.
9. Security OpenSSL improvements, new default authentication, SQL Roles, breaking up the super privilege, password strength, authorization.
10. Performance Up to 2x faster than MySQL 5.7.

Observability
Information Schema (speed up)

MySQL 8.0 reimplements Information Schema. In the new implementation the Information Schema tables are simple views on data dictionary tables stored in InnoDB. This is by far more efficient than the old implementation with up to 100 times speedup.

Performance Schema (speed up)

MySQL 8.0 speeds up performance schema queries by adding more than 100 indexes on performance schema tables.

Security features
OpenSSL by Default in Community Edition

MySQL 8.0 is unifying on OpenSSL as the default TLS/SSL library for both MySQL Enterprise Edition and MySQL Community Edition. 

SQL roles

Performance
MySQL 8.0 is up to 2x faster than MySQL 5.7. MySQL 8.0 comes with better performance for Read/Write workloads, IO bound workloads, and high contention “hot spot” workloads.

MySQL 8.0 implements SQL Roles. A role is a named collection of privileges. The purpose is to simplify the user access right management. One can grant roles to users, grant privileges to roles, create roles, drop roles, and decide what roles are applicable during a session.

Scaling Read/Write Workloads

MySQL 8.0 scales well on RW and heavy write workloads. On intensive RW workloads we observe better performance already from 4 concurrent users and more than 2 times better performance on high loads comparing to MySQL 5.7. We can say that while 5.7 significantly improved scalability for Read Only workloads, 8.0 significantly improves scalability for Read/Write workloads. The effect is that MySQL improves hardware utilization (efficiency) for standard server side hardware (like systems with 2 CPU sockets). This improvement is due to re-designing how InnoDB writes to the REDO log. In contrast to the historical implementation where user threads were constantly fighting to log their data changes, in the new REDO log solution user threads are now lock-free, REDO writing and flushing is managed by dedicated background threads, and the whole REDO processing becomes event-driven.

Better Performance upon High Contention Loads (“hot rows”)

MySQL 8.0 significantly improves the performance for high contention workloads. A high contention workload occurs when multiple transactions are waiting for a lock on the same row in a table, causing queues of waiting transactions. Many real world workloads are not smooth over for example a day but might have bursts at certain hours. MySQL 8.0 deals much better with such bursts both in terms of transactions per second, mean latency, and 95th percentile latency. The benefit to the end user is better hardware utilization (efficiency) because the system needs less spare capacity and can thus run with a higher average load.

https://mariadb.org/mariadb-10-2-14-mariadb-10-1-32-and-mariadb-connector-j-2-2-3-and-1-7-3-now-available/

Εκει η διαδικασία λογικά σταματά νωρίς με κάτι τέτοιο:

"ERROR 1050 (42S01) at line χχ: Table 'db_table' already exists"

αντί να κάνουμε DROP την βάση / recreate και ξανά recreate user connections υπάρχει και το ακόλουθο που παράγει όλα τα DROP statements για κάθε πίνακα της βασης:

SELECT CONCAT('DROP TABLE ', TABLE_NAME, ';')
FROM INFORMATION_SCHEMA.tables
WHERE TABLE_SCHEMA = '{database name}';

θα δείτε κάτι τέτοιο ( παράδειγμα από WP )

+----------------------------------------+
| CONCAT('DROP TABLE ', TABLE_NAME, ';') |
+----------------------------------------+
| DROP TABLE wpdbase_commentmeta;            |
| DROP TABLE wpdbase_comments;               |
| DROP TABLE wpdbase_links;                  |
| DROP TABLE wpdbase_options;                |
| DROP TABLE wpdbase_pmxi_history;           |
| DROP TABLE wpdbase_postmeta;               |
| DROP TABLE wpdbase_posts;                  |
| DROP TABLE wpdbase_term_relationships;     |
| DROP TABLE wpdbase_term_taxonomy;          |
| DROP TABLE wpdbase_termmeta;               |
| DROP TABLE wpdbase_terms;                  |
| DROP TABLE wpdbase_usermeta;               |
| DROP TABLE wpdbase_users;                  |
| DROP TABLE wpdbase_wysija_campaign;        |
| DROP TABLE wpdbase_wysija_campaign_list;   |
| DROP TABLE wpdbase_wysija_custom_field;    |
| DROP TABLE wpdbase_wysija_email;           |
| DROP TABLE wpdbase_wysija_email_user_stat; |
| DROP TABLE wpdbase_wysija_email_user_url;  |
| DROP TABLE wpdbase_wysija_form;            |
| DROP TABLE wpdbase_wysija_list;            |
| DROP TABLE wpdbase_wysija_queue;           |
| DROP TABLE wpdbase_wysija_url;             |
| DROP TABLE wpdbase_wysija_url_mail;        |
| DROP TABLE wpdbase_wysija_user;            |
| DROP TABLE wpdbase_wysija_user_field;      |
| DROP TABLE wpdbase_wysija_user_history;    |
| DROP TABLE wpdbase_wysija_user_list;       |
+----------------------------------------+
28 rows in set (0.00 sec)

και εύκολα μετα προχωράτε σε διαγραφή τους με ένα απλό copy paste

εχω βρει και άλλες λύσεις και σίγουρα θα υπάρχει και καλύτερη

http://stackoverflow.com/questions/27606518/how-to-drop-all-tables-from-a-database-with-one-sql-query

http://stackoverflow.com/questions/536350/drop-all-the-tables-stored-procedures-triggers-constraints-and-all-the-depend

http://stackoverflow.com/questions/11053116/mysql-bulk-drop-table-where-table-like

Check repair and optimize all SQL databases

mysqlcheck --all-databases -r #repair

mysqlcheck --all-databases -a #analyze

mysqlcheck --all-databases -o #optimize

    Useful! You can copy this code in a new .sh file and use it as a script, or even automate the optimisation using Cron

• XtraDB updated to 5.6.34-79.1
• TokuDB updated to 5.6.34-79.1
• HeidiSQL updated to 9.4
• The limit for the table_open_cache system variable has been increased to 1024K
• Galera wsrep library updated to 25.3.19
• packages for Debian 9 "stretch" amd64 and Debian 8 "jessie" ppc64el added

• Revision #c13b501 2016-12-14 19:20:17 +0000
  • Fix broken cmake -DBUILD_CONFIG=mysql_release on Windows.
• Revision #d93bbca 2016-12-14 20:13:36 +0530
  • MDEV-11479 Improved wsrep_dirty_reads - Updated sysvars_wsrep.result file
• Revision #f41bd7e 2016-12-13 05:07:02 +0530
  • MDEV-11060 sql/protocol.cc:532: void Protocol::end_statement(): Assertion `0' failed
• Revision #0c79de2 2016-12-14 09:30:43 +0530
  • MDEV-11479 Improved wsrep_dirty_reads
• Revision #25a9a3d 2016-12-14 08:39:36 +0530
  • Revert "MDEV-11016 wsrep_node_is_ready() check is too strict"
• Revision #72cc73c 2016-12-13 11:51:33 +0200
  • MDEV-10368: get_latest_version() called too often
• Revision #67b570a 2016-12-05 20:58:49 -0500
  • MDEV-10545: Server crashed in my_copy_fix_mb on querying I_S and P_S tables
• Revision #9c88a54 2016-12-05 20:07:30 -0500
  • MDEV-11179: WSREP transaction excceded size limit in Galera cluster
• Revision #dbb06d2 2016-11-21 19:44:48 -0500
  • MDEV-10954: MariaDB Galera: wsrep_sst_common: line 120: which: command not found
• Revision #5d9ca52 2016-12-12 00:59:40 +0200
  • Updated the list of unstable tests after the merge
• Revision #2f20d29 2016-12-11 09:53:42 +0100 - Merge branch '10.0' into 10.1
• Revision #eb4f2e0 2016-12-10 22:19:09 +0200
  • MDEV-11533: Roles with trailing white spaces are not cleared correctly
• Revision #3e8155c 2016-12-09 16:33:48 +0100 - Merge branch '5.5' into 10.0
• Revision #03dabfa 2016-12-08 22:54:58 +0100
  • MDEV-10713: signal 11 error on multi-table update - crash in handler::increment_statistics or in make_select or assertion failure pfs_thread == ((PFS_thread*) pthread_getspecific((THR_PFS)))
• Revision #ab65db6 2016-12-08 21:03:45 +0100
  • Revert "MDEV-10713: signal 11 error on multi-table update - crash in handler::increment_statistics or in make_select or assertion failure pfs_thread == ((PFS_thread*) pthread_getspecific((THR_PFS)))"
• Revision #f5e0522 2016-12-07 13:06:14 +0100
  • MDEV-10388 MariaDB 10.1.x keeps (deleted) ML* files in tmpdir after LOAD DATA completes
• Revision #1d702ff 2016-12-07 14:42:08 +0400
  • MDEV-8329 MariaDB crashes when replicate_wild_ignore_table is set to NULL.
• Revision #d67ef7a 2016-12-05 17:37:54 +0100
  • MDEV-10663: Use of Inline table columns in HAVING clause throws 1463 Error
• Revision #035a5ac 2016-09-26 18:15:11 +0200
  • MDEV-10713: signal 11 error on multi-table update - crash in handler::increment_statistics or in make_select or assertion failure pfs_thread == ((PFS_thread*) pthread_getspecific((THR_PFS)))
• Revision #f988bce 2016-09-21 18:36:34 +0200
  • MDEV-10776: Server crash on query
• Revision #46dee0d 2016-12-05 16:50:12 +0400
  • MDEV-10717 Assertion `!null_value' failed in virtual bool Item::send(Protocol*, String*)
• Revision #18cdff6 2016-12-04 12:37:01 +0100
  • MDEV-10293 'setupterm' was not declared in this scope
• Revision #02d153c 2016-06-26 13:37:27 +0200
  • str2decimal: don't return a negative zero
• Revision #4a3acbc 2016-12-02 00:19:49 +0100
  • MDEV-11241 Certain combining marks cause MariaDB to crash when doing Full-Text searches
• Revision #0a4b508 2016-12-01 20:04:36 +0100
  • MDEV-11242 MariaDB Server releases contains promotion of MariaDB Corporation
• Revision #f640527 2016-12-02 15:22:11 +0100
  • typo fixed: s/MSYQL/MYSQL/
• Revision #9976223 2016-11-28 17:28:37 +0400
  • MDEV-11171 Assertion `m_cpp_buf <= ptr && ptr <= m_cpp_buf + m_buf_length' failed in Lex_input_stream::body_utf8_append(const char*, const char*)
• Revision #adc38ed 2016-11-14 08:02:35 +0100
  • Restore MY_WME flag for my_pread in read_ddl_log_entry, fix errors in buildbot
• Revision #96b62b5 2016-11-11 20:55:03 -0800
  • Fixed bug MDEV-11161. The flag TABLE_LIST::fill_me must be reset to false at the prepare phase for any materialized derived table used in the executed query. Otherwise if the optimizer decides to generate a key for such a table it is generated only for the first execution of the query.
• Revision #10aee66 2016-11-10 23:47:42 +0000
  • MDEV-11248 Fix passing offset parameter to my_file_pread in read_ddl_log_file_entry
• Revision #e0f48e5 2016-11-03 16:21:48 +0000
  • MDEV-11214 Windows : MSI installation fails, if run by a service user (e.g LocalSystem)
• Revision #2a2e79b 2016-10-27 13:03:49 +0000
  • MDEV-11157 Windows - Upgrade installer to use HeidiSQL 9.4
• Revision #d8cb682 2016-10-26 21:54:41 +0000
  • VS2015 build fixes
• Revision #aec4321 2016-10-26 21:38:58 +0000
  • MDEV-9409 Windows - workaround VS2015 CRT bug that makes mysqldump/mysql_install_db.exe fail
• Revision #106664f 2016-12-08 02:03:34 +0530
  • MDEV-11162 Assertion `num_records == m_idx_array.size()' failed in Filesort_buffer::alloc_sort_buffer(uint, uint)
• Revision #822fb79 2016-12-07 23:44:52 +0530
  • MDEV-11162 Assertion `num_records == m_idx_array.size()' failed in Filesort_buffer::alloc_sort_buffer(uint, uint)
• Revision #c32d3e1 2016-12-07 18:05:13 +0400
  • MDEV-10787 Assertion `ltime->neg == 0' failed in void date_to_datetime(MYSQL_TIME*)
• Revision #52b590b 2016-12-07 10:04:10 +0400 - Merge pull request #271 from iangilfillan/10.0
• Revision #3ada316969 2016-12-06 13:18:48 +0200
  • Update mysqldump man page
• Revision #7f2fd34 2016-12-02 14:34:45 +0100
  • MDEV-11231 Server crashes in check_duplicate_key on CREATE TABLE ... SELECT
• Revision #c5ef621 2016-12-04 01:59:08 +0100 - Merge branch 'merge/merge-tokudb-5.6' into 10.0
• Revision #d4f0686 2016-12-02 10:24:00 +0100
  • 5.6.34-79.1
• Revision #f35b0d8 2016-12-04 01:37:55 +0100 - Merge branch 'merge/merge-xtradb-5.6' into 10.0
• Revision #7436c3d 2016-12-02 10:22:18 +0100
  • 5.6.34-79.1
• Revision #e4a0d75 2016-12-04 01:35:57 +0100
  • import a test case from percona-server-5.6.34-79.1
• Revision #e99990c 2016-10-28 17:10:05 +0200
  • MDEV-10744: Roles are not fully case sensitive
• Revision #525e214 2016-10-25 16:47:36 +0200
  • Remove labs() warning from maria and myisam storage engines
• Revision #748d993 2016-11-29 11:28:15 -0800
  • Fixed bug MDEV-11364. The function Item_func_isnull::update_used_tables() must handle the case when the predicate is over not nullable column in a special way. This is actually a bug of MariaDB 5.3/5.5, but it's probably hard to demonstrate that it can cause problems there.
• Revision #b209bc3 2016-11-29 09:01:46 +0200
  • MDEV-10427: innodb.innodb-wl5522-debug-zip fails sporadically in buildbot
• Revision #dd0ff30 2016-11-29 06:51:12 +0400
  • MDEV-11343 LOAD DATA INFILE fails to load data with an escape character followed by a multi-byte character
• Revision #099ce1d 2016-11-25 15:59:47 +0400
  • MDEV-11348 LOAD DATA LOCAL INFILE crashes the server on loading a backslash followed by a multi-byte character
• Revision #03ddc19 2016-11-17 15:15:20 +0200
  • MDEV-6424: MariaDB server crashes with assertion failure in file ha_innodb.c line 11652
• Revision #42a398b 2016-11-17 12:04:39 +0400
  • Fixing a typo in the patch for MDEV-10780, which caused default.test failure.
• Revision #390f2a0 2016-11-16 11:00:38 +0100
  • Fix incorrect reading of events from relaylog in parallel replication.
• Revision #f1fcc1f 2016-11-15 23:00:11 +0100
  • Back-port Master_info::using_parallel() to 10.0.
• Revision #9a09072 2016-11-15 11:08:01 +0100 - Merge branch 'mdev10863' into 10.0
• Revision #1d9b043 2016-11-10 18:15:36 +0400
  • A join patch for MDEV-10780 and MDEV-11265
• Revision #9741e0e 2016-11-01 07:52:28 +0200
  • Initialize zip_dict_ids table and avoid referencing array items as currently MariaDB does not support compressed columns.
• Revision #923a7f8 2016-10-31 12:16:53 +0200
  • MDEV-11188: rpl.rpl_parallel_partition fails with valgrind warnings in buildbot and outside
• Revision #425d341 2016-10-28 11:46:15 -0400
  • bump the VERSION
• Revision #cb7b03b 2016-10-28 13:34:13 +0400
  • MDEV-11164 - hardening-wrapper has been removed from Debian Sid
• Revision #a629b51 2016-12-10 23:04:41 +0200
  • Updated the list of unstable tests
• Revision #83f7151 2016-12-09 17:13:43 +0400
  • MDEV-10435 crash with bad stat tables.
• Revision #870d758 2016-12-08 20:49:54 +0200
  • MDEV-11491 binlog_encryption.rpl_checksum fails sporadically in buildbot
• Revision #8e702bc 2016-12-08 17:05:01 +0200
  • MDEV-11504 binlog_encryption.encrypted_master_switch_to_unencrypted fails sporadically in buildbot
• Revision #e1e1fbc 2016-12-07 14:05:04 +0400 - Merge pull request #272 from iangilfillan/10.1
• Revision #63edd27 2016-12-07 11:58:40 +0200
  • Update mysqld_multi man page
• Revision #2114aa4 2016-12-07 13:37:16 +0400 - Merge pull request #270 from JRonak/MDEV-11354
• Revision #d036be7 2016-12-06 02:29:52 +0530
  • fixes MDEV-11354 twin include
• Revision #74d52de 2016-12-05 22:29:25 +0100
  • fix binlog_encryption.binlog_incident test
• Revision #76546a0 2016-12-05 15:51:24 +0100
  • MDEV-10382 Using systemd, mariadb doesn't restart on crashes
• Revision #5142cd5 2016-12-04 21:19:32 +0100
  • MDEV-11052 mariadb-service-convert does not work after upgrading to 10.1.18
• Revision #b5aa0f4 2016-12-03 20:34:50 +0100
  • MDEV-11319 mysqlbinlog crashes or fails with out of memory while reading some encrypted binlogs
• Revision #952856c 2016-12-03 20:26:42 +0100
  • MDEV-11288 Server crashes in Binlog_crypt_data::init trying to feed encrypted log without decryption capabilities
• Revision #611f916 2016-12-05 20:19:01 +0200
  • MDEV-9038 Binlog encryption tests
• Revision #9199d72 2016-12-05 15:25:59 +0200
  • MDEV-11233 CREATE FULLTEXT INDEX with a token longer than 127 bytes crashes server
• Revision #ead6d0d 2016-12-05 03:13:28 +0200
  • Follow-up for MDEV-9451 - fix XtraDB rdiff files
• Revision #b0754ad 2016-12-05 03:11:42 +0200
  • Follow-up for MDEV-11429 - fix result files for embedded and 32-bit tests
• Revision #f1b80d8 2016-12-02 16:25:47 +0200
  • MDEV-11236 Failing assertion: state == TRX_STATE_NOT_STARTED
• Revision #1e7f961 2016-12-01 14:56:09 +0200
  • MDEV-9451 innodb_buffer_pool_populate does not seem to work on 10.1.10
• Revision #97b21a1 2016-12-02 14:02:30 +0200
  • MDEV-10759 Fix Aria to support 2-byte collation IDs - Used same fix as for MyISAM: High level collation byte stored in unused bit_end position. - Moved language from header to base_info - Removed unused bit_end part in HA_KEY_SEG
• Revision #2996f9a 2016-11-30 18:36:29 +0200
  • MDEV-11429 Increase number of max table_open_cache instances
• Revision #2fd3af4 2016-12-01 13:45:23 -0500
  • MDEV-11168: InnoDB: Failing assertion: !other_lock || wsrep_thd_is_BF(lock->trx->mysql_thd, FALSE) || wsrep_thd_is_BF(other_lock->trx->mysql_thd, FALSE)
• Revision #dbdef41 2016-11-29 08:41:45 +0200
  • MDEV-10686: innodb_zip.innodb_prefix_index_liftedlimit failed with timeout in buildbot
• Revision #9f31949 2016-11-29 08:35:51 +0200
  • MDEV-10739: encryption.innodb-page_encryption_compression fails with timeout on valgrind
• Revision #e493c6b 2016-11-28 09:57:28 +0100 - Merge remote-tracking branch 'my/tokudb_optimistic_parallel_replication' into 10.1
• Revision #3bec0b3 2016-11-23 16:45:31 +0100
  • Parallel replication test case for TokuDB.
• Revision #021f78f 2016-11-23 16:44:03 +0100
  • Use thd_kill_level() over old thd_killed() in TokuDB.
• Revision #660a292 2016-11-23 16:46:33 +0100
  • Fix optimistic parallel replication for TokuDB.
• Revision #d145d1b 2016-11-23 12:29:38 +0100
  • fix bogus stalls in the lock tree for low concurrency applications
• Revision #a68d135 2016-11-25 06:28:02 +0200
  • MDEV-11349 (2/2) Fix some bogus-looking Valgrind warnings
• Revision #8da33e3 2016-11-25 06:09:00 +0200
  • MDEV-11349 (1/2) Fix some clang 4.0 warnings
• Revision #1d8eafb 2016-11-24 15:55:55 +0400
  • Removing the unused function my_bincmp() from strings/ctype-ucs2.c
• Revision #57058cb 2016-11-22 16:38:36 +0200
  • MDEV-10377: innodb.innodb_blob_truncate fails in buildbot: Failing assertion: page_type == 34354 || page_type == 37401 || page_type == 17855 || page_type == 2 || page_type == 3 || ...
• Revision #ee3c99d 2016-11-22 16:17:05 +0530 - Merge branch 'bb-MDEV-11016' into 10.1
• Revision #7ed5563 2016-10-26 14:52:24 +0530
  • MDEV-11016 wsrep_node_is_ready() check is too strict Problem:- The condition that checks for node readiness is too strict as it does not allow SELECTs even if these selects do not access any tables. For example,if we run SELECT 1; OR SELECT @@max_allowed_packet; Solution:- We need not to report this error when all_tables(lex->query_tables) is NULL:
• Revision #af05bec 2016-11-16 13:52:41 +0200
  • MDEV-10771: Test innodb_defragment_fill_factor does not work correctly
• Revision #bccd0b5 2016-11-15 13:10:21 +0100 - Merge branch 'mdev10863' into 10.1
• Revision #717f212 2016-11-04 12:33:42 +0100
  • MDEV-10863: parallel replication tries to continue from wrong position
• Revision #cf29e8c 2016-11-14 11:02:57 -0500
  • wsrep_info plugin: Fix test case
• Revision #1fee017 2016-11-09 15:23:25 +0200
  • MDEV-10692: InnoDB: Failing assertion: lock->trx->lock.wait_lock == lock When we enter here wait_lock could be already gone i.e. NULL, that should be allowed.
• Revision #6ae3dd6 2016-11-09 00:10:45 +0100
  • AWS Key management plugin does not build on Centos7.
• Revision #909e239 2016-11-07 10:51:35 -0500
  • bump the VERSION

Notable Changes

• XtraDB updated to 5.6.33-79.0
• TokuDB updated to 5.6.33-79.0

• Fixes for the following security vulnerabilities:
  • CVE-2016-7440
  • CVE-2016-5584

Release notes:

Release date: 7 Nov 2016

For the highlights of this release, see the release notes.

The revision number links will take you to the revision's page on GitHub. On GitHub you can view more details of the revision and view diffs of the code modified in that revision.

    Revision #5fda340 2016-11-04 14:04:24 +0300
        Remove galera suites from default list for now, tests are unstable 
    Revision #1ddd1b5 2016-11-04 13:41:26 +0300
        Add sphinx tests to the list, just in case they are run somewhere 
    Revision #ee0094d 2016-11-04 13:33:28 +0300
        MDEV-10985, MDEV-10986 - sphinx tests have not been maintained 
    Revision #cbfb3f9 2016-11-03 19:30:02 -0400
        Move disabled galera tests to galera/disabled.def 
    Revision #d34cd35 2016-11-03 22:07:31 +0400
        Disabling tests mentioned in MDEV-11229 galera.MW-258 galera.galera_as_master fail in buildbot 
    Revision #f0d8a4d 2016-11-03 22:02:24 +0400
        MDEV-11219 main.null fails in buldbot and outside with ps-protocol 
    Revision #82780a7 2016-11-02 21:20:00 +0300
        MDEV-11130 Update the list of unstable tests for 10.1 
    Revision #54d3dc0 2016-11-01 17:27:53 -0400
        Fix/disable some failing galera tests. 
    Revision #7a17020 2016-10-26 13:19:00 -0400
        MDEV-11152: wsrep_replicate_myisam: SELECT gets replicated using TO 
    Revision #07918b4 2016-10-10 14:02:37 -0400
        MDEV-10993: wsrep.mdev_10186 result depends on location of galera library 
    Revision #3daf89c 2016-10-05 04:24:07 -0400
        MDEV-10957: Assertion failure when dropping a myisam table with wsrep_replicate_myisam enabled 
    Revision #6dbfe7f 2016-10-03 12:02:46 -0400
        MDEV-10944: GALERA log-slave-updates FAIL after upgrading from 10.1.17 to 10.1.18 
    Revision #fa4fa0a 2016-09-30 21:13:03 -0400
        Make galera test suites default. 
    Revision #a52a68c 2016-07-13 16:17:08 -0400
        fix the tokudb_analyze_in_background_basic test to run on mariadb. mariadb does additional value checking for boolean system variables 
    Revision #110a9f0 2016-07-13 15:15:35 -0400
        add mtr support files for tokudb_sys_vars tests 
    Revision #c948559 2016-07-20 13:43:53 -0400
        MDEV-10408 run the tokudb_rpl.rpl_rfr_disable_on_expl_pk_absence test. Add control files. Fixup result file for mariadb 
    Revision #a98c85b 2016-11-02 13:44:07 +0100 - Merge branch '10.0-galera' into 10.1
    Revision #7196691 2016-11-01 17:20:12 -0400
        Fix/disable some failing galera tests. 
    Revision #5db2195 2016-10-28 15:50:13 -0400 - Merge tag 'mariadb-10.0.28' into 10.0-galera
    Revision #eca8c32 2016-10-27 19:07:55 +0200
        Typo fixed. 
    Revision #a079565 2016-10-27 12:23:31 +0200
        MDEV-10846 Running mysqldump backup twice returns error: Table 'mysql.proc' doesn't exist. 
    Revision #d451d77 2016-10-26 10:59:38 -0700
        Fixed bug MDEV-9628. In the function create_key_parts_for_pseudo_indexes() the key part structures of pseudo-indexes created for BLOB fields were set incorrectly. Also the key parts for long fields must be 'truncated' up to the maximum length acceptable for key parts. 
    Revision #9d4a0dd 2016-10-24 10:15:11 -0700
        Fixed bug MDEV-11096. 1. When min/max value is provided the null flag for it must be set to 0 in the bitmap Culumn_statistics::column_stat_nulls. 2. When the calculation of the selectivity of the range condition over a column requires min and max values for the column then we have to check that these values are provided. 
    Revision #26b87c3 2016-10-27 00:04:26 +0400
        MDEV-10846 Running mysqldump backup twice returns error: Table 'mysql.proc' doesn't exist. 
    Revision #22490a0 2016-10-26 13:26:43 +0200
        MDEV-8345 STOP SLAVE should not cause an ERROR to be logged to the error log 
    Revision #2593270 2016-10-26 12:30:18 +0200
        backport include/search_pattern_in_file.inc from 10.1 
    Revision #5569ac0 2016-10-25 15:08:15 +0300
        MDEV-11126: Crash while altering persistent virtual column 
    Revision #59a7bc3 2016-10-26 14:09:11 +0400
        Removed duplicate open_strategy assignments 
    Revision #a3c980b 2016-10-24 15:26:11 +0400
        MDEV-10824 - Crash in CREATE OR REPLACE TABLE t1 AS SELECT spfunc() 
    Revision #9155cc7 2016-08-31 15:57:02 +1000
        MDEV-10292: Tokudb - PerconaFT - compile error in recent gcc 
    Revision #ad5b88a 2016-10-26 09:26:34 +0000
        Fix build error in XtraDB on Windows. 
    Revision #bd4568a 2016-10-26 10:49:31 +0200 - Merge branch 'bb-10.0-serg' into 10.0
    Revision #2cfccbe 2016-10-25 21:59:06 +0200 - Merge branch 'connect/10.0' into 10.0
    Revision #b7aee7d 2016-10-14 18:29:33 +0200
        Fix MDEV-10950. Null values not retrieved for numeric types. Now the null is tested using the result set getObject method. 
    Revision #9b20d60 2016-10-05 23:44:54 +0200
        Fix MDEV-10948. Syntax error on quoted JDBC tables. Was because the quoting character was always '"' instead of being retrieve from the JDBC source. 
    Revision #7d596c9 2016-09-16 22:14:14 +0200
        Working on MDEV-10525. Lrecl mismatch on DBF files 
    Revision #2140dcf 2016-09-05 13:19:28 +0200 - Merge branch '10.0' of https://github.com/MariaDB/server into ob-10.0
    Revision #213765c 2016-09-05 13:18:04 +0200
        Fix MDEV-10496. Memory leak in discovery 
    Revision #de9ea40 2016-10-25 21:58:59 +0200 - Merge branch 'merge/merge-tokudb-5.6' into 10.0
    Revision #d9787aa 2016-10-25 17:03:23 +0200
        5.6.33-79.0 
    Revision #675f27b 2016-10-25 18:28:31 +0200 - Merge branch 'merge/merge-xtradb-5.6' into 10.0
    Revision #d7dc03a 2016-10-25 17:01:37 +0200
        5.6.33-79.0 
    Revision #12c3e16 2016-10-25 16:41:43 +0200 - Merge branch '5.5' into 10.0
    Revision #6e25727 2016-10-17 11:43:47 -0400
        bump the VERSION 
    Revision #df87be5 2016-10-17 14:04:45 +0300
        MDEV-11069 main.information_schema test fails if hostname includes 'user' 
    Revision #eac8d95 2016-10-14 12:51:53 +0200
        compilation warning after xtradb merge 
    Revision #5a43a31 2016-10-14 00:33:49 +0200
        mysqldump: comments and identifiers with new lines 
    Revision #01b39b7 2016-10-13 20:58:08 +0200
        mysqltest: don't eat new lines in --exec 
    Revision #383007c 2016-10-13 21:35:01 +0200
        mysql cli: fix USE command quoting 
    Revision #e4957de 2016-10-13 12:40:24 +0200 - Merge branch 'merge-xtradb-5.5' into 5.5
    Revision #6010a27 2016-10-13 12:23:16 +0200
        5.5.52-38.3 
    Revision #02be50a 2016-10-13 11:18:30 +0200 - Merge branch 'mysql/5.5' into 5.5
    Revision #82ab92b 2016-10-25 22:35:35 +0000
        MDEV-10951 Field_newdate::cmp access violation 
    Revision #ed3998a 2016-10-25 15:46:10 +0200
        Revert "Add tokuftdump man page" 
    Revision #1daf746 2016-10-25 16:34:22 +0300
        Add tokuftdump man page 
    Revision #39dceaa 2016-10-09 12:09:44 +0200
        MDEV-10983: TokuDB does not compile on OS X 10.12 
    Revision #ba11dd6 2016-10-25 12:21:53 +0000
        MDEV-11127 : Fix innochecksum to work with large files on Windows. 
    Revision #3321f1a 2016-06-21 13:35:59 +1000
        MDEV-5944: Compile fix for OQGRAPH with LLVM 
    Revision #0c925aa 2016-10-23 18:47:44 +0300
        MDEV-11097 - Update the list of unstable tests 
    Revision #fb38d26 2016-10-22 07:34:23 +0000
        MDEV-11104 Fix client to correctly retrieve current user name on Windows 
    Revision #39b7aff 2016-10-21 23:02:56 +0200
        Upstream MIPS 32bit-build-on-64bit patch from Debian Bug#838914 
    Revision #7eb4bd3 2016-10-21 22:43:46 +0200
        Upstream patch from Debian Bug 838557 
    Revision #998f987 2016-10-21 22:37:51 +0200
        Upstream MIPS test fixes from Debian Bug 838557. 
    Revision #4dfb6a3 2016-09-28 14:16:38 +0000
        MDEV-11083 performance schema test fail with threadpool 
    Revision #4192c46 2016-10-16 04:46:39 +0300
        MDEV-11061 Valgrind builder produces endless warnings 
    Revision #8a49e00 2016-10-14 23:23:49 +0300
        More unstable tests 
    Revision #f6d4f82 2016-10-14 23:23:16 +0300
        MDEV-11061 Valgrind builder produces endless warnings after switching to OpenSS 
    Revision #c18054d 2016-11-02 08:20:15 +0400
        MDEV-10347 mysqld got signal 11 
    Revision #554c60a 2016-10-31 12:44:06 +0200
        MDEV-11182: InnoDB: Assertion failure in file buf0buf.cc line 4730 (encryption.create_or_replace fails in buildbot and outside) 
    Revision #cb5685a 2016-10-31 08:49:36 +0200
        MDEV-11184: innodb.innodb-wl5522-debug-zip fails in buildbot on Windows 
    Revision #9aa7315 2016-10-31 08:48:00 +0200
        MDEV-11183: innodb.innodb-wl5522-debug fails in buildbot and outside 
    Revision #67e6cfd 2016-10-30 09:16:02 +0200
        Add suppression for new InnoDB error log error as this test intentionally produces this error. 
    Revision #58b5c40 2016-10-29 12:57:48 +0300
        Remove accidentally added directory. 
    Revision #bb4b8c7 2016-10-28 13:59:35 +0300
        MDEV-9099: Test encryption.innodb_encryption_discard_import fails on buildbot 
    Revision #de0f77a 2016-10-28 09:27:03 +0300
        MDEV-11106: Improve error messages when importing tablespaces 
    Revision #84ce681 2016-10-27 15:01:15 +0300
        MDEV-10917: Warning suggesting that innodb_page_size is experimental may be inaccurate 
    Revision #885577f 2016-10-27 14:51:10 +0300
        MDEV-11004: Unable to start (Segfault or os error 2) when encryption key missing 
    Revision #bc32372 2016-10-27 08:18:14 +0300
        MDEV-10977: [ERROR] InnoDB: Block in space_id 0 in file ibdata1 encrypted. MDEV-10394: Innodb system table space corrupted 
    Revision #c1bbedb 2016-10-28 20:37:18 +0200
        AWS key Management plugin - add plugin variable for the region 
    Revision #ea0ae42 2016-10-26 08:34:04 +0300 - Merge pull request #250 from sensssz/10.1-vats
    Revision #7496176 2016-10-25 18:57:03 -0400
        A few fixes for VATS in 10.1 
    Revision #4edd4ad 2016-10-24 22:25:54 +0300
        MDEV-10970: Crash while loading mysqldump backup when InnoDB encryption is enabled 
    Revision #021212b 2016-10-24 21:51:42 +0300 - Merge pull request #245 from sensssz/10.1-vats
    Revision #183c028 2016-10-13 01:23:21 -0400
        Move the lock after deadlock is resolved. 
    Revision #0a769b0 2016-10-12 21:54:31 -0400
        Get thd by lock->trx->mysql_thd. 
    Revision #5dc7ad8 2016-10-12 21:52:14 -0400
        Reduce conflict during in-order replication. 
    Revision #55d2bff 2016-10-11 23:27:03 -0400
        Bug fix: add * and ; for innodb 
    Revision #288796f 2016-10-11 23:05:02 -0400
        Bug fix: missing * and ; 
    Revision #e93d44f 2016-10-11 23:02:26 -0400
        Bug fix: add undeclared variables. 
    Revision #6100f59 2016-10-11 20:52:35 -0400
        Implement VATS both in InnoDB and XtraDB. Add configuration options for it in both of them. 
    Revision #1bfa37a 2016-10-24 16:55:36 +0300
        Add more information if encryption information is already stored for tablespace but page0 is not yet read. 
    Revision #ec5bd0d 2016-10-24 09:25:36 +0300
        MDEV-10969: innochecksum dumps core for some .ibd files due to floating point exception 
    Revision #aea1967 2016-10-24 09:05:10 +0300 - Merge pull request #249 from Cona19/10.1-remove-unnecessary-semicolon
    Revision #9401e6b 2016-10-24 14:58:41 +0900
        Remove unnecessary semicolons 
    Revision #ee1d08c 2016-10-23 00:10:37 +0000
        Revert "Prepare XtraDB to be used with xtrabackup." 
    Revision #de5646f 2016-10-22 14:10:12 +0000
        Prepare XtraDB to be used with xtrabackup. 
    Revision #8f5e3e2 2016-10-21 16:20:47 +0000
        Fix escaping '\' in a string constant. 
    Revision #2584897 2016-10-19 03:02:13 +0300
        MDEV-11082 mysql_client_test: test_ps_query_cache fails with group-concat-max-len=1M 
    Revision #fd1f507 2016-10-19 03:01:36 +0300
        Additions to the list of unstable tests 
    Revision #c4776d3 2016-10-16 23:48:59 +0200 - Merge "remove unnecessary global mutex in parallel replication" into 10.1.
    Revision #50f19ca 2016-09-20 15:30:57 +0200
        Remove unnecessary global mutex in parallel replication. 
    Revision #ed4a6f1 2016-10-10 12:49:10 +0000
        MDEV-10823 amend : Use opt_log_basename instead of hostname to test filesystem case sensitivity. 
    Revision #f35e918 2016-09-30 12:11:09 -0400
        bump the VERSION 
    Revision #d83fd5f 2016-09-30 09:13:39 +0300
        MDEV-10685: innodb.xa_recovery failed in buildbot

Notable Changes

• XtraDB updated to 5.6.32-78.1
• TokuDB updated to 5.6.32-78.1
• Innodb updated to 5.6.33
• Performance Schema updated to 5.6.33
• Optimizer sometimes use "index" instead of "range" access for UPDATE (MDEV-10649)

Changelog:

• Revision #6925689 2016-09-29 14:58:32 -0400
  • MDEV-9312: storage engine not enforced during galera cluster replication
• Revision #235876d 2016-09-29 14:21:14 +0200
  • update test results after merge
• Revision #2ede40e 2016-09-29 12:59:51 +0200 - Merge branch '10.0' into 10.1
• Revision #a3f11f7 2016-09-29 12:31:46 +0200 - Merge branch '5.5' into 10.0
• Revision #7497ebf 2016-09-29 10:16:24 +0200
  • mysqld_safe: close stdout and stderr
• Revision #0e76054 2016-09-28 12:52:01 +0000
  • Feedback plugin : add support for Windows 10 / Server 2016.
• Revision #b38d3c3 2016-09-27 12:34:15 +0000
  • MDEV-10907 MTR and server writes can interleave in the error log
• Revision #ad20769 2016-09-29 11:50:13 +0200
  • init plugin psi keys before LOCK_plugin
• Revision #b34c813 2016-09-28 22:12:03 +0200
  • MDEV-10201 SSL tests fail on fedora23
• Revision #9ff9acb 2016-09-22 17:52:05 +0200
  • MDEV-10716: Assertion `real_type() != FIELD_ITEM' failed in Item_ref::build_equal_items(THD*, COND_EQUAL*, bool, COND_EQUAL)
• Revision #d5dfa0f 2016-09-28 13:27:34 -0400
  • MDEV-9416: MariaDB galera got signal 11 when altering table add unique index
• Revision #7c525ce 2016-09-28 13:26:13 -0400
  • MDEV-9312: storage engine not enforced during galera cluster replication
• Revision #88f2ec6 2016-09-28 13:23:31 -0400
  • MDEV-10041: Server crashes sporadically during bootstrap while running wsrep tests
• Revision #e1c6f28 2016-09-28 13:20:02 -0400 - Merge branch '10.0-galera' into 10.1
• Revision #c9ded85 2016-09-21 10:51:37 +0200
  • MDEV-10853 netcat help output in error log when running xtrabackup SST
• Revision #3dd88fb 2016-09-01 12:59:11 -0400
  • MDEV-10714: Could not execute Delete_rows event on table; wsrep_max_ws_rows exceeded. Error_Code 1180
• Revision #616271b 2016-09-01 12:53:44 -0400
  • Cleanup: MDL_context::wsrep_get_thd() is no longer needed
• Revision #16702ec 2016-08-25 21:19:25 -0400
  • Record wsrep.variables test result (with non-debug galera library).
• Revision #735a4a1 2016-09-28 17:59:11 +0200
  • MDEV-10508 Mariadb crash on out of disk space during dump import
• Revision #794c826 2016-09-26 14:29:23 +0200
  • MDEV-10890 plugins.pam fails in buildbot with valgrind
• Revision #66d9696 2016-09-28 17:55:28 +0200 - Merge branch '10.0' into 10.1
• Revision #23af6f5 2016-09-28 16:19:58 +0300 - Merge branch '10.0' of github.com:MariaDB/server into 10.0
• Revision #078e510 2016-09-27 19:03:11 +0200 - Merge branch 'merge/merge-tokudb-5.6' into 10.0
• Revision #e312e2e 2016-09-27 17:59:58 +0200
  • 5.6.32-78.1
• Revision #2e914ac 2016-09-27 19:00:08 +0200 - Merge branch 'merge/merge-perfschema-5.6' into 10.0
• Revision #e3124a8 2016-09-27 17:57:28 +0200
  • 5.6.33
• Revision #bb8b658 2016-09-27 18:58:57 +0200 - Merge branch 'merge/merge-xtradb-5.6' into 10.0
• Revision #93ab309 2016-09-27 18:00:59 +0200
  • 5.6.32-78.1
• Revision #3629f62 2016-09-27 18:05:06 +0200 - Merge branch 'merge/merge-innodb-5.6' into 10.0
• Revision #094f140 2016-09-27 17:56:00 +0200
  • 5.6.33
• Revision #77ce4ea 2016-09-27 09:21:19 +0200 - Merge branch '5.5' into 10.0
• Revision #d61e526 2016-09-26 17:48:08 +0200
  • MDEV-10441 Document the server_audit_loc_info variable
• Revision #c91fdb6 2016-09-26 13:03:02 +0200
  • Windows , mtr : allow cdb to print core dumps also if --parallel > 1
• Revision #8483659 2016-09-24 10:06:58 +0200
  • report correct write error on log writes
• Revision #f620da1 2016-09-24 01:17:35 +0200
  • MDEV-10725 Server 10.1.17 fails to build using clang with c++11
• Revision #9434431 2016-09-24 13:50:42 +0200
  • Fix free() after my_malloc() (should be my_free()).
• Revision #b3f7a80 2016-09-13 11:12:54 -0400
  • bump the VERSION
• Revision #0da39ca 2016-09-12 16:18:07 +0200
  • fix BIGINT+MEDIUMINT type aggregation
• Revision #347eeef 2016-09-11 20:55:11 +0200
  • don't use my_copystat in the server
• Revision #611dc0d 2016-09-11 20:53:16 +0200
  • missing element in prelocked_mode_name[] array
• Revision #a229091 2016-09-11 20:52:00 +0200
  • potential signedness issue
• Revision #7ae555c 2016-09-11 20:51:09 +0200 - Merge branch 'mysql/5.5' into 5.5
• Revision #b9631e3 2015-11-10 12:41:26 +0100
  • MDEV-8833 Crash of server on prepared statement with conversion to semi-join
• Revision #ee97274 2016-08-25 09:50:04 +0300
  • DEV-10595 MariaDB daemon leaks memory with specific query
• Revision #a92a8cc 2016-08-19 17:11:20 +0000
  • Windows packaging : use /d switch to sign MSI, to prevent installer showing randomly generated name in UAC prompt
• Revision #723488b 2016-08-04 15:43:52 +0400
  • MDEV-10424 - Assertion `ticket == null' failed in MDL_request::set_type
• Revision #09cb646 2016-08-11 19:35:53 +0000
  • Windows : fix search for WiX root directory when using 64bit cmake
• Revision #737964d 2016-08-10 11:24:18 -0400
  • bump the VERSION
• Revision #677c44f 2016-09-23 20:27:58 +0200
  • MDEV-10775 System table in InnoDB format allowed in MariaDB could lead to crash
• Revision #e56a539 2016-07-01 13:57:18 +0400
  • MDEV-10315 - Online ALTER TABLE may get stuck in tdc_remove_table
• Revision #83d5b96 2016-09-19 17:15:18 +0200
  • Fix tokudb jemalloc linking
• Revision #fd0c114 2016-09-12 14:57:32 +0200
  • Update contributors
• Revision #6e02d42 2016-09-13 13:16:11 +0200
  • Fix compilation failure of TokuDB on BSD-like systems
• Revision #b34d7fb 2016-09-11 11:18:27 +0200
  • Debian bug#837369 - test failures on hppa
• Revision #af3dc48 2016-09-10 20:42:20 +0200
  • Attempt to fix strange rpm dependency issue following prior patch
• Revision #577f3c1 2016-09-10 17:50:32 +0200
  • Fix use of `require` in mysql-test-run.
• Revision #6c74ef8 2016-09-07 09:30:02 +1000
  • MDEV-10707: Fix tokudb test rows-32m-rand-insert (#231)
• Revision #a14f61e 2016-09-05 12:28:35 +0300
  • MDEV-7142: main.index_merge_innodb fails sporadically in buildbot
• Revision #f81f985 2016-08-29 11:53:33 +0200
  • fix conpilation on OpenBSD
• Revision #39ec5ac 2016-08-25 11:55:54 -0400
  • bump the VERSION
• Revision #66a58f4 2016-09-28 16:19:05 +0300 - Merge fix for MDEV-10649 from 10.0 to 10.1
• Revision #a53f3c6 2016-09-28 16:12:58 +0300
  • MDEV-10649: Optimizer sometimes use "index" instead of "range" access for UPDATE
• Revision #0e47223 2016-09-27 17:38:47 +0200
  • Make sure to recompile the feedback plugin for EMBEDDED
• Revision #e226276 2016-09-14 18:15:03 +0200
  • MDEV-10777: Server crashed due to query_cache_info plugin
• Revision #3f5aedc 2016-09-27 11:18:24 +0000
  • MDEV-10847 Bring AWS KMS encryption plugin up-to-date with released SDK
• Revision #f1aefd9 2016-09-23 18:55:44 +0200
  • MDEV-10823 Certain unicode characters in hostname prevent mysqld from starting
• Revision #661d08c 2016-09-26 15:16:00 +0300
  • MDEV-10887: innodb.innodb_stats_fetch_nonexistent fails in buildbot on Windows
• Revision #452e849 2016-09-26 12:29:31 +0300
  • MDEV-10886: encryption.innodb-bad-key-change fails (crashes) in buildbot
• Revision #4e2a0c3 2016-09-26 09:58:50 +0300
  • MDEV-10888: encryption.filekeys_emptyfile fails in buildbot with valgrind
• Revision #d30809a 2016-09-26 09:40:47 +0400
  • MDEV-10832 Out of tree build: mysql_install_db to see all .sql files.
• Revision #7d7b92c 2016-09-24 14:21:27 +0300
  • Disable encryption info and first page read info for every tablespace on product builds.
• Revision #5d001d1 2016-09-23 17:28:38 +1000
  • MDEV-10832 - Out of tree build: mysql_install_db to see all .sql files (#237)
• Revision #e136aa1 2016-09-23 09:11:11 +0300
  • Fix test failure. Need to mask more tablespace numbers as they are not consistent on parallel mtr runs.
• Revision #1d55cfc 2016-09-22 20:57:15 +0300
  • Do not use os_file_read() directly for reading first page of the tablespace. Instead use fil_read() with syncronous setting. Fix test failures and mask tablespace number as it could change in concurrent mtr runs.
• Revision #2bedc39 2016-09-22 16:32:26 +0300
  • MDEV-9931: InnoDB reads first page of every .ibd file at startup
• Revision #e387bfa 2016-09-22 19:14:40 +1000
  • MDEV-10830 - Fix undefined database test error when running mysql_install_db (#234)
• Revision #9f837c6 2016-09-22 10:03:12 +0400
  • MDEV-10864 Wrong result for WHERE .. (f2=COMPRESS('test') OR f2=COMPRESS('TEST'))
• Revision #7e4eb99 2016-09-22 07:00:10 +0400
  • MDEV-10425 Assertion `collation.derivation == DERIVATION_IMPLICIT' failed in Item_func_conv_charset::fix_length_and_dec()
  • MDEV-10850 Wrong result for WHERE .. (f2=TO_BASE64('test') OR f2=TO_BASE64('TEST'))
• Revision #ec7e0b7 2016-09-21 09:13:33 +0400
  • MDEV-10556 Assertion `0' failed in virtual void Item_sum_field::set_result_field(Field*)
• Revision #8b51bac 2016-09-20 21:32:53 -0400
  • MDEV-10735: Valgrind warnings around Galera SST
• Revision #6eca463 2016-09-20 15:17:57 -0400
  • Fix typo in valgrind.supp
• Revision #bb2c1a5 2016-09-09 11:53:50 +0200 - Merge parallel replication async deadlock kill into 10.1
• Revision #7e0c9de 2016-09-08 15:25:40 +0200
  • Parallel replication async deadlock kill
• Revision #de7f877 2016-09-09 08:40:24 +0400
  • MDEV-10702 Crash in SET STATEMENT FOR EXECUTE
• Revision #8494039 2016-09-06 16:34:25 +0200
  • fix the test to work
• Revision #61fd38a 2016-09-05 17:11:14 +0200
  • update plugin maturities
• Revision #362ad94 2016-09-05 09:11:42 +0200
  • cleanup: don't copy-paste, don't current_thd
• Revision #747893a 2016-09-02 14:40:09 -0400
  • MDEV-10545: Update perfschema.nesting result
• Revision #31697d0 2016-09-02 12:21:40 -0400
  • MDEV-10545: Server crashed in my_copy_fix_mb on querying I_S and P_S tables
• Revision #a322651 2016-08-29 16:44:46 +0200
  • MDEV-10017: Get unexpected `Empty Set` for correlated subquery with aggregate functions
• Revision #f6e47c0 2016-08-31 11:51:12 +0400 - Merge pull request #224 from 0xAX/build-get-rid-from-die
• Revision #080ac47 2016-08-25 15:56:53 +0600
  • remove die() from BUILD/autorun.sh
• Revision #64fe389 2016-08-30 10:32:37 -0400
  • bump the VERSION

Percona Server is an enhanced drop-in replacement for MySQL. With Percona Server,

• Your queries will run faster and more consistently.
• You will consolidate servers on powerful hardware.
• You will delay sharding, or avoid it entirely.
• You will save money on hosting fees and power.
• You will spend less time tuning and administering.
• You will achieve higher uptime.
• You will troubleshoot without guesswork.

Does this sound too good to be true? It’s not. Percona Server offers breakthrough performance, scalability, features, and instrumentation. Its self-tuning algorithms and support for extremely high-performance hardware make it the clear choice for companies who demand the utmost performance and reliability from their database server.