MySQL Bugs: #109015: BETWEEN takes more locks then needed

Bug #109015	BETWEEN takes more locks then needed
Submitted:	7 Nov 2022 10:55	Modified:	8 Nov 2022 13:49
Reporter:	Maksim Novikov	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Server: Locking	Severity:	S3 (Non-critical)
Version:		OS:	Linux
Assigned to:		CPU Architecture:	Any
Tags:	locking mysql

File:	Maximum allowed size is 50MB.
Description:
Privacy:

If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.

To split a large file:

On *nix platforms use the split command e.g. split -b 50MB <my_large_archive> <my_split_archive_prefix>
On windows use WinZip or a similar utility to split the large file

Here is screenshot from performance_schema

Attachment: photo_2022-11-05_12-14-50.jpg (image/jpeg, text), 40.75 KiB.

I cut lots of unnecessary data from it, but you can clearly see that there is no deadlock here. It's just normal lock

Attachment: show_engine_innodb_status.txt (text/plain), 1.92 KiB.

Okay, here is full output of innodb status

Attachment: innodb_status.txt (text/plain), 4.79 KiB.