Fix for bug 254 : the first Start_log_event after server startup will
have created=now(), whereas the next ones (FLUSH LOGS, auto rotation)
will have created=0. Before this, it was always now().
This way, slaves >=4.0.14 will know when they must
drop stale temp tables or not. The next task is now modify 4.0.14 to
implement this.

into narttu.mysql.fi:/my/mysql-3.23

(Casused problems in GIS functions in 4.1)

  Prevent the InnoDB main thread from hogging CPU if a table lingers in the background drop queue (though it is essentially a bug if a table end up there at all)

into narttu.mysql.fi:/my/mysql-3.23

into mashka.mysql.fi:/home/my/mysql-3.23

(this bug was already fixed in 4.0, I just copied and pasted two lines).

into eagle.mysql.r18.ru:/home/vva/work/LOADDATA/mysql-3.23

into narttu.mysql.fi:/my/mysql-3.23

  Backport from 4.0: We had forgotten to call pthread_mutex_destroy when we free an OS mutex in Unix

Security patch to remove wrong error when one had a global update/delete privilige and a database specific SELECT privilege. 

into narttu.mysql.fi:/my/mysql-3.23

All tests plus grant.pl test passed.

into sinisa.nasamreza.org:/mnt/work/mysql

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

Backported fix from 4.1 for bug 212: SELECT query containing a NATURAL JOIN and parentheses in the WHERE clause

into mashka.mysql.fi:/home/my/mysql-3.23

Fixed problem with not freed thr_alarm() on slave connect

logged, but read as LOAD DATA INFILE REPLACE"
This was just bad && instead of &, but nasty consequences.
This should be merged to 4.0 BUT it will not be automatic (some code
has moved from log_event.h to log_event.cc, and log_event.cc has changed);
please Merging Man, do 'bk grep REPLACE_FLAG' in 4.0/sql
to find all the new places.

least one BLOB column.

into narttu.mysql.fi:/my/mysql-3.23

into mysql.com:/home/mysql_src/mysql-3.23