Norbert Tretkowski

Today I uploaded MySQL 5.1.23 to Debian experimental. It is currently waiting in the NEW queue for manual approval, because thanks to Monty Taylor the libndb parts are now in separate binary packages libndbclient3 and libndbclient-dev. Until it is getting approved to experimental, the updated package is available (amd64 only) from my home directory on gluck.

Last week I uploaded MySQL 5.0.51a-1 to Debian unstable. Usually not worth a separate blog entry, but in this release I included the patch for MySQL bug #4541, which was opened more than three years ago. The problem results in an error like this, e.g. when migrating a database from latin1 to utf8:

Specified key was too long; max key length is 1000 bytes

The patch from Ingo Strüwing now included in Debian raises the maximum key length to 4005 bytes or 1001 UTF-8 characters. It will not go into the official MySQL source repositories because it results in bigger buffers and as such increases memory footprint and decreases performance. See the bugreport for further details.

Update: After some criticism from MySQL (see comments) I decided to disable the patch in the default builds with the next upload, but still ship it in the source package.

Today I uploaded an updated backport of the linux-2.6 package. It is based on 2.6.22-6, which was the last 2.6.22 series kernel available in Debian unstable, and includes the upstream patches from 2.6.22.12 (2.6.22.12-rc1 was included in 2.6.22-6) up to 2.6.22.18 (the user pointer access fix in get_iovec_page_array(), main reason for this update), and an update to the latest vserver patch.