into mysql.com:/my/mysql-4.1

into mysql.com:/my/mysql-4.1

into mysql.com:/usr/local/home/marty/MySQL/mysql-4.1

into mysql.com:/home/jonas/src/mysql-4.1

  after merge fix

into hundin.mysql.fi:/home/marko/k/mysql-4.1

into mysql.com:/my/mysql-4.1

into hundin.mysql.fi:/home/marko/j/mysql-5.0

It is not safe to infer the status bits from the B-tree page
level, because after MLOG_COMP_LIST_END_COPY_CREATED, the
level will not be initialized before the records have been inserted.
(Bug #7973)

into gw.mysql.r18.ru:/usr/home/ram/work/4.1.b7261

into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1

into gw.mysql.r18.ru:/usr/home/ram/work/5.0

into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0

    changed ndb_restore test somewhat to fisrt make the tables in myisam

into gw.mysql.r18.ru:/usr/home/ram/work/4.1.b7261

into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1

into hundin.mysql.fi:/home/jan/mysql-4.1

  Call file->external_lock() for handler objects that index_merge code creates in addition to 
  the handler object opened in open_and_lock_tables.

into mysql.com:/home/kostja/work/mysql-5.0-root

into mysql.com:/home/jimw/my/mysql-4.1-clean

it's crucial to disable Nagle algorithm on client for no-reply commands
(like mysql_stmt_free) to always work fast.
Nagle algorithm instructs the sender to buffer (store) data if any 
unacknowledged data is outstanding and the size of to-send data is less than
the network segment. It was exactly the case with COM_STMT_CLOSE after 
COM_STMT_PREPARE, so the client was waiting for Nagle timer to expire or
 for ACK from the server, while the server was holding up ACK because of 
delayed acknowledgement algorithm.
The tricky part is that we have been already disabling Nagle 
algorithm (by setting TCP_NODELAY)
almost everywhere except Windows (and maybe Netware).
It is the reason why the bug was repeatable only with Windows client.

into mysql.com:/home/jimw/my/mysql-4.1-clean

lower_case_tables_names=2 is sensible. Related to Bug #7887.

into serg.mylan:/usr/home/serg/Abk/mysql-4.1