MariaDB server is a community developed fork of MySQL server. Started by core members of the original MySQL team, MariaDB actively works with outside developers to deliver the most featureful, stable, and sanely licensed open SQL server in the industry.
Find a file
Marko Mäkelä 3e6fcb6ac8 MDEV-14935 Remove bogus conditions related to not redo-logging PAGE_MAX_TRX_ID changes
InnoDB originally skipped the redo logging of PAGE_MAX_TRX_ID changes
until I enabled it in commit e76b873f24
that was part of MySQL 5.5.5 already.

Later, when a more complete history of the InnoDB Plugin for MySQL 5.1
(aka branches/zip in the InnoDB subversion repository) and of the
planned-to-be closed-source branches/innodb+ that became the basis of
InnoDB in MySQL 5.5 was pushed to the MySQL source repository, the
change was part of commit 509e761f06:

 ------------------------------------------------------------------------
 r5038 | marko | 2009-05-19 22:59:07 +0300 (Tue, 19 May 2009) | 30 lines

 branches/zip: Write PAGE_MAX_TRX_ID to the redo log. Otherwise,
 transactions that are started before the rollback of incomplete
 transactions has finished may have an inconsistent view of the
 secondary indexes.

 dict_index_is_sec_or_ibuf(): Auxiliary function for controlling
 updates and checks of PAGE_MAX_TRX_ID: check whether an index is a
 secondary index or the insert buffer tree.

 page_set_max_trx_id(), page_update_max_trx_id(),
 lock_rec_insert_check_and_lock(),
 lock_sec_rec_modify_check_and_lock(), btr_cur_ins_lock_and_undo(),
 btr_cur_upd_lock_and_undo(): Add the parameter mtr.

 page_set_max_trx_id(): Allow mtr to be NULL.  When mtr==NULL, do not
 attempt to write to the redo log.  This only occurs when creating a
 page or reorganizing a compressed page.  In these cases, the
 PAGE_MAX_TRX_ID will be set correctly during the application of redo
 log records, even though there is no explicit log record about it.

 btr_discard_only_page_on_level(): Preserve PAGE_MAX_TRX_ID.  This
 function should be unreachable, though.

 btr_cur_pessimistic_update(): Update PAGE_MAX_TRX_ID.

 Add some assertions for checking that PAGE_MAX_TRX_ID is set on all
 secondary index leaf pages.

 rb://115 tested by Michael, fixes Issue #211
 ------------------------------------------------------------------------

