MySQL 4.0.20 Released

Patrick Galbraith <[email protected]>
Newsgroups gmane.comp.db.mysql.announce,gmane.comp.db.mysql.general,gmane.comp.db.mysql.packagers
Message-ID <[email protected]>
Dear MySQL users and developers,

MySQL 4.0.20, a new version of the popular Open Source/Free Software 
Database
  Management System, has been released. It is now available in source 
and binary
  form for a number of platforms from our download pages at
  http://www.mysql.com/downloads/ and mirror sites.


  Note that not all mirror sites may be up to date at this point in time 
-
  if you can't find this version on some mirror, please try again later 
or
  choose another download site.


This is a maintenance release of 4.0.x.

Please refer to our bug database at http://bugs.mysql.com/ for more
  details about the individual bugs fixed in this version.

News from the ChangeLog:

ChangeSet:

   1.1827 04/05/13 22:07:51 [email protected] +4 -0
   ha_innodb.cc, trx0trx.h, lock0lock.c, trx0trx.c:
   Reserve the MySQL LOCK_thread_count mutex when printing thd->query of
   an arbitrary transaction; if we are printing thd->query of a 
transaction that
   we know is currently executing inside InnoDB, then we know that MySQL 
cannot
   meanwhile change thd->query, and no need to reserve the MySQL mutex; 
note
   that this patch still leaves open the possibility of races in MySQL's
   thd->query_len

   sql/ha_innodb.cc
     1.207 04/05/13 22:01:11 [email protected] +34 -14
     Reserve the MySQL LOCK_thread_count mutex when printing thd->query 
of an arbitrary transaction; if we are printing thd->query of the a 
transaction that we know is currently executing inside InnoDB, then we 
know that MySQL cannot meanwhile change thd->query, and no need to 
reserve the MySQL mutex; note that thsi patch still leaves aopen the 
possibility of races in MySQL's thd->query_len

   innobase/include/trx0trx.h
     1.30 04/05/13 22:00:54 [email protected] +4 -2
     Reserve the MySQL LOCK_thread_count mutex when printing thd->query 
of an arbitrary transaction; if we are printing thd->query of the a 
transaction that we know is currently executing inside InnoDB, then we 
know that MySQL cannot meanwhile change thd->query, and no need to 
reserve the MySQL mutex; note that thsi patch still leaves aopen the 
possibility of races in MySQL's thd->query_len

... more changes listed in ChangeLog.


Thank you very much for using MySQL!

       Patrick Galbraith

Patrick Galbraith Senior Software Developer
[email protected] http://www.mysql.com


-- 
MySQL Announce Mailing List
For list archives: http://lists.mysql.com/announce
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.