Query based inserting or updating of blob
PDF (US Ltr) - 31.3Mb PDF (A4) - 31.4Mb PDF (RPM) - 29.9Mb HTML Download (TGZ) - 7.6Mb HTML Download (Zip) - 7.6Mb HTML Download (RPM) - 6.5Mb Man Pages (TGZ) - 177.0Kb Man Pages (Zip) - 287.1Kb Info (Gzip) - 3.0Mb Info (Zip) - 3.0Mb My SQL Backup and Recovery My SQL Globalization My SQL Information Schema My SQL Installation Guide My SQL and Linux/Unix My SQL and OS X My SQL Partitioning My SQL Performance Schema My SQL Replication Using the My SQL Yum Repository My SQL Restrictions and Limitations Security in My SQL My SQL and Solaris Building My SQL from Source Starting and Stopping My SQL My SQL Tutorial My SQL and Windows My SQL NDB Cluster 7.3-7.4 The My SQL server maintains many system variables that indicate how it is configured. System variables can be set at server startup using options on the command line or in an option file.Most of them can be changed dynamically at runtime using the statement, which enables you to modify operation of the server without having to stop and restart it.In some cases, the amount might be less than the value assigned.It is also possible that the server will adjust a value upward.This means that a MEMORY table with *one row* will take up, essentially, "read_buffer_size" bytes.For each on the table, add on another "read_buffer_size" bytes to the table.Variables with no version indicated are present in all My SQL 5.6 releases.For more information about manipulation of system variables, see Section 5.1.6, “Using System Variables”.
This is not documented anywhere as far as I can tell, and I only found it after banging my head against a wall looking through the My SQL source code.
However, the fact that on 32-bit GNU/Linux x86, "sort_buffer_size" must be a few Mi B only to avoid exceeding maximum process space, as explained in one infer that that sort_buffer_size is actually some kind of in-memory buffer.
Additionally, the formula should probably be extended: total = innodb_buffer_pool_size key_buffer_size innodb_additional_mem_pool_size innodb_log_buffer_size max_connections * (sort_buffer_size read_buffer_size binlog_cache_size maximum_thread_stack_size); Noting that "key_buffer_size" is a My ISAM parameter there is abug in My SQL server that treat open_files_limit and open-files-limit differently also the limit for open-files-limit mentioned on this page is not entirely true appears that the "read_buffer_size" setting is used by the MEMORY table engine as the allocation increment size (minus a few bytes).
This means it is impractical to think that the memory usage of the table definition cache is a fixed amount in anyway.
There are purge functions and limits in place but on a busy system with many tables with large blobs you could see a significant amount of bloat.