Mysql upstream update

[Scott Hanson <shanson@shcon.com>]

There's just been (yet another) upstream update to mysql 3.21. At this
late stage of the hamm beta, I'm inclined _not_ to submit it to
frozen, but rather only to unstable until there is a 'hamm updates'
procedure.

However, here's the upstream changelog in case any mysql users here
have experienced any of these problems and would like to see the new
version put into hamm. In that case, let me know.

Scott


  18.4.1 Changes in release 3.21.32

     * Fixed some possible race conditions when using with MySQL and many
       reopen/close of the same tables under heavy load! This could in
       some very rare case corrupt the header of the index file and cause
       error 126 or 138.
     * Fixed fatal bug in refresh() when running with --skip-locking here
       was a 'very small' time gap after a 'mysqladmin refresh' when a
       table can be corrupted if one thread updated a table while another
       thread did mysqladmin refresh and another thread started a new
       update at the same table before the first thread had finished. A
       Refresh (or --flush-tables) will now not return until all used
       tables was closed!
     * SELECT DISTINCT with a WHERE clause that didn't match any rows
       returned a row in some context (bug only in 3.21.31)
     * GROUP BY + ORDER BY returned one empty row when no rows where
       found.
     * Fixed a bug in range optimizer that wrote: "Use_count: Wrong count
       for ..." in the error log file.

                                                                           
-- 
Scott Hanson <shanson@shcon.com>  <shanson@debian.org>
Johmsweg 9, D-21266 Jesteburg, Germany


--  
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org