Bug #75879 memory consumed quickly while executing loop in procedure
Submitted: 12 Feb 2015 17:04 Modified: 27 Apr 2015 14:25
Reporter: zhai weixiang (OCA) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Utilities: Binlog Events Severity:S2 (Serious)
Version:5.6,5.7 OS:Any
Assigned to: CPU Architecture:Any

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:

[12 Feb 2015 19:11] Shane Bester
can clearly see the set_trans_pos call gobbling up memory!

Attachment: bug75879_5.7.6_memory_profile.pdf (application/pdf, text), 14.45 KiB.