Posts Tagged ‘mariadb downloads’

MariaDB 10.0.10 Overview and Highlights

Tuesday, April 8th, 2014

MariaDB 10.0.10 was recently released, and is available for download here:

https://downloads.mariadb.org/mariadb/10.0.10/

This is the first GA (“Generally Availability“, aka “recommended for production systems”) release of MariaDB 10.0, and 11th overall release of MariaDB 10.0.

Since this is the initial 10.0 GA release, this is primarily a bug-fix and polishing release.

Here are the main items of note:

  1. The Audit Plugin is now included in MariaDB (MDEV-5584)
  2. Improved XtraDB performance by fixing incorrect calculation of flushed pages (MDEV-5949)
  3. Fix for GTID duplicate key multi-master corruption bug (MDEV-5804)
  4. Default TokuDB compression is now TOKUDB_ZLIB (instead of TOKUDB_UNCOMPRESSED)
  5. Various algorithm improvements for engine-independent table statistics (EITS) (MDEV-5901, MDEV-5917, MDEV-5950, MDEV-5962, MDEV-5926)

You can read more about the 10.0.10 release here:

https://mariadb.com/kb/en/mariadb-10010-release-notes/

And if interested, you can review the full list of changes in 10.0.10 (changelogs) here:

https://mariadb.com/kb/en/mariadb-10010-changelog/

Hope this helps.

 

MariaDB 10.0.9 Overview and Highlights

Friday, March 14th, 2014

MariaDB 10.0.9 was recently released, and is available for download here:

https://downloads.mariadb.org/mariadb/10.0.9/

This is the second RC (“Release Candidate”) release of MariaDB 10.0, and 10th overall release of 10.0. All features planned for MariaDB 10.0 GA are included in this release.

There were 6 notable changes in MariaDB 10.0.9:

  1. InnoDB upgraded to version 5.6.15
  2. Extended-keys optimization is now enabled by default.
  3. MariaDB can be compiled to use the system’s PCRE library.
  4. Added MASTER_GTID_WAIT() and @@last_gtid.
  5. When a TIME value is casted to a DATETIME, the date part will be the CURRENT_DATE, not 0000-00-00. This is compatible with the SQL standard and MySQL-5.6. One can use @@old_mode=ZERO_DATE_TIME_CAST to revert to the old behavior.
  6. XtraDB is now the default InnoDB implementation, Oracle InnoDB is a plugin that can be dynamically loaded if desired.
  7. Builds for Debian Sid and Ubuntu Trusty are being made available for the first time in the MariaDB repositories. For this release the Trusty packages are considered as alpha releases. The Sid packages will likely always be considered as such. Both were made as part of normal MariaDB development, and we’re making them available for those that want to test or try them out.

Also, if you read my MariaDB 10.0.8 Overview post, you will have noticed there was a build issue with Percona’s XtraDB that was preventing it from being the default in MariaDB 10.0. I’m glad I posted about it, as the MariaDB and Percona Devs began working together immediately, and resolved the issue in days, and now XtraDB+ is back the default InnoDB in MariaDB 10.0. (This is mentioned in the bullet point #6 above, but I wanted to explicitly mention it as well, so it did not go unnoticed.)

You can read more about the 10.0.9 release here:

https://mariadb.com/kb/en/mariadb-1009-release-notes/

And if interested, you can review the full list of changes in 10.0.9 (changelogs) here:

https://mariadb.com/kb/en/mariadb-1009-changelog/

Hope this helps.

 

MariaDB 5.5.36 Overview and Highlights

Friday, March 14th, 2014

MariaDB 5.5.36 was recently released (it is the latest MariaDB 5.5), and is available for download here:

https://downloads.mariadb.org/mariadb/5.5.36/

This is a maintenance release, and so there are not too many big changes of note, just a number of normal bug fixes. However, there are a couple items worth mentioning:

  1. Includes all bugfixes and updates from: MySQL 5.5.36
  2. TokuDB is now included in RPM packages for CentOS 6 on x86-64

Note this release did not contain the bugfixes from XtraDB 5.5.36 yet. There is one bug fix in XtraDB 5.5.36 that is fairly serious, so if you are a *heavy* XtraDB+ user, I might wait for MariaDB 5.5.37 to be released, so you get this fix. I should note the bug was partially fixed in 5.5.35, and I did not see reports of the same issues in 5.5.35, so perhaps that covered it, or at least the majority. 5.5.34 had the worst of this bug, so if you are running 5.5.34, then I *would* definitely recommend upgrading.

Additionally, if you are using MySQL’s InnoDB in MariaDB, then I would definitely recommend upgrading to MariaDB 5.5.36 as well.

If interested, there is more about the 5.5.36 release here:

https://mariadb.com/kb/en/mariadb-5536-release-notes/

And the full list of fixed bugs and changes in MariaDB 5.5.36 can be found here:

https://mariadb.com/kb/en/mariadb-5536-changelog/

Hope this helps.

 

MariaDB 10.0.8 Overview and Highlights

Tuesday, February 11th, 2014

MariaDB 10.0.8 was recently released as RC (“Release Candidate”), and is available for download here:

https://downloads.mariadb.org/mariadb/10.0.8/

This is the first RC release of MariaDB 10.0. It is primarily a bug-fix and polishing release, and all features planned for MariaDB 10.0 GA are included in this release.

There were 6 notable changes in MariaDB 10.0.8:

  1. InnoDB upgraded to version 5.6.14
  2. FLUSH … FOR EXPORT works
  3. Added a new server variable, old_mode, to allow selectively restoring old behavior, in contrast to the old “all-or-nothing” approach of the –old command-line option. See OLD MODE for more.
  4. Added a new read-only server variable malloc_library
  5. Bundled PCRE library upgraded to version 8.34
  6. The CREATE OR REPLACE TABLE statement was added. It is used internally for replicating CREATE … SELECT statements (MDEV-5491), but it is also can be used by clients as any other SQL statement.

You can read more about the 10.0.8 release here:

https://mariadb.com/kb/en/mariadb-1008-release-notes/

And if interested, you can review the full list of changes in 10.0.8 (changelogs) here:

https://mariadb.com/kb/en/mariadb-1008-changelog/

Hope this helps.

 

MariaDB 5.5.35 Overview and Highlights

Thursday, February 6th, 2014

MariaDB 5.5.35 was recently released (it is the latest MariaDB 5.5), and is available for download here:

https://downloads.mariadb.org/mariadb/5.5.35/

This is a maintenance release, and so there are not too many big changes of note. However, there are a couple items worth mentioning:

  1. Includes all bugfixes and updates from: MySQL 5.5.35
  2. Includes all bugfixes and updates from: XtraDB from Percona-Server-5.5.35-rel33.0
  3. New SQL_MODE: OLD_MODE – to emulate behavior from old MySQL/MariaDB versions

You can read more about OLD_MODE here, if interested:

https://mariadb.com/kb/en/old_mode/

Also, there is more about the 5.5.35 release here:

https://mariadb.com/kb/en/mariadb-5535-release-notes/

And the full list of fixed bugs and changes in MariaDB 5.5.35 can be found here:

https://mariadb.com/kb/en/mariadb-5535-changelog/

Hope this helps.

 

MariaDB 10.0.7 Overview and Highlights

Wednesday, February 5th, 2014

MariaDB 10.0.7 was recently released (it is the latest MariaDB 10.0), is currently “beta”, and is available for download here:

https://downloads.mariadb.org/mariadb/10.0.7/

I just wanted to note a couple of the main highlights, which are:

  1. XtraDB storage engine was upgraded to the 5.6 version. Now one can use XtraDB with MariaDB 10.0. Unlike MariaDB 5.5, in 10.0 XtraDB is not the default engine, the default is InnoDB, and XtraDB is available as a dynamic plugin.
  2. OQGraph storage engine was upgraded to the version 3. Unlike OQGraph v2, that stores all the data in memory, new OQGraph v3 stores them in a table of another storage engine, on disk. Which makes your graphs persistent and also can support much larger graphs. See the OQGraph documentation for details.
  3. A new plugin metadata_lock_info was added. It implements a new table INFORMATION_SCHEMA.METADATA_LOCK_INFO that shows active metadata locks.

https://mariadb.com/kb/en/mariadb-1007-release-notes/

And for reference, the full 10.0.7 changelog can be viewed here:

https://mariadb.com/kb/en/mariadb-1007-changelog/

Hope this helps.

Troubleshooting Building MariaDB 5.1 on Windows

Tuesday, June 18th, 2013

This is a follow-up, troubleshooting article that goes hand-in-hand with my “Building MariaDB 5.1 on Windows Revisited” post, and covers some problems and their solutions that one might encounter when attempting to build MariaDB from source code on Microsoft Windows.

The first error I ran into was this, on my main compile step (i.e., the 2nd cmake command):

C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.Cpp
Common.targets(151,5): error MSB6006: "cmd.exe" exited with code 1.
[C:\mysql\mariadb-5.1.67\bld\scripts\GenFixPrivs.vcxproj]

That in itself doesn’t tell us too much. Searching the full compile output, we find:

Generating ../../scripts/mysql_fix_privilege_tables.sql
The system cannot find the file specified.
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.Cpp
Common.targets(151,5): error MSB6006: "cmd.exe" exited with code 1.
[C:\mysql\mariadb-5.1.67\bld\scripts\GenFixPrivs.vcxproj]
Done Building Project
"C:\mysql\mariadb-5.1.67\bld\scripts\GenFixPrivs.vcxproj" (default targets)
 -- FAILED.

Thus, there is a path issue. In this case, I had created a directory named “bld” within mysql-5.1.67/ and was attempting to build (and run cmake) there. After seeing this error, I deleted bld/ and just compiled in the main dir.

This helped things progress further on the next compile.

However, while it progressed further, I encountered a new set of errors:

"C:\mysql\mariadb-5.1.67\package.vcxproj" (default target) (1) ->
(PostBuildEvent target) ->
  EXEC : CPack error : Cannot find NSIS compiler makensis:
    likely it is not installed, or not in your PATH
    [C:\mysql\mariadb-5.1.67\package.vcxproj]
  EXEC : CPack error : Could not read NSIS registry value.
    This is usually caused by NSIS not being installed. Please install NSIS
    from http://nsis.sourceforge.net [C:\mysql\mariadb-5.1.67\package.vcxproj]
  EXEC : CPack error : Cannot initialize the generator NSIS
    [C:\mysql\mariadb-5.1.67\package.vcxproj]
  ...
    17 Warning(s)
    4 Error(s)

These seem related to NSIS, and so I’ll follow the note from the error message: Please install NSIS from http://nsis.sourceforge.net

Thus I downloaded NSIS and installed it (since I didn’t already have it installed). I then re-ran the 2nd cmake command, and it progressed further than before.

However, I was still not out of the woods yet. This time it produced:

  CPack: Create package using NSIS
  CPack: Install projects
  CPack: - Install project: MySql
  CPack: -   Install component: Unspecified
  CPack: -   Install component: headers
  CPack: -   Install component: mysqltest
  CPack: -   Install component: runtime
  CPack: -   Install component: scripts
  CPack: -   Install component: sqlbench
  CPack: Create package
EXEC : CPack error : Problem running NSIS command:
  "C:/Program Files (x86)/NSIS/makensis.exe"
  "C:/mysql/mariadb-5.1.67/_CPack_Packages/win32/NSIS/project.nsi"
  [C:\mysql\mariadb-5.1.67\package.vcxproj]
  Please check C:/mysql/mariadb-5.1.67/_CPack_Packages/win32/NSIS/NSISOutput.log
  for errors
EXEC : CPack error : Problem compressing the directory
  [C:\mysql\mariadb-5.1.67\package.vcxproj]
EXEC : CPack error : Error when generating package: MariaDB
  [C:\mysql\mariadb-5.1.67\package.vcxproj]
...
Done Building Project "C:\mysql\mariadb-5.1.67\package.vcxproj" (default targets)
 -- FAILED.
Build FAILED.

    0 Warning(s)
    4 Error(s)

Upon examining the above, we see the main error is:

EXEC : CPack error : Problem running NSIS command:
  "C:/Program Files (x86)/NSIS/makensis.exe"
  "C:/mysql/mariadb-5.1.67/_CPack_Packages/win32/NSIS/project.nsi"
  [C:\mysql\mariadb-5.1.67\package.vcxproj]
  Please check C:/mysql/mariadb-5.1.67/_CPack_Packages/win32/NSIS/NSISOutput.log
  for errors

I checked the log it mentions to see what is going on, and the last 2 lines of NSISOutput.log say:

!macro: macro named "RemoveSection" already found!
Error in script "C:/mysql/mariadb-5.1.67/_CPack_Packages/win32/NSIS/project.nsi"
on line 134 -- aborting creation process

Re-looked at error, which says “Problem running NSIS command …”

Thus I tried to run said command, exactly as-is, to see if it runs and/or what it reports:

C:\> "C:/Program Files (x86)/NSIS/makensis.exe" "C:/mysql/mariadb-5.1.67/_CPack_Packages/win32/NSIS/project.nsi"

Output is basically identical to that in NSISOutput.log, aside from 2 comments at the very beginning of NSISOutput.log (which shows the command run). The last 2 lines are (shown in ‘red’ in my terminal):

!macro: macro named "RemoveSection" already found!
Error in script "C:/mysql/mariadb-5.1.67/_CPack_Packages/win32/NSIS/project.nsi"
on line 134 -- aborting creation process

So what is this “RemoveSection”? Need to check project.nsi on line 134.

Searched the file, is only there once, so not sure where else it is coming from (i.e., how it is “already found!”).

So I decided to Google: “macro named “RemoveSection” already found”

1st result, bingo! Known bug!

“0013202: CPack fails with latest prerelease NSIS”

http://public.kitware.com/Bug/view.php?id=13202

Bug says, “Fixed in Version CMake 2.8.11″, so I checked my cmake version:

C:\>cmake –version
cmake version 2.8.10.2

Thus it is an affected version of cmake, therefore I need to upgrade cmake.

I downloaded the latest cmake, 2.8.11.1, and then upgraded it:

C:\Windows\system32>cmake --version
cmake version 2.8.11.1

So now re-run cmake command again:

cmake --build . --config relwithdebinfo --target package

Worked!!!!!!!

Build succeeded.
    0 Warning(s)
    0 Error(s)

Hope this helps. :)

 

