On friday we released the second Beta version of PBXT. PBXT is a transactional storage engine for MySQL 5.1 and 6.0. You can find out more about the engine at www.primebase.org.
PBXT is pluggable, so it can be built separately from the MySQL tree, and loaded dynamically at runtime using the LOAD PLUGIN statement.
You can download PBXT from here. A "quick guide" to building and installing the plugin is provided. I have also updated the documentation for this version.
There are no major new features in this release because we are working towards the RC version in December. But we wrote some release notes to prove we have been busy :)
There is now also a version of PBXT available for Drizzle. You will find the source code here: https://code.launchpad.net/~drizzle-pbxt/drizzle/pbxt.
By the way, did any of you see this report: Sun releases MySQL 5.1?! It's dated 7 Nov, but no sign of the new release on the MySQL website ... to bad.
Showing posts with label beta. Show all posts
Showing posts with label beta. Show all posts
Monday, November 10, 2008
Monday, September 01, 2008
PBXT Beta Version Released!
I am pleased to announce that the Beta version of PBXT has just been released. You can download the source code of the storage engine from www.primebase.org/download. I have also updated the documentation for this version.
Configuring and building the engine is easier than ever now. To configure PBXT all you have to do is specify the path to the MySQL source code tree (after building MySQL), for example:
./configure --with-mysql=/home/foo/mysql/mysql-5.1.26-rc
The PBXT configure command will retrieve all required options from the MySQL build. For example whether to do a debug or optimized build and where to install the plugin are determined automatically, depending on how you configured MySQL.
This was a source of some mistakes when building the plugin, so I think it is really cool!
So what's next?
My goal is a RC (release candidate) version before the end of the year. Considering the stability of the new Beta, I think this is realistic.
The main work is testing, performance tuning, and fixing all those bugs you are about to find as you give PBXT a spin, right? :)
Besides, the size of the PBXT programming team will soon double! But more about that later...
Another thing I would love to do soon is a Drizzle version of PBXT. This has one significant advantage. If I discover a bottleneck in Drizzle, while performance tuning the engine, a patch for the problem in the server will probably be accepted fairly quickly.
But first I need to move PBXT to launchpad where all the music is playing these days!
Configuring and building the engine is easier than ever now. To configure PBXT all you have to do is specify the path to the MySQL source code tree (after building MySQL), for example:
./configure --with-mysql=/home/foo/mysql/mysql-5.1.26-rc
The PBXT configure command will retrieve all required options from the MySQL build. For example whether to do a debug or optimized build and where to install the plugin are determined automatically, depending on how you configured MySQL.
This was a source of some mistakes when building the plugin, so I think it is really cool!
So what's next?
My goal is a RC (release candidate) version before the end of the year. Considering the stability of the new Beta, I think this is realistic.
The main work is testing, performance tuning, and fixing all those bugs you are about to find as you give PBXT a spin, right? :)
Besides, the size of the PBXT programming team will soon double! But more about that later...
Another thing I would love to do soon is a Drizzle version of PBXT. This has one significant advantage. If I discover a bottleneck in Drizzle, while performance tuning the engine, a patch for the problem in the server will probably be accepted fairly quickly.
But first I need to move PBXT to launchpad where all the music is playing these days!
Subscribe to:
Posts (Atom)