Bug #38448 | size limit option for mysql_store_result() | ||
---|---|---|---|
Submitted: | 30 Jul 2008 8:46 | Modified: | 30 Jul 2008 8:52 |
Reporter: | Hartmut Holzgraefe | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: C API (client library) | Severity: | S4 (Feature request) |
Version: | 5.0, 5.1, all | OS: | Any |
Assigned to: | Assigned Account | CPU Architecture: | Any |
[30 Jul 2008 8:46]
Hartmut Holzgraefe
[4 Nov 2008 16:03]
Hartmut Holzgraefe
Another idea besides simply failing when the preconfigured amount of memory is exceeded: store the client side result set in temporary disk file instead of main memory when it exceeds a certain configurable threshold and serve actual application row fetch request from there ... a mechanism similar to tmp_table_size on the server side ...
[2 Oct 2009 12:47]
Bernd Ocklin
reminds me off 1. BUG#36701 - joins on BLOB tables do not have their buffers released fast enough 2. BUG#47572 - releases BLOB memory more often in long-running transactions 3. BUG#47573 - BLOB buffer may not be freed correctly 4. BUG#47574 - BLOB buffer calculation could be wrong in scan operations can you check and possibly simply close?
[12 Oct 2009 14:26]
Frazer Clement
Regarding the recently closed Blob bugs - they affect memory usage in the Server, not the mysql client.