Related Build Links:

 

Building MariaDB 5.1 on Windows Revisited

Tuesday, June 18th, 2013

I previously wrote an article on Building MariaDB 5.1 on Windows, but it was about 1.5 years ago (for 5.1.60; this is for 5.1.67), so I wanted to update this a little since I’ve built it entirely from the command-line this time (as well as highlight a couple problems/solutions – which I’ll cover in a subsequent troubleshooting post). This process it quite similar to my steps for building MariaDB 5.5 and MariaDB 10.0, however it’s slightly different since 5.1 requires you run the configure.js script before running cmake. Aside from that though, things are mostly the same. :)

Here is the full procedure:

Download 5.1.67 MariaDB source and extract to C:\mysql\mariadb-5.1.67
cd C:\mysql\mariadb-5.1.67
win\configure.js
cmake .
cmake --build . --config relwithdebinfo --target package

There you have it. MariaDB-5.1.67-win32.exe is created in the main dir. Also, it, and other related files, can be found in C:\mysql\mariadb-5.1.67\_CPack_Packages\win32\NSIS as well.

And for those interested, here is my [mostly] full output (I’ll spare you the “full” build/compilation outputs):

C:\>cd C:\mysql\mariadb-5.1.67

C:\>cd C:\mysql\mariadb-5.1.67

