Bug #121543 READ COMMITTED range DELETE waits on a record outside the exclusive upper bound
Submitted: 19 Oct 6:14 Modified: 19 Oct 9:10
Reporter: Jinpeng Shi Email Updates:
Status: Open Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S3 (Non-critical)
Version:8.4.11, 9.7.2 OS:Any
Assigned to: CPU Architecture:Any
Tags: delete, innodb, lock wait timeout, locking, read committed

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: