[MDEV-4970] Wrong result with Aria table populated with disabled keys Created: 2013-08-29 Updated: 2014-01-29 Resolved: 2014-01-26 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | None |
| Affects Version/s: | 10.0.4, 5.5.33 |
| Fix Version/s: | 5.5.35 |
| Type: | Bug | Priority: | Major |
| Reporter: | Elena Stepanova | Assignee: | Michael Widenius |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | Aria | ||
| Description |
|
The following test case produces wrong results:
Actual result:
The result is not persistent, the next execution of the same queries produces the expected one:
The failure started happening on 5.5 since this revision:
Here is a simpler test case, without LEFT JOIN. I didn't check whether it appeared with the same revision, but it looks similar:
Actual result:
(obviously, rows 6,8,9 are missing) |
| Comments |
| Comment by Michael Widenius [ 2014-01-25 ] |
|
Problem was that ALTER TABLE DISABLE KEYS incremented create_trid for the table, which made the new index entries invisible until the global trid catched up. Fixed by only updating create_trid if we are rewriting all rows and indexes. |
| Comment by Michael Widenius [ 2014-01-25 ] |
|
Pushed into maria-5.5-monty to be merged into 5.5.35 |
| Comment by Michael Widenius [ 2014-01-26 ] |
|
Fixed in my tree. Will be in 5.5.35 |
| Comment by Daniel Bartholomew [ 2014-01-29 ] |
|
http://bazaar.launchpad.net/~maria-captains/maria/5.5/revision/4036 |