C:\mysql\mariadb-5.1.67>win\configure.js

C:\mysql\mariadb-5.1.67>cmake .
-- Building for: Visual Studio 10
-- The C compiler identification is MSVC 16.0.30319.1
-- The CXX compiler identification is MSVC 16.0.30319.1
-- Check for working C compiler using: Visual Studio 10
-- Check for working C compiler using: Visual Studio 10 -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler using: Visual Studio 10
-- Check for working CXX compiler using: Visual Studio 10 -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
build CSV as static library (libcsv.lib)
build FEDERATEDX as static library (libfederatedx.lib)
build HEAP as static library (libheap_s.lib)
build MARIA as static library (libmaria_s.lib)
build MYISAM as static library (libmyisam_s.lib)
build MYISAMMRG as static library (libmyisammrg_s.lib)
build PBXT as static library (libpbxt_s.lib)
build XTRADB as static library (libxtradb.lib)
build ARCHIVE as DLL (ha_archive.dll)
build BLACKHOLE as DLL (ha_blackhole.dll)
build EXAMPLE as DLL (ha_example.dll)
build FEDERATED as DLL (ha_federated.dll)
build INNODB_PLUGIN as DLL (ha_innodb_plugin.dll)
CMake Warning at C:/Program Files (x86)/cmake/share/cmake-2.8/Modules/
InstallRequiredSystemLibraries.cmake:343 (message):
  system runtime library file does not exist:
  'MSVC10_REDIST_DIR-NOTFOUND/x86/Microsoft.VC100.CRT/msvcp100.dll'
Call Stack (most recent call first):
  CMakeLists.txt:562 (INCLUDE)

