From: Date: May 18 2004 7:46am
Subject: MySQL 4.0.20 Released
List-Archive: http://lists.mysql.com/announce/191
Message-Id: <C49549EE-A88E-11D8-9DE9-000A95B48A2A@mysql.com>
MIME-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit

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 heikki@stripped +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 heikki@stripped +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 heikki@stripped +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
patg@stripped http://www.mysql.com