I created and ran some simple tests on mysql and postgresql to figure out which one is faster. It is already known that postgresql is more stable and reliable than mysql. pgsql has a rich set of features. It is a complete RDBMS and also supports fulltext search.

All benchmarks were done on my laptop - Intel core 2 duo (2.0 GHz) with 4MB L2 cache & 2 GB ram. I have 64 Bit ubuntu system loaded

Nexaweb contributes code to open source Ajax effort. IBM releases v1.0 of Lotus Symphony. Zmanda teams with NetApp on MySQL backup. (and more)

Open Source Ajax Gains Enterprise Momentum With dojo.E Contribution From Nexaweb, Nexaweb Technologies (Press Release)

ODF Comes of Age: IBM Lotus Symphony Turns 1.0, IBM (Press Release)

Zmanda Teams with NetApp to Deliver Highly Optimized Backup Solution for MySQL, Zmanda / NetApp (Press Release)

Linux Framework Wars Down to Two Parties, ABI Research (Press Release)

…

We (the MySQL Web team) have now made it easier for you to keep track of upcoming MySQL Live Web Seminars as well as MySQL OnDemand Webinars - check out the new RSS Feeds:





Have you noticed the change on www.mysql.com?



BTW, did you see the RSS icon next to MySQL Training? This …

I was intrigued by this survey about MySQL today, and I took it.
Some of the questions made me think about the status of MySQL community. Unlike other free/open source projects, MySQL community people are not direct contributors to the project, but just users. Then there are the more advanced ones who keep an active role, and the majority who are just content to use it and don't even care to participate in blogs or forums.
Seen throrugh the articles in PlanetMySQL, the MySQL community has three components, with sub components:

• Sun/MySQL employees, who link between the noisy users and the company.
  • The ones who produce or advocate closed source
  • The ones who only deal with open source
  • The ones who tell interesting stories without taking sides.
  …

Keith Murphy and Mark Schoonover have put together an excellent survey which is already doing good (seeing the numbers they have been clocking). Survey results will be out in the summer issue of MySQL magazine. I feel this is a "must take" survey for everyone in the MySQL community. And do not forget to mention my blog in the "top 5 favorite MySQL blogs" ;-). Just kidding!

Overall, this is the best survey regarding MySQL that I have ever taken, don't miss it. It will hardly take 10 minutes of your busy schedule. A busy man has the time do anything, right?

Quick Links:

• …

In the next proxy release we introduce plugins, we talked about it already in http://jan.kneschke.de/projects/mysql/mysql-proxy-a-chassis-and-a-mysql-server. Take a look at http://svn.mysql.com/svnpublic/mysql-proxy/trunk/plugins/ and check out:

• proxy
• admin
• debug

each of them sharing the common code that is provided by the chassis.

The debug plugin is a lua shell with a mysql-protocol ... well, just read on ;)

The purpose of the plugin is to be able to introspect the proxy at runtime. If it is loaded you can connect to port 4043 and execute lua code inside the proxy core:

$ mysql --user=root --password=secret --port=4043 --host=192.168.2.113 …

There are now two ways how to do this:

1. Using "set debug=d,flag" and adding some DBUG_EXECUTE_IF("flag", abort()) we can trigger the server to crash at a specific place in the code. There is an example of this in crash_commit_before.test
This requires a debug compiled server so you need to add a "source include/have_debug.inc" at the beginning of the test.

2. There is also a new way to do it without using DBUG_. By using the new command in mysqltest called "shutdown_server"[1], we will tell the server to stop, wait a while(60 seconds) and finally kill it off. This way we get a reliable shutdown. The first testcase that uses this is events_restart.test

In both of these methods, the testcase has to write a small file before the "crash/shutdown", that file tells mysql-test-run.pl that it was an expected crash/shutdown. The server will be started up again with the same settings as before …

I’m very pleased to say that I’ve been invited to join CIO.com’s first Executives Online discussion panel, Open Source in the Enterprise, this week. As the starter post explains, the event is a virtual round table discussion bringing together a number of open source executives, and me, to discuss the enterprise adoption of open source software between today and Friday June 6.

It promises to be an interesting discussion, and CIO.com has been good enough to give us some starting discussions points with its survey of attitudes towards open source in the CIO community. I’ll be …

This column obfuscation scheme is designed so that information can be gathered about the query and underlying schema, by just looking at the query. You will be able to tell if it is using keys correctly just by looking at the column names in the query.

Column Name Obfuscation 

1. Table Prefix Columns of a table will be prefixed with a abbreviation or (from a list of random names that can be selected from a list following a theme or something) of the Obfuscated table name (when I tackle joins this will resolve and conflict in names that are going to occur)
   
2. Column Type, undecided on whether or not to just go with simplified names like (str|int|float|bin) or go with the full data type (i.e BININT,BLOB,DECIMAL,VARCHAR,TEXT…).
   

3. Keys, P[0-9] numbers are only for multi value PRIMARY KEYS.

   …

This is going to be an unusual blog post, because I will continuously update it with features that MySQL still has on top of PostgreSQL, which is generally considered to be more feature rich. Some of these missing features can however hurt a lot. I am including MySQL 5.1 in here, since eventhough its not yet released as GA, more and more people have started to use it in production. At the same time I am also including 8.4. So in a way I am talking about what MySQL has on top of PostgreSQL by the end of the year. I am not going to include stuff like auto increment if there is something that is more or less equivalent with SERIAL. I am also not including features I consider unwise (like REPLACE). Finally I am skipping XML support, because I know both are working on improving the support, but I have not yet looked at it so closely. So here it goes:

• Multiple charsets/collations in the same DB (all the way down to the column level)
…