Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2.2, 10.3.0
-
None
-
CentOS Linux release 7.4.1708 (Core)
3.10.0-693.21.1.el7.x86_64 #1 SMP
VMWare client
Description
Whilst truncating a bunch of tables from a Python script, the server fell over on a table that was already empty.
Attachments
Issue Links
- relates to
-
MDEV-9663 InnoDB assertion failure: *cursor->index->name == TEMP_INDEX_PREFIX, or !cursor->index->is_committed()
-
- Closed
-
-
MDEV-13256 innodb.truncate_debug fails in buildbot
-
- Closed
-
Activity
Link |
This issue relates to |
Status | Open [ 1 ] | Confirmed [ 10101 ] |
Assignee | Marko Mäkelä [ marko ] |
Summary | Crash whilst TRUNCATEing a table | Change buffer crash during TRUNCATE or DROP TABLE |
Component/s | Storage Engine - InnoDB [ 10129 ] | |
Component/s | Data Manipulation - Delete [ 11300 ] |
Affects Version/s | 10.3.0 [ 22127 ] | |
Affects Version/s | 10.2.2 [ 22013 ] | |
Affects Version/s | 10.2.14 [ 22911 ] |
issue.field.resolutiondate | 2018-05-09 09:14:10.0 | 2018-05-09 09:14:10.273 |
Fix Version/s | 10.2.15 [ 23006 ] | |
Fix Version/s | 10.3.7 [ 23005 ] | |
Resolution | Fixed [ 1 ] | |
Status | Confirmed [ 10101 ] | Closed [ 6 ] |
Workflow | MariaDB v3 [ 86628 ] | MariaDB v4 [ 154182 ] |
Zendesk Related Tickets | 167943 |