mirror of
https://github.com/MariaDB/server.git
synced 2025-01-15 19:42:28 +01:00
81d3d3ac42
the table is empty. - lifting another limit: versioning was disabled if table had more than one unique index - correcting test of statement-based binlogging, when converting read locks to TL_READ_NO_INSERT KNOWN_BUGS.txt: removing mostly fixed limitation (see ha_maria.cc) mysql-test/r/maria-mvcc.result: result update mysql-test/t/maria-mvcc.test: now when table is empty it does not do versioning, so test hung; inserting one row at start of the test, to enable versioning. sql/sql_parse.cc: Maria team wrongly removed this "break", thanks Davi for noticing storage/maria/ha_maria.cc: - We used to prevent versioning in INSERT/REPLACE SELECT and LOAD DATA, because the index rebuild done by bulk insert sometimes, is unsafe when versioning is on. Here we change that: in store_lock(), if the table is empty (which is required for index rebuild to be used), we disable versioning; in start_bulk_insert(), we don't do index rebuild if versioning is enabled. - Test for statement-based binlogging was incomplete: statement-based binlogging is on for this statement if binlog is open and statement has binlogging enabled and statement is not doing row-based binlogging storage/maria/ma_open.c: Monty and I agreed that it's ok to have versioning on a table with more than one unique index: if an INSERT hits a duplicate key when inserting the second index' key, no other thread should be able to touch the first index' just-inserted key, because that key has an uncommitted transaction id, so the first thread should have time to remove the first index' key.
71 lines
2.9 KiB
Text
71 lines
2.9 KiB
Text
This file should contain all know fatal bugs in the Maria storage
|
|
engine for the last source or binary release. Minor bugs, extensions
|
|
and feature request and bugs found since this release can be find in the
|
|
MySQL bugs databases at: http://bugs.mysql.com/ (category "Maria
|
|
storage engine").
|
|
|
|
There shouldn't normally be any bugs that affects normal operations in
|
|
any Maria release. Still, there are always exceptions and edge cases
|
|
and that's what this file is for.
|
|
|
|
For the first few Alpha releases of Maria there may be some edge cases
|
|
that crashes during recovery; We don't like that but we think it's
|
|
better to get the Maria alpha out early to get things tested and get
|
|
more developers on the code early than wait until these are fixed. We
|
|
do however think that the bugs are not seriously enough to stop anyone
|
|
from starting to test and even use Maria for real (as long as they are
|
|
prepared to upgrade to next MySQL-Maria release ASAP).
|
|
|
|
If you have found a bug that is not listed here, please add it to
|
|
http://bugs.mysql.com/ so that we can either fix it for next release
|
|
or in the worst case add it here for others to know!
|
|
|
|
|
|
Known bugs that we are working on and will be fixed shortly
|
|
===========================================================
|
|
|
|
- We have some instabilities in log writing that is under investigatation
|
|
This causes mainly assert to triggers in the code and sometimes
|
|
the log handler doesn't start up after restart.
|
|
Most of this should now be fixed...
|
|
|
|
- INSERT on a duplicate key against a key inserted by another connection
|
|
that has not yet ended will give a duplicate key error instead of
|
|
waiting for the other statement to end.
|
|
|
|
|
|
Known bugs that are planned to be fixed before Gamma/RC
|
|
=======================================================
|
|
|
|
- If we get a write failure on disk (disk full or disk error) for the
|
|
log, we should stop all usage of transactional tables and mark all
|
|
transactional tables that are changed as crashed.
|
|
For the moment, if this happens, you have to take down mysqld,
|
|
remove all logs, restart mysqld and repair your tables.
|
|
|
|
If you get the related error:
|
|
"Disk is full writing '/usr/local/mysql/var/maria_log.????????' (Errcode: 28)
|
|
Waiting for someone to free space..."
|
|
you should either free disk space, in which Maria will continue as before
|
|
or kill mysqld, remove logs and repair tables.
|
|
|
|
|
|
Known bugs that are planned to be fixed later
|
|
=============================================
|
|
|
|
LOCK TABLES .. WRITE CONCURRENT is mainly done for testing MVCC. Don't
|
|
use this in production.
|
|
|
|
Missing features that is planned to fix before Beta
|
|
===================================================
|
|
|
|
None
|
|
|
|
Features planned for future releases
|
|
====================================
|
|
|
|
Most notable is full transaction support and multiple reader/writers
|
|
in Maria 2.0
|
|
|
|
http://forge.mysql.com/worklog/
|
|
(you can enter "maria" in the "quick search" field there).
|