|
All this started during a long drive from Charlottesville to Washington, back in November 2008, when I and Dups discussed the status of MySQL Community web presence. We agreed that we needed to enhance the usefulness of the tools for the community, and MySQL Planet was the first candidate for change. Externally, you have noticed very little until now. First, a login, then the voting system, the Buzz, the Italian, Japanese, and Russian aggregators, an improved treatment for group blogs, and finally the Tags and … |
|
All this started during a long drive from Charlottesville to Washington, back in November 2008, when I and Dups discussed the status of MySQL Community web presence. We agreed that we needed to enhance the usefulness of the tools for the community, and MySQL Planet was the first candidate for change. Externally, you have noticed very little until now. First, a login, then the voting system, the Buzz, the Italian, Japanese, and Russian aggregators, an improved treatment for group blogs, and finally the Tags and … |
The current release of MySQL Cluster 7.0 is based on MySQL Server
5.1.34, normally we update the MySQL Server version as soon as a
new one has been released. That is an almost automated process
since it's just another branch in bazaar - ie "bzr pull", resolve
any conflicts and commit.
The cluster team mainly work with the files in storage/ndb/ where
the source for ndbd, ndb_mgmd and all the ndb_* tools for working
with MySQL Cluster is kept. We have also produced improvements to
the MySQL Server itself. While most of them have been merged back
up - either to 5.1 or 6.0 - some hasn't. This means that when
someone touch an are that has been improved we get a few
conflicts when merging down the latest MySQL Server version.
Fortunately that is quite rare now when 5.1 is GA.
Some of the improvements are generic and simply improves MySQL
Server's portability, while some are specific and useful only for
ha_ndbcluster(the MySQL …
In large vBulletin forum we had strange problem in memory table "session", we've 25M post, 1.7M user, 20K online user.So we change engine of session table to InnoDB and set configuration of innoDB as follow (be careful this configuration is not proper for other tables because this is good in performance but bad in crash and recovery, and data reliability)innodb_data_home_dir = /dev/shm/mysql/
If you had to configure a Wordpress MU installation without access to any details of your MySQL Configuration, what would you do?
What top five configuration settings would you use?
I asked the community this question, see For MySQL DBA fame and glory. Prize included and a number of brave soles responded for a chance to win a free copy of MySQL Administrators Bible by MySQL Community She-BA Sheeri Cabral.
There is no perfect answer and of course you would want to set more then five options, however the purpose of the competition was to seek what people would do with limited information and a limited choice of …
[Read more]Ever since Sun Microsystems agreed to acquire MySQL back in 2008, there has been a fair bit of uncertainty and chaos surrounding the world’s most popular Open Source database. With many big names in the MySQL community pulling in different directions and the recent Oracle / Sun acquisition, the choice of which Open Source database to use is now easier than ever – PostgreSQL. …
[Read more]
Hi,
We are currently running code coverage for MySQL Cluster testing
and have hit a few bumps along the road when it cam to collecting
the "block" coverage for the NDBD.
I wanted to share them here for others that might run into
similar frustrations when doing testing code coverage.
Gcov accumulates during each run information on which functions
and lines of code are called and a total for the times
called.
The problem comes from when gcov dumps this information out. The
actual data is dumped on the "exit" of the program.
After much time tracking this issue down, it turns out that the
NDBD code had been changed to use _exit() instead of just
exit()
What is the difference?
exit()
Terminate the process after cleanup.
_exit()
Terminate process immediately.
So by calling _exit(), gcov never had a …
My last post about Basic MySQL Security generated a number of interesting comments, thanks for all your feedback! I'd like to address a few points that were mentioned there:
While the problem seems to be a non-issue on Linux, Keith Murphy stated that the password might still be visible on other Unix operating systems (e.g. Solaris), as described in Bug#11952 in our bug database. According to the bug report, it depends on the implementation of "ps" — there seems to be a BSD variant (/usr/ucb/ps) as well as a SysV implementation (/usr/bin/ps).
…
[Read more]
I am going to Madrid, Spain, to participate in the Open Communities Forum on June 18-19.
As usual with Sun open events, the agenda includes several actors
in the open source arena, such as MySQL, Java, Open Solaris, with
topics ranging from web development to mobile integration.
It looks promising, and I look forward to this event, which is my
first one in Spain.
On the first day, I will do an introductory talk about MySQL, and
a more technical workshop for advanced users. The second day will
be mainly dedicated to meeting users in the area, but I will also
do a guest appearance in a talk about database testing.