Backport from 4.1: make sure change_active_index is only called with a properly initialized InnoDB table handle

  Make SHOW INNODB STATUS aware when we are estimating index range size etc.

  Backport from 4.0: fix the BLOB hang if the index tree is of height 1

  Backport from 4.0: fix possible adaprive hash index latch hang

  Fix a typo

  Fix a possible hang at the adaptive hash index latch if MySQL does query estimations also in the middle of a SELECT statement processing

  Make SHOW INNODB STATUS aware which trx's are waiting because of innodb_thread_concurrency exceeded

  Print also the thread ids in SHOW INNODB STATUS also in Linux

Allocate bigger default thread stack because of problems with glibc
Fixed bug in UPDATE ... not_null_field=expression_that_returns_null
Fixed bug in replication when using auto_increment and LOAD DATA INFILE

  Backport the InnoDB HANDLER bug fix from 4.1

  Fix a hang associated with an index tree of height 1 and purging of BLOB fields from it

  Add another diagnostic print to determine why the 'queries inside InnoDB' counter might drift upwards

  Add diagnostic prints to determine why the 'queries inside InnoDB' might drift upwards
ha_innodb.cc:
  Add more print space to SHOW INNODB STATUS; remove possible memory leak in case there is an error

Fixed problem with replication LOAD DATA INFILE when using  --old-rpl-compat.
When executing on master LOAD DATA and InnoDB failed with 'table full' error the binary log was corrupted.

Free row buffer cache after each query for MyISAM tables.
Added table join option FORCE INDEX
Fixed core dump bug when connecting with hostname that could not be resolved.

into sergbook.mysql.com:/usr/home/serg/Abk/mysql-4.0

  no _mi_search_next() bug fixed

Fix for SHOW VARIABLES in embedded server

  Remove the warning message that mem allocation spills from the additional mem pool to the OS; this does not hit performance with modern malloc libraries

Fixed test suite for HPUX 10.20 and MacOSX

  Backport bugfix from 4.0: combined log file size >= 2 GB could cause log to be written in wrong place
btr0pcur.c:
  Backport bugfix from 4.0: index cursor restoration could theoretically fail

  Fix bug: an index cursor can theoretically be restored in a wrong place
log0log.c:
  Fix bug: if combined log file size is >= 2 GB in a 32-bit computer InnoDB can write log to a wrong position

Added rename table for BDB. This fixes a bug in ALTER TABLE with BDB tables.