Hello Marko, Alexander, Thanks for your quick analysis. As I be able to reproduce crash with parallel "delete / insert", does it mean that "delete" act as truncate when there is no clause ? Feel free to ask me if you want me to test patches. Alexander, there is nothing specific to sql_mode=ORACLE. Best regards, Jérôme.
-----Message d'origine----- De : Alexander Barkov [mailto:bar@mariadb.org] Envoyé : lundi 3 avril 2017 06:24 À : Marko Mäkelä Cc : jerome brauge; MariaDB Developers (maria- developers@lists.launchpad.net); Sergey Vojtovich Objet : Re: [Maria-developers] Database corruption
Hello Marko, Jerome,
Marko, thanks for your comments.
On 04/03/2017 08:17 AM, Marko Mäkelä wrote:
I wonder if this could be caused by missing MDL protection around TRUNCATE TABLE, which would then incorrectly allow concurrent INSERT and TRUNCATE. One place where MDL is definitely missing is DROP DATABASE (reported as MDEV-11342 <https://jira.mariadb.org/browse/MDEV-11342>).
This is assigned to Sergey Vojtovich. Sergey is currently on vacation and will be back in the last decade of April.
Marko, do you think it is something hard to fix?
(Sorry, I'm not strong in this area of the code)
That said, the InnoDB in MariaDB 10.2 is based on MySQL 5.7, and one difference between MySQL 5.6 and 5.7 is that InnoDB supports crash-safe atomic TRUNCATE TABLE for .ibd files (WL#6501 <http://dev.mysql.com/worklog/task/?id=6501>).
Best regards,
Marko -- DON’T MISS M|17 April 11 - 12, 2017 The Conrad Hotel New York City https://m17.mariadb.com/
Marko Mäkelä, Lead Developer InnoDB MariaDB Corporation