diff options
author | unknown <guilhem@gbichot4.local> | 2008-01-25 21:14:48 +0100 |
---|---|---|
committer | unknown <guilhem@gbichot4.local> | 2008-01-25 21:14:48 +0100 |
commit | e4e8418ced94fff9c8b4bd7b8fcf5e2123717f2b (patch) | |
tree | 9ec249e4e1becd2bd8c94548a2d386b6136e5eb8 /KNOWN_BUGS.txt | |
parent | b40a6348c966bb734d034cb60a24bd7b91d5d38c (diff) | |
download | mariadb-git-e4e8418ced94fff9c8b4bd7b8fcf5e2123717f2b.tar.gz |
Two bugs already fixed
Diffstat (limited to 'KNOWN_BUGS.txt')
-rw-r--r-- | KNOWN_BUGS.txt | 9 |
1 files changed, 0 insertions, 9 deletions
diff --git a/KNOWN_BUGS.txt b/KNOWN_BUGS.txt index a9dd851ea78..8779262cbd4 100644 --- a/KNOWN_BUGS.txt +++ b/KNOWN_BUGS.txt @@ -23,15 +23,6 @@ or in the worst case add it here for others to know! Known bugs that are planned to be fixed before next minor release ================================================================= -- If mysqld crashed or is killed during REPAIR or OPTIMIZE, Maria will not - be able to automaticly repair the table again; You must manually run - REPAIR on the table again after mysqld is started. - -- If mysqld crashes during batch insert into an empty table, - (This includes LOAD DATA INFILE, SELECT ... INSERT and INSERT (many rows)) - Maria repair may not be able to recreate the empty table. In this case - You must manually run either REPAIR TABLE or TRUNCATE to fix the table. - - If the log files are damaged or inconsistent, Maria may fail to start. We should fix that if this happens and mysqld is restarted (thanks to mysqld_safe, instance manager or other script) it should disregard the |