Changes in release 3.23.48
--------------------------
* Changed to use `autoconf' 2.52 (from `autoconf' 2.13)
* Fixed bug in complicated join with `const' tables.
* Added internal safety checks for InnoDB.
* Some InnoDB variables was always shown in `SHOW VARIABLES' as
`OFF' on high-byte-first systems (like sparc).
* Fixed problem with one thread using an InnoDB table and another
thread doing an `ALTER TABLE' on the same table. Before that,
mysqld could crash with an assertion failure in row0row.c, line
474.
* Tuned the InnoDB SQL optimizer to favor more often index searches
over table scans.
* Fixed a performance problem with InnoDB tables when several large
SELECT queries are run concurrently on a multiprocessor Linux
computer. Large CPU-bound SELECT queries will now also generally
run faster on all platforms.
* If MySQL binlogging is used, InnoDB now prints after crash
recovery the latest MySQL binlog name and the offset InnoDB was
able to recover to. This is useful, for example, when
resynchronizing a master and a slave database in replication.
* Added better error messages to help in installation problems of
InnoDB tables.
* One can now recover also MySQL temporary tables which have become
orphaned inside the InnoDB tablespace.
* InnoDB now prevents a `FOREIGN KEY' declaration where the
signedness is not the same in the referencing and referenced
integer columns.
* Calling `SHOW CREATE TABLE' or `SHOW TABLE STATUS' could cause
memory corruption and make mysqld to crash. Especially at risk was
`mysqldump', because it calls frequently `SHOW CREATE TABLE'.
* If inserts to several tables containing an auto-inc column were
wrapped inside one `LOCK TABLES', InnoDB asserted in lock0lock.c.
* In 3.23.47 we allowed several `NULLS' in a `UNIQUE' secondary
index for an InnoDB table. But `CHECK TABLE' was not relaxed: it
reports the table as corrupt. `CHECK TABLE' no longer complains in
this situation.
* `SHOW GRANTS' now shows `REFERENCES' instead of `REFERENCE'.