into mysql.com:/home/kostja/mysql/mysql-4.0-1724

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

rli->save_temporary_tables and slave_open_temp_tables
(in old 4.0 you could make "SHOW STATUS LIKE 'slave_open_temp_tables'" grow
indefinitely by doing RESET SLAVE and replicating always the same CREATE
TEMPORARY TABLE).
It's critical to reset save_temporary_tables to 0 (otherwise you may later
read memory which has been freed) so this changeset should go into 4.1.

has changed since 4.0.14'
We need to calculate cost of RANGE
scan if it is present instead of cost of 
FULL scan.

into mysql.com:/my/mysql-4.0

Added my_sync() to mysys which will do fsync/fdatasync/_commit() on a file.

- when we don't have in_addr_t, use uint32.
- a forgotten initialization of slave_proxy_id in sql/log_event.cc (was not really "forgot", was
"we needn't init it there", but there was one case where we needed...).
- made slave_proxy_id always meaningful in THD and Log_event, so we can
rely more on it (no need to test if it's meaningful). THD::slave_proxy_id
is equal to THD::thread_id except for the slave SQL thread.
- clean up the slave's temporary table (i.e. free their memory) when slave
server shuts down.

of lock scope

into mysql.com:/home/kostja/mysql/mysql-4.0-root

thd->proc_info added

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

mysql-test-run --manager --valgrind
(without this fix, the manager fails to start mysqld and the tests hang).

into mysql.com:/home/kostja/mysql/mysql-4.0-root

Don't add service name to read config file segments if it's "MySQL"
Fixed possible memory leak when CHANGE USER failed.

"If 2 master threads with same-name temp table, slave makes bad binlog"
and (two birds with one stone) for
BUG#1240 "slave of slave breaks when STOP SLAVE was issud on parent slave
and temp tables".

Here is the design change:
in a slave running with --log-slave-updates, events are now logged with the
thread id they had on the master. So no more id conflicts between master threads,
but introduces id conflicts between one master thread and one normal 
client thread connected to the slave. This is solved by storing the server id
in the temp table's name.

New test which requires mysql-test-run to be run with --manager,
otherwise it will be skipped.

Undoing a Monty's change (hum, a chill runs down my spine ;) which was
"Cleanup temporary tables when slave ends" in ChangeSet 1.1572.1.1.

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

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

mysql --install mysql --defualts-file=path-to-file
(Bug #1643)

  If innodb_force_recovery >= 5, do not try to fetch an old version of a clustered index record: this reduces crashes when dumping tables from a corrupt database

max_user_connections is not set - that is no limit - so that when
max_user_connections is set (with SET) old connections are also
taken into account
mutexes are added where appropriate

into eagle.mysql.r18.ru:/home/vva/work/BUG_1228/mysql-4.0

into eagle.mysql.r18.ru:/home/vva/work/BUG_1348/mysql-4.0

into eagle.mysql.r18.ru:/home/vva/work/BUG_1228/mysql-4.0

(fixed bug #1348)

changing root password on all hosts (bug 1228)

into mysql.com:/home/pem/work/mysql-4.0

in MySQL server...

to cause program to abort. Such table name could have been
one with a semicolon (:) in the middle.

directory owner ship was not honored.