Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <442D4BA3.2040404@amberpoint.com>
Date: Fri, 31 Mar 2006 07:32:51 -0800
From: Bryan Pendleton <bpendleton@amberpoint.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: derby-dev@db.apache.org
Subject: Re: Does in-place compress really defragment?
References: <0IWZ00J4WWUAYO@epost-mail1.sweden.sun.com>
In-Reply-To: <0IWZ00J4WWUAYO@epost-mail1.sweden.sun.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

�ystein Gr�vlen wrote:
> I tried an experiment with on-line compress and it seems like no space
> is freed unless I delete records at the end of the heap:

It does seem like the documentation allows for this:

           SYSCS_COMPRESS_TABLE is guaranteed to recover the maximum amount
           of free space, at the cost of temporarily creating new tables
           and indexes before the statement in committed. SYSCS_INPLACE_COMPRESS
           attempts to reclaim space within the same table, but cannot guarantee
           it will recover all available space.

Did you try your same experiment with full compress?

thanks,

bryan