The Ultimate Guide to High Availability with MariaDB
This is a read-only copy of the MariaDB Knowledgebase generated on 2024-12-22. For the latest, interactive version please visit https://mariadb.com/kb/.

MariaDB 5.1.53 Changelog

Download | Release Notes | Changelog | Overview of 5.1

Release date: 6 Dec 2010

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 #2934
    • Fixes to not trigger end-consistency testing of pagecache.
      • Moved end_pagecache() to after maria_close()
      • Flush page cache before closing files (in maria_pack)
    • Fixed test suite failure for PBXT
  • Revision #2933
    • The assert removed because it do not take into account case when previous and this buffers used for first time but previous buffer was not sent to disk yet (i.e. previous buffer was never sent to disk yet).
  • Revision #2932
    • Aria unit tests fixed to have correct pagecache shutdown.
    • The Aria multithread test unlocked.
  • Revision #2931
    • Removed assert as gcc on gentoo couldn't compile it without a warning :(
    • (Not critical, we will just catch the error later)
  • Revision #2930
    • Fixed (wrong) compiler warning
  • Revision #2929
    • Fixed compiler warning
    • Added missing inc_counter_for_resize_op(pagecache).
    • (caused maria.maria-preload.test to fail)
  • Revision #2928
    • Fixed compiler warnings.
    • Fixed timing test failures.
    • Fixed a failure in the Aria engines page cache and log handler (found with maria.maria-big test)
      • This could cause a core dump when deleting big blobs.
      • Added test to end_pagecache() to verify that page cache was correctly used.
        • inc_counter_for_resize_op and dec_counter_for_resize_op are called same number of times.
        • All page cache blocks was properly deallocated (empty)
  • Revision #2927
    • Fix problems seen in Buildbot:
      • Make sure creation of t1 is replicated before trying to create trigger on it on slave
      • Use safe #ifdef for declaration as for definition to avoid warning about unused static function.
  • Revision #2926 [merge]
  • Revision #2925
    • Fixed failures in buildbot
  • Revision #2924
    • MySQL Bug #54201: "SET INSERT_ID" event must be ignored if corresponding event is ignored
      • An INSERT query log event is preceeded by an INSERT_ID intvar event if the INSERT allocates a new auto_increment value. But if we ignore the INSERT due to --replicate-ignore-table or similar, then the INSERT_ID event is still executed, and the set value of INSERT_ID lingers around in the slave sql thread THD object indefinitely until the next INSERT that happens to need allocation of a new auto_increment value.
      • Normally this does not cause problems as such following INSERT would normally come with its own INSERT_ID event. In this bug, the user had a trigger on the slave which was missing on the master, and this trigger had an INSERT which could be affected. In any case, it seems better to not leave a stray INSERT_ID hanging around in the sql thread THD indefinitely.
      • Note that events can also be skipped from apply_event_and_update_pos(); however it is not possible in that code to skip the INSERT without also skipping the INSERT_ID event.
  • Revision #2923
    • Fixed some compiler warnings
  • Revision #2922
    • Fixed compiler and gmake warnings
      • Removed SCCS rule from Makefile.am
      • Made dummy rule in sql_yacc.yy to get rid of compiler warning about not used label.
    • Don't use maintainer mode with valgrind (as we don't want to initialize all variables)
  • Revision #2921
    • Fixed compiler warnings and a compilation failure on windows
  • Revision #2920
    • Patch from Sergey Petrunya:
    • Fix post-merge failure in 5.1-merge
      • Let QUICK_RANGE_INTERSECT_SELECT not make assumption that HA_EXTRA_KEYREAD scans do not touch parts of table->record[0] that refer to fields that are not covered by the used index.
      • This assumption is not true for XtraDB (e.g. grep row/row0sel.c for "init null bytes with default values as they might be").
  • Revision #2919 [merge]
    • Automatic merge with 5.1
      • Revision #2891.18.1
        • Fix of Bug #675248.
        • Registration of pointer change if we assign it to other pointer which should be identical after statement execution (PS/SP).
  • Revision #2918
    • Fixed failing test cases
  • Revision #2917
    • Merge of innodb_plugin for MySQL 5.1.53 with xtradb
    • Fixed compiler warnings in xtradb
    • Added back resetting of null bitmap but now in row_search_for_mysql()
  • Revision #2916
    • A proper fix for MySQL Bug #57688.
    • Introduced a new flag in the class Item. The flag is set to 1 only for items that are used in GROUP BY lists of queries with ROLLUP.
  • Revision #2915 [merge]
    • Automatic merge with base
      • Revision #2912.1.1 [merge]
        • Merge with MySQL 5.1.53
        • Open issues:
          • A better fix for #57688; Igor is working on this
          • Test failure in index_merge_innodb.test ; Igor promised to look at this
          • Some Innodb tests fails (need to merge with latest xtradb) ; Kristian promised to look at this.
            • Failing tests: innodb_plugin.innodb_bug56143 innodb_plugin.innodb_bug56632 innodb_plugin.innodb_bug56680 innodb_plugin.innodb_bug57255
          • Werror is disabled; Should be enabled after merge with xtradb.
  • Revision #2914
    • Fix test failure when the mysql-test/ directory is not writable.
  • Revision #2913 [merge]
    • Merge XtraDB from Percona-Server 5.1.52-11.6 into MariaDB 5.1
    • revid:oleg.tsarev@percona.com-20101118145125-wjhjrb5jwhi0g7sj
    • Revision #0.6.44
      • Updated with changes from lp:percona-server/release-5.1.52-11 as of November 24, 2010
      • Merged: revid:oleg.tsarev@percona.com-20101118145125-wjhjrb5jwhi0g7sj
  • Revision #2912 [merge]
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.