Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <894019874.58311265340628247.JavaMail.jira@brutus.apache.org>
Date: Fri, 5 Feb 2010 03:30:28 +0000 (UTC)
From: "Mamta A. Satoor (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-4537) Update on tables with blob columns
 streams blobs into memory even when the blobs are not updated/accessed.
In-Reply-To: <700039087.58081265340148283.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-4537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mamta A. Satoor updated DERBY-4537:
-----------------------------------

    Issue & fix info: [Repro attached]

> 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
>         Attachments: derby4537Repro.java
>
>
> 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.