1
This file should contain all know fatal bugs in the Maria storage
2
engine for the last source or binary release. Minor bugs, extensions
3
and feature request and bugs found since this release can be find in the
4
MySQL bugs databases at: http://bugs.mysql.com/ (category "Maria
7
There shouldn't normally be any bugs that affects normal operations in
8
any Maria release. Still, there are always exceptions and edge cases
9
and that's what this file is for.
11
For the first few Alpha releases of Maria there may be some edge cases
12
that crashes during recovery; We don't like that but we think it's
13
better to get the Maria alpha out early to get things tested and get
14
more developers on the code early than wait until these are fixed. We
15
do however think that the bugs are not seriously enough to stop anyone
16
from starting to test and even use Maria for real (as long as they are
17
prepared to upgrade to next MySQL-Maria release ASAP).
19
If you have found a bug that is not listed here, please add it to
20
http://bugs.mysql.com/ so that we can either fix it for next release
21
or in the worst case add it here for others to know!
24
Known bugs that we are working on and will be fixed shortly
25
===========================================================
27
- We have some instabilities in log writing that is under investigatation
28
This causes mainly assert to triggers in the code and sometimes
29
the log handler doesn't start up after restart.
30
Most of this should now be fixed...
32
- INSERT on a duplicate key against a key inserted by another connection
33
that has not yet ended will give a duplicate key error instead of
34
waiting for the other statement to end.
37
Known bugs that are planned to be fixed before Gamma/RC
38
=======================================================
40
- If we get a write failure on disk (disk full or disk error) for the
41
log, we should stop all usage of transactional tables and mark all
42
transactional tables that are changed as crashed.
43
For the moment, if this happens, you have to take down mysqld,
44
remove all logs, restart mysqld and repair your tables.
46
If you get the related error:
47
"Disk is full writing '/usr/local/mysql/var/maria_log.????????' (Errcode: 28)
48
Waiting for someone to free space..."
49
you should either free disk space, in which Maria will continue as before
50
or kill mysqld, remove logs and repair tables.
53
Known bugs that are planned to be fixed later
54
=============================================
56
LOCK TABLES .. WRITE CONCURRENT is mainly done for testing MVCC. Don't
57
use this in production. Things that is not working if you are using
60
- INSERT/REPLACE ... SELECT on an empty table may cause crashes or
61
wrong results if someone else is doing writes on the table during repair
62
or someone is doing selects during the repair index phase.
64
INSERT ... SELECT, REPLACE ... SELECT and LOAD DATA are blocking
65
inserts and SELECT for the table. They should only have to do this if
66
the destination is empty (as then we are using fast index rebuild).
68
Missing features that is planned to fix before Beta
69
===================================================
73
Features planned for future releases
74
====================================
76
Most notable is full transaction support and multiple reader/writers
79
http://forge.mysql.com/worklog/
80
(you can enter "maria" in the "quick search" field there).