Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: neutral (nike.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=sbcglobal.net;
  h=DKIM-Signature:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding;
  b=HoJCWnYDoNOyb0RcDm4jpiGMpQm4p+GVRQCoMDDflG9kLm20tvEDQbq9OcLz3CN0vL9CZsY5esfX0zdt1LphiFWfxQQbFUJI7eP8MQTKAolPDIdqeP+7QE5YUGeNbWE+J/sWjmVJOweXDEDAB8M5jzTcHzshuHO2Pnjb6RPG2HU=
  ;
Message-ID: <4F42AE92.4030104@sbcglobal.net>
Date: Mon, 20 Feb 2012 12:35:30 -0800
From: Mike Matrigali <mikem_app@sbcglobal.net>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Derby Discussion <derby-user@db.apache.org>
Subject: Re: CALL SYSCS_UTIL.SYSCS_COMPRESS_TABLE
References: 
 <CAK04dvaWb7ojvJKjZVF9-6EQyOdCWLiE4+7Jjzq-L3mqDPZQzQ@mail.gmail.com>
 <4F3A8C58.9010909@sbcglobal.net> <33345945.post@talk.nabble.com>
 <4F3EDE8A.6030204@sbcglobal.net> <33357142.post@talk.nabble.com>
 <4F4286C3.7080707@sbcglobal.net> <33358994.post@talk.nabble.com>
In-Reply-To: <33358994.post@talk.nabble.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Matthew McCawley wrote:
> 
> 
> Mike Matrigali wrote:
>> I have reported DERBY-5624 to track this issue.  I think I understand 
>> the problem, but would feel much better with a reproducible test case
>> I could run.  Feel free to add your information to DERBY-5624.
>>
> 
> In our case, we just have a single table with about 5 million rows of
> essentially junk data. I delete some portion of the data that's older than
> some margin (half, single day's worth, etc.) and run compression.
> 
> I also tried another table that's about twice as big, but it required an 8
> MB stack size. I've run out of heap space a few times as well, but I'm still
> working on reproducing it.
at this point could you move the discussion to (just add comments I 
don't think you have to be authorized to do so):
https://issues.apache.org/jira/browse/DERBY-5624