MariaDB 5.1.61 Changelog

Downloadarrow-up-right |Release Notes |Changelog |Overview of 5.1

Release date: 2 Apr 2012

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

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

  • Revision #3142arrow-up-right Fri 2012-03-30 13:42:52 +0300

    • Fixed Bug #967914arrow-up-right "CHECK TABLE persistently reports table corruption after removing Aria logs" Fixed that repair removes the 'table is moved' mark.

  • Revision #3141arrow-up-right Thu 2012-03-29 18:06:08 +0200

    • fix the test case for windows: replace_result \\ /

  • Revision #3140arrow-up-right Thu 2012-03-29 16:36:06 +0200

    • make the code compile again

  • Revision #3139arrow-up-right Wed 2012-03-28 13:22:21 +0300

    • Fixed Bug #944422arrow-up-right "mysql_upgrade destroys Maria tables?"

    • The issue was that check/optimize/anaylze did not zerofill the table before they started to work on it.

    • Added one more element to not often used function handler::auto_repair() to allow handler to decide when to auto repair.

  • Revision #3138arrow-up-right Wed 2012-03-21 18:22:02 +0100

    • Bug #933959arrow-up-right Assertion `0' failed in net_end_statement(THD*) on concurrent SELECT FROM I_S.INNODB_SYS_INDEXES and ALTER TABLE

    • Workaround: report a generic error if an I_S plugin failed silently.

  • Revision #3137arrow-up-right Thu 2012-03-15 15:06:06 +0100

    • Fix access to uninitialized variable in innodb error message in case WriteFile() fails.

  • Revision #3136arrow-up-right Wed 2012-03-14 21:16:24 +0100

    • restore my_safe_printf_stderr for "crash-safe sigsegv handler"

      • use vsnprintf()

      • use write() on windows, not WriteFile or fwrite()

      • localtime_r is still a problem

  • Revision #3135arrow-up-right Mon 2012-03-12 11:31:40 +0100

  • Revision #3134arrow-up-right Fri 2012-02-24 17:01:47 +0200

    • Fix for Bug #909635arrow-up-right: MariaDB crashes on a select with long varchar and blob fields Problem was a crash in internal temporary (Maria) files when row length exceeded 65535

  • Revision #3133arrow-up-right Tue 2012-02-21 14:17:33 +0200

    • Fixed suppression expression.

  • Revision #3132arrow-up-right [merge] Tue 2012-02-21 01:51:55 +0200

    • Automatic merge

    • Revision #3130.1.1arrow-up-right Tue 2012-02-21 01:44:50 +0200

      • More general handling of memory loss in dlclose (backported from 5.2)

      • Fixed supression in mysql-test-run so it also works on windows.

  • Revision #3131arrow-up-right Mon 2012-02-20 18:07:38 +0100

    • Fix compilation on Windows, and various Windows related mistakes introduced by "safe exception patch".

    • Remove misleading comments suggesting about signal() Windows, the routine here is part of a exception handler, and sig parameter is an exception code.

  • Revision #3130arrow-up-right Mon 2012-02-20 17:56:47 +0200

    • Fixed compiler warnings

  • Revision #3129arrow-up-right [merge] Mon 2012-02-20 16:23:18 +0200

    • Merge with MYSQL 5.1.61

    • Fixed README with link to source

    • Merged InnoDB change to XtraDB

  • Revision #3128arrow-up-right [merge] Sat 2012-02-11 16:42:46 +0100

    • merge

    • Revision #3117.1.3arrow-up-right Sat 2012-02-11 03:25:49 +0100

      • A recent change in the server protocol code broke SSL connection for some client libraries.

      • Protocol documentation (MySQL_Internals_ClientServer_Protocolarrow-up-right) says that initial packet sent by client if client wants SSL, consists of client capability flags only (4 bytes or 2 bytes edependent on protocol versionl). Some clients happen to send more in the initial SSL packet (C client, Python connector), while others (Java, .NET) follow the docs and send only client capability flags.

      • A change that broke Java client was a newly introduced check that frst client packet has 32 or more bytes. This is generally wrong, if client capability flags contains CLIENT_SSL.

      • Also, fixed the code such that read max client packet size and charset in the first packet prior to SSL handshake. With SSL, clients do not have to send this info, they can only send client flags.

      • This is now fixed such that max packet size and charset are not read prior to SSL handshake, in case of SSL they are read from the "complete" client authentication packet after SSL initialization.

  • Revision #3127arrow-up-right Wed 2012-01-25 11:34:43 +0100

    • mtr runs only "big" tests, if --big-test is repeated twice

  • Revision #3126arrow-up-right Wed 2012-01-04 20:10:15 +0100

    • report innodb_file_per_table, innodb_flush_log_at_trx_commit, innodb_flush_method

  • Revision #3125arrow-up-right Thu 2011-12-29 21:55:17 -0800

  • Revision #3124arrow-up-right Wed 2011-12-21 13:23:15 +0200

  • Revision #3123arrow-up-right Mon 2011-12-12 16:28:16 +0100

    • new "./configure --disable-distribution" option

  • Revision #3122arrow-up-right Mon 2011-12-12 13:37:18 +0100

    • Fix GCC build failure in PBXT in some cases/platforms.

  • Revision #3121arrow-up-right Sun 2011-12-11 22:58:01 +0200

    • Fixed valgrind problem: reference on deleted memory of temporary table name.

    • Removed previous patch of this problem.

circle-info

Be notified of new MariaDB Server releases automatically by subscribingarrow-up-right to the MariaDB Foundation community announce 'at' lists.mariadb.org announcement list (this is a low traffic, announce-only list). MariaDB plc customers will be notified for all new releases, security issues and critical bug fixes for all MariaDB plc products thanks to the Notification Services.

MariaDB may already be included in your favorite OS distribution. More information can be found on the Distributions which Include MariaDB page.

This page is licensed: CC BY-SA / Gnu FDL

spinner

Last updated

Was this helpful?