Update on tables with blob columns streams blobs into memory even when the
blobs are not updated/accessed.
----------------------------------------------------------------------------------------------------------
Key: DERBY-4537
URL: https://issues.apache.org/jira/browse/DERBY-4537
Project: Derby
Issue Type: Improvement
Components: SQL
Affects Versions: 10.6.0.0
Reporter: Mamta A. Satoor
Priority: Minor
While investigating DERBY-1482, I wrote a simple program to see the behavior of
a simple update (without any triggers) of a table with blob columns.
The update is on a non-blob column of a table with blob volumns.
When this update is made with limited heap memory, Derby runs into OOM error.
I tried another table similar to earlier table but with no blob column. An
update on that table does not run into OOM when run with same limited heap
memory.
I would have expected the update to pass for table with blob column since we
are not referencing/updating the blob column. But it appears that we might be
streaming in blob column even though it is untouched by the update sql.
I wonder if working on this jira first will make the work for DERBY-1482 any
easier or better yet, will it make the problem with DERBY-1482 go away? Will
attach a reproducible program for this soon.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