After this fix, some bogus references to recv_recovery_is_on()
remained. Also, some references could be replaced with
references to index->is_dummy to prepare us for MDEV-14481
(background redo log apply).
2018-01-12 18:31:03 +02:00
BUILD Merge 10.2 into bb-10.2-ext 2018-01-11 18:00:31 +02:00
client Merge bb-10.2-ext into 10.3 2018-01-04 09:22:59 +02:00
cmake Minor spelling fixes in code comments, docs and output 2018-01-12 16:49:02 +02:00
dbug Re-enable 'S' for --debug (sf_sanity checking for each call) 2017-12-22 14:56:58 +02:00
debian Minor spelling fixes in code comments, docs and output 2018-01-12 16:49:02 +02:00
Docs Minor spelling fixes in code comments, docs and output 2018-01-12 16:49:02 +02:00
extra MDEV-14874 innodb_encrypt_log corrupts the log when the LSN crosses 32-bit boundary 2018-01-08 09:44:40 +02:00
include Minor spelling fixes in code comments, docs and output 2018-01-12 16:49:02 +02:00
libmariadb@f3944bbd36 Fix compilation warnings for libmariadb 2018-01-11 12:12:31 +02:00
libmysqld Merge bb-10.2-ext into 10.3 2018-01-04 09:22:59 +02:00
libservices
man Minor spelling fixes in code comments, docs and output 2018-01-12 16:49:02 +02:00
mysql-test After-merge fix to innodb.log_corruption 2018-01-11 22:54:22 +02:00
mysys Minor spelling fixes in code comments, docs and output 2018-01-12 16:49:02 +02:00
mysys_ssl
pcre
plugin Moved semisync from a plugin to normal server 2017-12-18 13:43:36 +02:00
randgen/conf
scripts Merge bb-10.2-ext into 10.3 2018-01-04 09:22:59 +02:00
sql Merge bb-10.2-ext into 10.3 2018-01-11 19:44:41 +02:00
sql-bench
sql-common Merge bb-10.2-ext into 10.3 2018-01-04 09:22:59 +02:00
storage MDEV-14935 Remove bogus conditions related to not redo-logging PAGE_MAX_TRX_ID changes 2018-01-12 18:31:03 +02:00
strings Minor spelling fixes in code comments, docs and output 2018-01-12 16:49:02 +02:00
support-files Merge bb-10.2-ext into 10.3 2018-01-04 09:22:59 +02:00
tests Merge bb-10.2-ext into 10.3 2017-11-30 08:16:37 +02:00
unittest MDEV-13728 - Import MySQL 5.7 atomic operations for MSVC and Solaris 2017-11-27 18:35:53 +04:00
vio MDEV-14113 Use abortive TCP close, in case server closes the connection 2017-12-11 14:54:17 +00:00
win Minor spelling fixes in code comments, docs and output 2018-01-12 16:49:02 +02:00
wsrep
zlib
.gitattributes
.gitignore Merge bb-10.2-ext into 10.3 2018-01-04 09:22:59 +02:00
.gitmodules
.travis.compiler.sh Lean down compilation when running travis with rpl 2017-12-29 19:38:29 +02:00
.travis.yml Travis-CI: clean up cruft and add more in-line commments 2017-11-21 13:07:26 +02:00
appveyor.yml Appveyor: apply feedback from wlad, timeout=4 2017-12-25 12:00:52 +01:00
BUILD-CMAKE Minor spelling fixes in code comments, docs and output 2018-01-12 16:49:02 +02:00
CMakeLists.txt
config.h.cmake Cleanup UT_LOW_PRIORITY_CPU/UT_RESUME_PRIORITY_CPU 2017-11-28 16:34:31 +04:00
configure.cmake Minor spelling fixes in code comments, docs and output 2018-01-12 16:49:02 +02:00
COPYING
COPYING.thirdparty
CREDITS
EXCEPTIONS-CLIENT
INSTALL-SOURCE
INSTALL-WIN-SOURCE
KNOWN_BUGS.txt
README.md
VERSION bump the VERSION 2018-01-04 10:41:08 -05:00

MariaDB: drop-in replacement for MySQL

MariaDB is designed as a drop-in replacement of MySQL(R) with more features, new storage engines, fewer bugs, and better performance.

MariaDB is brought to you by the MariaDB Foundation. Please read the CREDITS file for details about the MariaDB Foundation, and who is developing MariaDB.

MariaDB is developed by many of the original developers of MySQL who now work for the MariaDB Foundation and the MariaDB Corporation, and by many people in the community.

MySQL, which is the base of MariaDB, is a product and trademark of Oracle Corporation, Inc. For a list of developers and other contributors, see the Credits appendix. You can also run 'SHOW authors' to get a list of active contributors.

A description of the MariaDB project and a manual can be found at: https://mariadb.org/ https://mariadb.com/kb/en/ https://mariadb.com/kb/en/mariadb-vs-mysql-features/ https://mariadb.com/kb/en/mariadb-versus-mysql-features/ https://mariadb.com/kb/en/mariadb-versus-mysql-compatibility/

As MariaDB is a full replacement of MySQL, the MySQL manual at http://dev.mysql.com/doc is generally applicable.

Help:

More help is available from the Maria Discuss mailing list https://launchpad.net/~maria-discuss and the #maria IRC channel on Freenode.

License:


NOTE:

MariaDB is specifically available only under version 2 of the GNU General Public License (GPLv2). (I.e. Without the "any later version" clause.) This is inherited from MySQL. Please see the README file in the MySQL distribution for more information.

License information can be found in the COPYING, COPYING.LESSER, and COPYING.thirdparty files.


Bug Reports:

Bug and/or error reports regarding MariaDB should be submitted at https://mariadb.org/jira

Bugs in the MySQL code can also be submitted at https://bugs.mysql.com

The code for MariaDB, including all revision history, can be found at: https://github.com/MariaDB/server


Code status:

  • tests status travis-ci.org (10.2 branch)