[MDEV-16103] Instance crash on second insert with trigger Created: 2018-05-07  Updated: 2018-05-24  Resolved: 2018-05-24

Status: Closed
Project: MariaDB Server
Component/s: Data Manipulation - Insert
Affects Version/s: 10.3.4
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Tadas Balaišis Assignee: Alice Sherepa
Resolution: Duplicate Votes: 0
Labels: None

Attachments: File 2-14.err     File enum_data_trg.sql     File enum_trg.sql     File insert_script.sql    
Issue Links:
Duplicate
duplicates MDEV-13170 Database service (MySQL) stops after ... Closed

 Description   

I got service unloaded after trying to execute insert script. Err file attached. Version: 10.2.14 on winx64.
The insert script attached. It breaks on second statement. I assume it caused by insert trigger action, trigger code attached.
The error is reproducible after service startup.
I noticed that I get no error if I go step-by-step, executing every statement manualy (F10 on HeidiSQL). And then I can get error on third statement. This makes my think that there is some pause duration (several seconds) required for service to recover and accept subsequent statement. And it crashes, if this pause is too short.

 Comments   
Comment by Tadas Balaišis [ 2018-05-07 ]

Maybe I was wrong about specific duration. Maybe committing after each statement helps.

Comment by Tadas Balaišis [ 2018-05-07 ]

No, commit is not a good workaround. I got crash after commit either. I didn't get the rule. Yes, it is possible to insert in several attempts, but nevertheless I would like this bug fixed.

Comment by Tadas Balaišis [ 2018-05-24 ]

Affected Version 10.3.4 10.3.6

Comment by Alice Sherepa [ 2018-05-24 ]

It looks like it is the same problem as MDEV-13170. If the crash will still appear after fix of MDEV-13170, feel free to comment here and the case will be reopen

Generated at Thu Feb 08 08:26:24 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.