Bug #42287 max_binlog_cache_size has differing initial, DEFAULT, and max values

Submitted: 23 Jan 2009 0:52 Modified: 24 Feb 2009 0:34
Reporter: Patrick Crews Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Options Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: Tatiana Azundris Nuernberg CPU Architecture:Any
Tags: default values, max_binlog_cache_size, variables

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
[23 Jan 2009 0:52] Patrick Crews 
.result file

Attachment: exp.result (, text), 804 bytes.
[23 Jan 2009 0:53] Patrick Crews 
.test file to demonstrate bug

Attachment: exp.test (, text), 656 bytes.

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

Page generated in 0.049 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.