CMake Warning at C:/Program Files (x86)/cmake/share/cmake-2.8/Modules/
InstallRequiredSystemLibraries.cmake:343 (message):
  system runtime library file does not exist:
  'MSVC10_REDIST_DIR-NOTFOUND/x86/Microsoft.VC100.CRT/msvcr100.dll'
Call Stack (most recent call first):
  CMakeLists.txt:562 (INCLUDE)

-- Configuring done
-- Generating done
-- Build files have been written to: C:/mysql/mariadb-5.1.67

C:\mysql\mariadb-5.1.67>cmake --build . --config relwithdebinfo --target package
......
...... tons of output ......
......
PostBuildEvent:
  ...
  CPack: Create package using NSIS
  CPack: Install projects
  CPack: - Install project: MySql
  CPack: -   Install component: Unspecified
  CPack: -   Install component: headers
  CPack: -   Install component: mysqltest
  CPack: -   Install component: runtime
  CPack: -   Install component: scripts
  CPack: -   Install component: sqlbench
  CPack: Create package
  CPack: - package: C:/mysql/mariadb-5.1.67/MariaDB-5.1.67-win32.exe generated.
FinalizeBuildStatus:
  Deleting file "Win32\relwithdebinfo\PACKAGE\PACKAGE.unsuccessfulbuild".
  Touching "Win32\relwithdebinfo\PACKAGE\PACKAGE.lastbuildstate".
Done Building Project "C:\mysql\mariadb-5.1.67\package.vcxproj" (default targets).

Build succeeded.
    0 Warning(s)
    0 Error(s)

Time Elapsed 00:13:53.66

Hope this helps. :)

 

 

MariaDB 5.3 is now GA

Tuesday, March 20th, 2012

This is another, in-case-you-missed-it, but it is definitely worth mentioning again:

MariaDB 5.3 is now GA

So, if you’re using MariaDB 5.1 or 5.2, I’d definitely recommend upgrading to the new MariaDB 5.3.

Also, if you’re a Windows user using MySQL 5.1, I’d highly consider making the switch to MariaDB 5.3 due to all of the Windows-specific improvements in it.

MariaDB 5.3 Enhancements:

  • Subquery optimizations
  • Semi-join subquery optimizations
  • Non-semi-join optimizations
  • Subquery Cache
  • Subquery Optimizations Map
  • Optimizations for derived tables and views
  • Disk access optimization
  • Join optimizations
  • Index Merge improvements
  • Optimizer control
  • NoSQL-style interfaces
  • Group commit for the binary log
  • Replication and binary logging enhancements
  • Microsecond support for NOW() and timestamp, time, and datetime columns
  • Windows performance improvements
  • And a number of other general improvements

MariaDB 5.3 Windows-Specific Performance improvements include:

  • Backported Windows performance patches from MySQL 5.5
  • Asynchronous IO in XtraDB is redesigned and is now faster, due to the use of IO completion ports
  • Additional durability option for XtraDB : innodb_flush_method can now be O_DSYNC, like on Unixes. (The effect of using this option is that the log file is opened with FILE_FLAG_WRITETHROUGH, and FlushFileBuffers() is not done. This may improve speed in write-heavy scenarios.)
  • A new Windows MSI installer
  • Includes a GUI-tool, HeidiSQL

All of the above, and more are documented in further detail here:

http://kb.askmonty.org/en/what-is-mariadb-53

You can download it here:

http://downloads.askmonty.org/mariadb/5.3/

(And just for reference, if running MariaDB you should probably keep your eye on the new MariaDB 5.5 too (5.5.20 was alpha, 5.5.21 is now beta), benchmarks here).

Hope this helps.

MariaDB 5.5 has been Released

Thursday, March 8th, 2012

In case you didn’t notice it last week, MariaDB 5.5 (5.5.20, specifically) has been released.

It’s a release I’ve been looking forward to for a while now, so I’m very excited that it’s now available! :)

Note that it is currently ‘alpha’ since it is the very first release of MariaDB 5.5. However, it is not your typical new ‘alpha’, so I would expect it to be GA in the not-so-distant future (please don’t quote me on this though, as I have no idea of the true time table – but the goal is for the next 5.5 release to be ‘beta’).

You can download MariaDB 5.5 from the following location:

http://downloads.askmonty.org/mariadb/5.5/

There are also more details on this 5.5.20 MariaDB version here:

What is MariaDB 5.5
Release Notes
Changelog
General Info

 


Period Panties by Period Panteez Menstrual Underwear Menstruation PMS Panty