This week MySQL released version 5.0.75 of their Community Edition. The package in testing is in good shape, so I had time to prepare and upload 5.0.75-1 to unstable, but it should work on testing as well. I also made a rebuild for etch, which is available here.

In the next upload of MySQL 5.1.30 to the experimental branch of Debian we are going to drop MySQL Cluster support from the standard MySQL packages. I already wrote something about the future of MySQL Cluster in Debian a while ago, this is just the first step towards a separate mysql-cluster package in Debian.

This change does not (and will never) affect the MySQL packages in etch and lenny, and unstable not until we decide to move MySQL 5.1 from experimental to unstable.

In the next upload of MySQL 5.1.30 to the experimental branch of Debian we are going to drop MySQL Cluster support from the standard MySQL packages. I already wrote something about the future of MySQL Cluster in Debian a while ago, this is just the first step towards a separate mysql-cluster package in Debian.

This change does not (and will never) affect the MySQL packages in etch and lenny, and unstable not until we decide to move MySQL 5.1 from experimental to unstable.

Installing Nginx With PHP5 And MySQL Support On Debian Etch

Nginx (pronounced "engine x") is a free, open-source, high-performance HTTP server. Nginx is known for its stability, rich feature set, simple configuration, and low resource consumption. This tutorial shows how you can install Nginx on a Debian Etch server with PHP5 support (through FastCGI) and MySQL support.

Setting Up Master-Master Replication On Four Nodes With MySQL 5 On Debian Etch

This tutorial explains how you can set up MySQL master-master replication on four MySQL nodes (running on Debian Etch). The difference to a two node master-master replication is that if you have more than two nodes, the replication goes in a circle, i.e., with four nodes, the replication goes from node1 to node2, from node2 to node3, from node3 to node4, and from node4 to node1.

Hello, there! With another Ubuntu release, it has come the time to update our series of posts on how to install Oracle 11g on Ubuntu. If you’ve been following, we’ve been publishing updated howtos since Ubuntu 7.04:

• Installing Oracle 11g on Ubuntu 8.04 Hardy Heron LTS
• Installing Oracle 11g on Ubuntu 7.10 Gutsy Gibbon
• Installing Oracle 11g on Ubuntu 7.04 Feisty Fawn

In fact, in this article I refer several times to previous posts regarding some configuration aspects and why I chose particular values. Also, note that this series of posts is a work in progress and we were able to improve this series with your help. So please do post comment below as …

Preventing MySQL Injection Attacks With GreenSQL On Debian Etch

GreenSQL (or greensql-fw) is a firewall for MySQL databases that filters SQL injection attacks. It works as a reverse proxy, i.e., it takes the SQL queries, checks them, passes them on to the MySQL database and delivers back the result from the MySQL database. It comes with a web interface (called greensql-console) so that you can manage GreenSQL through a web browser. This guide shows how you can install GreenSQL and its web interface on a Debian Etch server.

This morning I finally found some time to add an init script to the Debian package of mysql-proxy (0.6.1-3 which includes it was just uploaded to unstable, I will try to get a freeze exception for lenny). It is disabled by default, because mysql-proxy is quite useless without a proper configuration. It can be enabled in /etc/default/mysql-proxy, here is an example:ENABLED="true"
OPTIONS="--proxy-lua-script=/usr/share/mysql-proxy/rw-splitting.lua
         --proxy-address=192.168.1.140:3306
         --proxy-backend-addresses=192.168.1.20:3306
         --proxy-read-only-backend-addresses=192.168.1.23:3306
         --proxy-read-only-backend-addresses=192.168.1.24:3306"In this example the proxy binds to 192.168.1.140 port 3306 and does …

This morning I finally found some time to add an init script to the Debian package of mysql-proxy (0.6.1-3 which includes it was just uploaded to unstable, I will try to get a freeze exception for lenny). It is disabled by default, because mysql-proxy is quite useless without a proper configuration. It can be enabled in /etc/default/mysql-proxy, here is an example:ENABLED="true"
OPTIONS="--proxy-lua-script=/usr/share/mysql-proxy/rw-splitting.lua
         --proxy-address=192.168.1.140:3306
         --proxy-backend-addresses=192.168.1.20:3306
         --proxy-read-only-backend-addresses=192.168.1.23:3306
         --proxy-read-only-backend-addresses=192.168.1.24:3306"In this example the proxy binds to 192.168.1.140 port 3306 and does …

Last weekend I updated the Debian package of MySQL to 5.0.67, the latest Community Edition release. It was not uploaded into the Debian archive, but is available from my home directory on gluck (amd64 only at the moment). The next Debian release lenny is frozen already, which means no newer upstream releases get accepted into testing before lenny is released, hence lenny definitely gets shipped with MySQL 5.0.51a. We will not see MySQL 5.0.67 or 5.1 in lenny, but we will continue providing backports of newer MySQL releases.

Our current primary goal regarding the MySQL packages in Debian is to get 5.0.51a in shape for lenny, so please do not send us mails asking about MySQL 5.1 …