mirror/mariadb
1
0
Fork 0
mirror of https://github.com/MariaDB/server.git synced 2025-01-18 04:53:01 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
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.
182067 commits 2784 branches 343 tags 1.6 GiB
MariaDB\ 71.8%
C++ 16.2%
C 10.6%
Shell 0.5%
Perl 0.4%
Other 0.3%
Find a file
Marko Mäkelä 76c62bc69c MDEV-15914: Restore MLOG_UNDO_INSERT 
trx_undof_page_add_undo_rec_log(): Write the MLOG_UNDO_INSERT
record instead of the equivalent MLOG_2BYTES and MLOG_WRITE_STRING.
This essentially reverts commit 9ee8917dfd.

In MariaDB 10.3, I attempted to simplify the crash recovery code
by making use of lower-level redo log records. It turns out that
we must keep the redo log parsing code in order to allow crash-upgrade
from older MariaDB versions (MDEV-14848).

Now, it further turns out that the InnoDB redo log record format is
suboptimal for logging multiple changes to a single page. This simple
change to the redo logging of undo log significantly affects the
INSERT and UPDATE performance.

Essentially, we wrote
	(space_id,page_number,MLOG_2BYTES,2 bytes)
	(space_id,page_number,MLOG_WRITE_STRING,N+4 bytes)
instead of the previously written
	(space_id,page_number,MLOG_UNDO_INSERT,N+2 bytes)

The added redo log volume caused a single-threaded INSERT
(without innodb_adaptive_hash_index) of
1,000,000 rows to consume 11 seconds instead of 9 seconds,
and a subsequent UPDATE of 30,000,000 rows to consume 64 seconds
instead of 58 seconds. If we omitted all redo logging for the
undo log, the INSERT would consume only 4 seconds.
2018-04-26 22:53:33 +03:00
BUILD Renamed compile-pentium scripts to compile-pentium32 2018-04-16 20:16:43 +03:00
client Fix a lot of compiler warnings found by -Wunused 2018-04-26 17:35:12 +03:00
cmake MDEV-12924 No --innodb-numa-interleave in mysqld binaries 2018-04-19 13:08:35 +05:30
dbug
debian
Docs
extra Fix a lot of compiler warnings found by -Wunused 2018-04-26 17:35:12 +03:00
include Fix a lot of compiler warnings found by -Wunused 2018-04-26 17:35:12 +03:00
libmariadb@668757aaa9
libmysqld
libservices
man
mysql-test MDEV-15915 Add Feature_json status variable. 2018-04-26 23:12:51 +04:00
mysys Merge 10.2 into 10.3 2018-04-24 20:59:57 +03:00
mysys_ssl
pcre
plugin
randgen/conf
scripts
sql MDEV-15915 Add Feature_json status variable. 2018-04-26 23:12:51 +04:00
sql-bench Quote 'rank' in test-ATIS so that it can be run with MySQL 8.0 2018-04-21 17:54:14 +03:00
sql-common Merge 10.2 into 10.3 2018-04-24 20:59:57 +03:00
storage MDEV-15914: Restore MLOG_UNDO_INSERT 2018-04-26 22:53:33 +03:00
strings
support-files
tests Fixed a compiler error 2018-04-25 18:22:56 -07:00
unittest
vio
win
wsrep
zlib
.gitattributes
.gitignore
.gitmodules
.travis.compiler.sh
.travis.yml
appveyor.yml
BUILD-CMAKE
CMakeLists.txt MDEV-12924 No --innodb-numa-interleave in mysqld binaries 2018-04-19 13:08:35 +05:30
config.h.cmake Fix a lot of compiler warnings found by -Wunused 2018-04-26 17:35:12 +03:00
configure.cmake
COPYING
COPYING.thirdparty
CREDITS
EXCEPTIONS-CLIENT
INSTALL-SOURCE
INSTALL-WIN-SOURCE
KNOWN_BUGS.txt
README.md
VERSION bump the VERSION 2018-04-16 11:31:02 -04:00

README.md

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)