[MDEV-19188] Server Crash When Using a Trigger With A Number of Virtual Columns on INSERT/UPDATE Created: 2019-04-05 Updated: 2019-05-01 Resolved: 2019-05-01 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Triggers, Virtual Columns |
| Affects Version/s: | 10.3.14, 10.3.15, 10.2, 10.3, 10.4 |
| Fix Version/s: | 10.2.24, 10.3.15, 10.4.5 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Robert Humphries | Assignee: | Nikita Malyavin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | triggers, virtual_columns | ||
| Environment: |
Production: Ubuntu 16.04 LTS |
||
| Attachments: |
|
| Description |
|
When you have a table that has 9 (or more) virtual columns, with any type (tested VARCHAR and INT) or expression (initially found the bug where JSON_VALID was used, then tested with referring to another column or just a constant expression) and a BEFORE INSERT or BEFORE UPDATE trigger (with any content or where the trigger is empty); then any INSERT or UPDATE will crash the server; even if the trigger is a BEFORE INSERT trigger and an UPDATE is run, or the other way round, or an INSERT is run with the trigger being a BEFORE INSERT trigger, etc. In the event that the INSERT is done via an INSERT INTO ... SELECT statement, no crash occurs. |
| Comments |
| Comment by Elena Stepanova [ 2019-04-06 ] | |||||||||||||||||||||||||||||||||||||||
|
Thanks for the report and test case. Reproducible as described. Test case - same as in attachments, only wrapped up for MTR.
|