WingNews logo WingNews GitHub [2]
top | item 15425379

MySql fixes autoincrement bug after 14 years of users complaining about dataloss

42 points| TekMol | 8 years ago |bugs.mysql.com | reply

17 comments

order
[+] jlgaddis|8 years ago|reply
I'd wager that this only got fixed now because some large Oracle customer got bit hard by this bug.
[+] PhantomGremlin|8 years ago|reply
Best comment from the bug report: So we decides to switch on PostreSQL for production...

And 14 1/2 years after the first bug report the bug is fixed and: Thank you for the bug report.

[+] kanwisher|8 years ago|reply
This is quite scary, I wonder how many systems I’ve been on that have had minor unnoticed data corruptions because of this. This is truely a weird thing to not fix
[+] icedchai|8 years ago|reply
Probably because it's not that scary. In practice, it would generally be a non-issue.

1) mysql server restarts are rare. you'd need a delete followed by a restart to trigger this. 2) you may be using soft deletes, which wouldn't trigger this problem anyway. 3) even if an ID gets reused, it may not actually matter (application dependent.)

[+] bkm|8 years ago|reply
I wonder when it was fixed in Percona's MySQL version, as the reporter of this bug founded Percona in the meantime.
[+] noncoml|8 years ago|reply
The title is a bit clickbaity. The bug doesn’t cause data loss by itself.
[+] jar3624|8 years ago|reply
curious how they did a shutdown of the db. are they saying in all scenarios this causes an the issue ?