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: pass (athena.apache.org: local policy)
Message-ID: <4A3A2E01.1070802@sun.com>
Date: Thu, 18 Jun 2009 13:07:29 +0100
From: Alan Burlison <Alan.Burlison@sun.com>
User-Agent: Thunderbird 2.0.0.21 (X11/20090505)
MIME-Version: 1.0
To: Derby Discussion <derby-user@db.apache.org>
Subject: Re: SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE versus
 SYSCS_UTIL.SYSCS_UPDATE_STATISTICS
References: <4A3A0F36.5080004@sun.com> <wjo8ljnpeq6z.fsf@sun.com>
In-Reply-To: <wjo8ljnpeq6z.fsf@sun.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Knut Anders Hatlen wrote:

> As far as I can see, SYSCS_INPLACE_COMPRESS_TABLE does not update the
> index statistics. I couldn't find anything in the in-place compress code
> that attempted to update the statistics, and it didn't appear to have
> updated them when I monitored the CREATIONTIMESTAMP column in
> SYS.SYSSTATISTICS.
> 
> I think much of the documentation about index statistics was written
> before in-place compress was implemented, which is probably why the docs
> are unclear. Could you please file a JIRA issue and point to the
> sections that you found unclear? Thanks.

Hmm just noticed this in the docs for the related 
SYSCS_UTIL.SYSCS_COMPRESS_TABLE procedure:

"The SYSCS_UTIL.SYSCS_COMPRESS_TABLE system procedure updates statistics 
on all indexes as part of the index rebuilding process."

But no mention of that (either way) for 
SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE

-- 
Alan Burlison
--