Bug #100029 ERROR 1032 (HY000) at line 49: Can't find record in 'test'
Submitted: 29 Jun 2020 8:30 Modified: 1 Aug 2020 14:05
Reporter: wuzhenxing wu Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:mysql Ver 8.0.18 for Win64 on x86_64 (M OS:Windows (win 10 64bit)
Assigned to: MySQL Verification Team CPU Architecture:Any (intel i7 9750h)
Tags: MySQL, mysqlbinlog

[29 Jun 2020 8:30] wuzhenxing wu 
Description:
I created the test table and inserted a lot of data.

Then I executed the delete statement

want to use mysqlbinlog for data recovery

-----

ERROR 1032 (HY000) at line 49: Can't find record in 'test'

How to repeat:
CREATE TABLE `test` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `name` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci DEFAULT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=15 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;

insert test(name) values('12312312');
insert test(name) values('12312312');
insert test(name) values('12312312');
insert test(name) values('12312312');
insert test(name) values('12312312');
insert test(name) values('12312312');
insert test(name) values('12312312');

delete a from test a where id =1;
delete a from test a where id =2;
delete a from test a where id =3;

mysqlbinlog --start-position=492469 --stop-position=492845 DESKTOP-bin.000057 |mysql -uroot -p
[29 Jun 2020 8:34] MySQL Verification Team 
Please try version 8.0.20.
[30 Jun 2020 2:12] wuzhenxing wu 
I have updated to version 8.0.20, 
But problems remain.

---error
ERROR 1032 (HY000) at line 49: Can't find record in 'test'
[1 Jul 2020 14:05] MySQL Verification Team 
Hi,

I don't see how is this a bug?

> mysqlbinlog --start-position=492469 --stop-position=492845 DESKTOP-bin.000057 |mysql -uroot -p

What are you trying to do here? You are obviously executing those DELETE's and they fail as the item is already deleted. 

Kind regards
Bogdan
[2 Aug 2020 1:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".