Bug #38479 valgrind warnings in show table status for innodb tables

Submitted: 31 Jul 2008 7:31 Modified: 17 Jul 2009 2:56
Reporter: Shane Bester (Platinum Quality Contributor) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S3 (Non-critical)
Version:5.0.66a, 5.0.74, 5.0.82 OS:Linux
Assigned to: Satya B 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:

  • 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
[20 Oct 2008 17:34] Vasil Dimov
Potential patch to silence the warning.

Attachment: bug38479.diff (application/octet-stream, text), 586 bytes.

[22 May 2009 8:50] Shane Bester
Vasil, here's more details. I will rebuild and try that patch next.

Attachment: bug38479_5.0.82_build_and_valgrind_infos.txt (text/plain), 20.63 KiB.

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.047 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.