Bug #93141 | Duplicate Records despite index | ||
---|---|---|---|
Submitted: | 9 Nov 2018 13:17 | Modified: | 20 Nov 2018 14:42 |
Reporter: | Daniel Jänecke | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server: DML | Severity: | S3 (Non-critical) |
Version: | 5.7.22-22-log | OS: | Linux |
Assigned to: | CPU Architecture: | Any |
[9 Nov 2018 13:17]
Daniel Jänecke
[12 Nov 2018 11:55]
MySQL Verification Team
Thank you for the bug report. To process this bug report we need a repeatable test case, please comment here when you will able to provide it. Thanks in advance.
[13 Nov 2018 14:14]
Daniel Jänecke
I cannot reproduce this, I have no idea how this could happen. All I can say is that this data exists, though the unique index clearly says that it must not exist. All I can offer is either a dump or the innodb files of the affected table. By the way, I started to search through all our (non-production) databases and found other cases in four tables. Versions are 5.1, 5.5 and 5.7
[20 Nov 2018 7:21]
Daniel Jänecke
Just to get that right - unless I find out how it was possible to have duplicate data in that tables you will not process this issue?
[20 Nov 2018 9:36]
MySQL Verification Team
Thank you for the feedback. I tried test cases from old but similar/related bug's(Bug #69979, Bug #76927, Bug #73170 etc) to reproduce this issue on latest GA but not seeing any issues now and most likely this is the reason our Miguel asked you to provide a reproducible test case in order to proceed further on this. Your observed issue is unusual and it is hard to know how it allowed invalid data at first place but if we have a reproducible case or exact steps which triggered this issue then it would be much helpful. regards, Umesh