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)
Message-ID: <4C337540.1010309@sbcglobal.net>
Date: Tue, 06 Jul 2010 11:26:08 -0700
From: Kathey Marsden <kmarsdenderby@sbcglobal.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5
MIME-Version: 1.0
To: derby-user@db.apache.org
Subject: Re: How to best constrain database space with many records being
 inserted and deleted
References: <97EB699F861AD841B5908C7CA9C956560127D9F5F694@VSERVER1.canoga.com>
In-Reply-To: 
 <97EB699F861AD841B5908C7CA9C956560127D9F5F694@VSERVER1.canoga.com>
Content-Type: multipart/alternative;
 boundary="------------020803020200030004050405"

This is a multi-part message in MIME format.
--------------020803020200030004050405
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 7/6/2010 11:09 AM, Bergquist, Brett wrote:
>
> I  What I am seeing is that the database is growing and it does not 
> seem to be reusing the deleted space.  Should it be?  The records 
> being inserted are exactly the size of the records being deleted.
>
The known issues in this area are:
https://issues.apache.org/jira/browse/DERBY-4057
https://issues.apache.org/jira/browse/DERBY-4055

For DERBY-4055 a possible workaround is here:
https://issues.apache.org/jira/browse/DERBY-4055?focusedCommentId=12680196&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12680196
Also synchronizing table access has helped some users.

You can verify if you are seeing DERBY-4055 by running with a SANE build 
and putting
derby.debug.true=DaemonTrace

in your derby.properties.

All that said, I have heard anecdotal reports that there may be another 
bug.  If you can come up with a reproduction that is not either of these 
issues, we would appreciate it.

Thanks

Kathey

--------------020803020200030004050405
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html; charset=ISO-8859-1"
 http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 7/6/2010 11:09 AM, Bergquist, Brett wrote:
<blockquote
 cite="mid:97EB699F861AD841B5908C7CA9C956560127D9F5F694@VSERVER1.canoga.com"
 type="cite">
  <meta http-equiv="Content-Type"
 content="text/html; charset=ISO-8859-1">
  <meta name="Generator" content="Microsoft Word 12 (filtered medium)">
  <style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
-->
  </style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext="edit">
  <o:idmap v:ext="edit" data="1" />
 </o:shapelayout></xml><![endif]-->
  <div class="WordSection1">
  <p class="MsoNormal">I&nbsp; What I am seeing is
that the database is growing and it does not seem to be reusing the
deleted
space.&nbsp; Should it be?&nbsp; The records being inserted are exactly the
size of the records being deleted.<o:p></o:p></p>
  <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
  </div>
</blockquote>
The known issues in this area are:<br>
<a class="moz-txt-link-freetext" href="https://issues.apache.org/jira/browse/DERBY-4057">https://issues.apache.org/jira/browse/DERBY-4057</a><br>
<a class="moz-txt-link-freetext" href="https://issues.apache.org/jira/browse/DERBY-4055">https://issues.apache.org/jira/browse/DERBY-4055</a><br>
<br>
For DERBY-4055 a possible workaround is here:<br>
<a class="moz-txt-link-freetext" href="https://issues.apache.org/jira/browse/DERBY-4055?focusedCommentId=12680196&amp;page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12680196">https://issues.apache.org/jira/browse/DERBY-4055?focusedCommentId=12680196&amp;page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12680196</a><br>
Also synchronizing table access has helped some users.<br>
<br>
You can verify if you are seeing DERBY-4055 by running with a SANE
build and putting<br>
derby.debug.true=DaemonTrace<br>
<br>
in your derby.properties.<br>
<br>
All that said, I have heard anecdotal reports that there may be another
bug.&nbsp; If you can come up with a reproduction that is not either of
these issues, we would appreciate it.<br>
<br>
Thanks<br>
<br>
Kathey<br>
</body>
</html>

--------------020803020200030004050405--