Potential crashing bug in MySQL 4.0.19

Lenz Grimmer <[email protected]>
Newsgroups gmane.comp.db.mysql.devel,gmane.comp.db.mysql.general,gmane.comp.db.mysql.packagers
Message-ID <[email protected]>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

Some of you may have noted that we have uploaded the MySQL 4.0.19 binaries
to our mirrors, but have not sent out an announcement or updated the web
pages yet.

The MySQL 4.0.19 binaries were uploaded to the download mirrors on May,
10th. However, a potential crashing bug in MySQL 4.1 was found and
confirmed to affect the 4.0.19 release as well. This happened just shortly
before the release was publicly announced and published on the 4.0
download pages at http://dev.mysql.com/.

See Bug #3596 for details (it was initially reported against MySQL-4.1,
but was confirmed to exits 4.0.19 as well).

A fix for this bug was pushed into the MySQL source tree quickly after it
could be reproduced and will be included in the upcoming MySQL 4.0.20, to
be released shortly.

We recommend our users to stick to MySQL 4.0.18 for the time being, until
MySQL 4.0.20 has been released (this specific bug was introduced after
MySQL 4.0.18 was released, so older versions were not affected by it).

We apologize for the inconvenience!

Bye,
	LenZ
- -- 
 Lenz Grimmer <[email protected]>
 Senior Production Engineer
 MySQL GmbH, http://www.mysql.de/
 Hamburg, Germany
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: For info see http://quantumlab.net/pine_privacy_guard/

iD8DBQFAo+IqSVDhKrJykfIRAhIZAJ0cqsKxuxYvfwy63E8lOxS+2xYbZgCfaFQw
BTnndPF57A9ZFROMSCCnKkM=
=bszb
-----END PGP SIGNATURE-----

-- 
MySQL Internals Mailing List
For list archives: http://lists.mysql.com/internals
To unsubscribe:    http://lists.mysql.com/[email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.