- 25 Apr, 2003 7 commits
-
-
hf@deer.mysql.r18.ru authored
-
lenz@mysql.com authored
into mysql.com:/space/my/mysql-4.0
-
lenz@mysql.com authored
into mysql.com:/space/my/mysql-4.0-build
-
lenz@mysql.com authored
ANALYZE TABLE)
-
serg@sergbook.mysql.com authored
into sergbook.mysql.com:/usr/home/serg/Abk/mysql-4.0
-
bar@bar.mysql.r18.ru authored
Don't allow access outside the string
-
lenz@mysql.com authored
instead of being an individual file to avoid redundancy
-
- 24 Apr, 2003 6 commits
-
-
greg@mysql.com authored
-
heikki@hundin.mysql.fi authored
When FLUSH LOGS is called, flush InnoDB logs to disk also in the case innodb_flush_log_at_trx_commit=0
-
heikki@hundin.mysql.fi authored
Make sure we do not do insert buffer merge in fast shutdown even if there is some buglet which increments srv_activity_counter during a shutdown
-
heikki@hundin.mysql.fi authored
Make buffer pool flush batches bigger as that may save some time if fsync is very inefficient
-
heikki@hundin.mysql.fi authored
Make ANALYZE TABLE to update index cardinality and other statistics also for an InnoDB table; note that the estimates are based on 10 random dives, not on an exhaustive read of the table
-
monty@narttu.mysql.fi authored
-
- 23 Apr, 2003 15 commits
-
-
monty@narttu.mysql.fi authored
(There was a problem on some AMD system when the floating point precision wasn't accurate enough)
-
serg@sergbook.mysql.com authored
into sergbook.mysql.com:/usr/home/serg/Abk/mysql-4.0
-
monty@narttu.mysql.fi authored
-
peterg@mysql.com authored
into mysql.com:/home/pgulutzan/mysql-4.0
-
peterg@mysql.com authored
from Monty.
-
monty@narttu.mysql.fi authored
Added optimzation for clustered index Fixed bug in UPDATE ... ORDER BY Fixed handling of UPDATE ... LIMIT
-
serg@sergbook.mysql.com authored
-
mmatthew@markslaptop. authored
Enable 'LOAD LOCAL INFILE', for parity with unix binaries.
-
peterg@mysql.com authored
more detailed explanation of record header and column storage.
-
gluh@gluh.mysql.r18.ru authored
unknown event'
-
serg@sergbook.mysql.com authored
into sergbook.mysql.com:/usr/home/serg/Abk/mysql-4.0
-
serg@sergbook.mysql.com authored
-
serg@sergbook.mysql.com authored
-
lenz@mysql.com authored
Christian Hammers for providing this patch
-
serg@sergbook.mysql.com authored
-
- 22 Apr, 2003 9 commits
-
-
lenz@mysql.com authored
-
lenz@mysql.com authored
into mysql.com:/space/my/mysql-4.0
-
lenz@mysql.com authored
discovering this)
-
heikki@hundin.mysql.fi authored
Give sensible advice to the user if InnoDB notices index corruption
-
lenz@mysql.com authored
-
vva@eagle.mysql.r18.ru authored
into eagle.mysql.r18.ru:/home/vva/work/LOADDATA_BUG/mysql-4.0
-
vva@eagle.mysql.r18.ru authored
into eagle.mysql.r18.ru:/home/vva/work/LOADDATA_BUG/mysql-4.0
-
vva@eagle.mysql.r18.ru authored
-
serg@sergbook.mysql.com authored
-
- 21 Apr, 2003 1 commit
-
-
heikki@hundin.mysql.fi authored
No buffer pool activity in SHOW INNODB STATUS actually meant no page gets
-
- 20 Apr, 2003 1 commit
-
-
heikki@hundin.mysql.fi authored
If HAVE_purify is defined, define UNIV_SET_MEM_TO_ZERO to eliminate Purify warnings
-
- 19 Apr, 2003 1 commit
-
-
heikki@hundin.mysql.fi authored
Do not set buffer pool to zero when we start up: that takes too much time for big buffer pools; Purify users must define UNIV_SET_MEM_TO_ZERO in univ.i to eliminate spurious (?) Purify warnings
-