Gebruikers van MySQL kunnen weer aan het upgraden slaan; versie 3.23.54 van deze zeer populaire database-server is uit. Het changelog geeft een aantal redenen om deze release op je server te installeren:
- Fixed a bug that made OPTIMIZE TABLE to corrupt the table under some rare circumstances.
- Fixed mysqlcheck so it can deal with table names containing dashes.
- Fixed the bug that caused IGNORE INDEX and USE INDEX sometimes to be ignored.
- Fixed rare core dump problem in complicated GROUP BY queries that didn't return any result.
- Fixed a bug where MATCH ... AGAINST () >=0 was treated as if it was >.
- One can create TEMPORARY MERGE tables now.
- Fixed that --core-file works on Linux (at least on kernel 2.4.18).
- Fixed a problem with BDB and ALTER TABLE.
- Fixed reference to freed memory when doing complicated GROUP BY ... ORDER BY queries. Symptom was that mysqld died in function send_fields.
- Allocate heap rows in smaller blocks to get better memory usage.
- Fixed memory allocation bug when storing BLOB values in internal temporary tables used for some (unlikely) GROUP BY queries.
- Fixed a bug in key optimizing handling where the expression WHERE column_name = key_column_name was calculated as true for NULL values.
- Fixed core dump bug when doing LEFT JOIN ... WHERE key_column=NULL.
- Fixed MyISAM crash when using dynamic-row tables with huge numbers of packed fields.
InnoDB 3.23.54 changelog:
[break]MySQL is geschikt voor elf verschillende besturingssystemen, zoek de versie van jouw voorkeur hier uit.
- Fixed a bug: the InnoDB range estimator greatly exaggerated the size of a short index range if the paths to the endpoints of the range in the index tree happened to branch already in the root. This could cause unnecessary table scans in SQL queries.
- Fixed a bug: ORDER BY could fail if you had not created a primary key to a table, but had defined several indexes of which at least one was a UNIQUE index with all its columns declared as NOT NULL.
- Fixed a bug: a lock wait timeout in connection with ON DELETE CASCADE could cause corruption in indexes.
- Fixed a bug: if a SELECT was done with a unique key from a primary index, and the search matched to a delete-marked record, InnoDB could erroneously return the NEXT record.
- Fixed a bug introduced in 3.23.53: LOCK TABLES ... READ LOCAL should not set row locks on the rows read. This caused deadlocks and lock wait timeouts in mysqldump.
- Fixed a bug: if an index contains some column twice, and that column is updated, the table will become corrupt. From now on InnoDB prevents creation of such indexes.
- An outstanding bug: in replication issuing SLAVE STOP in the middle of a multi-statement transaction can cause that SLAVE START will only perform part of the transaction.
Deze versie niet gebruiken op Linux, gebruik versie 3.23.54c of later!!
:strip_exif()/i/2001945307.png?f=thumbmedium)
/u/11473/notAvailable.PNG?f=community){kind=small}
/u/49083/armind_60.png?f=community){kind=small}