Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 24122 invoked from network); 27 Jun 2008 15:53:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 27 Jun 2008 15:53:36 -0000 Received: (qmail 70812 invoked by uid 500); 27 Jun 2008 15:53:37 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 70596 invoked by uid 500); 27 Jun 2008 15:53:37 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 70585 invoked by uid 99); 27 Jun 2008 15:53:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Jun 2008 08:53:37 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Jun 2008 15:52:55 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 11B4D234C14E for ; Fri, 27 Jun 2008 08:52:45 -0700 (PDT) Message-ID: <1632233966.1214581965071.JavaMail.jira@brutus> Date: Fri, 27 Jun 2008 08:52:45 -0700 (PDT) From: "Mike Matrigali (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Updated: (DERBY-269) Provide some way to update index cardinality statistics (e.g. reimplement update statistics) In-Reply-To: <744936781.1115833984587.JavaMail.jira@ajax.apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali updated DERBY-269: --------------------------------- I like the proposal for a single procedure with 3 args as described, which can handle both the case of updating stats for all indexes and stats for a single named index. my vote for name would be SYSCS_UPDATE_STATISTICS(). > Provide some way to update index cardinality statistics (e.g. reimplement update statistics) > -------------------------------------------------------------------------------------------- > > Key: DERBY-269 > URL: https://issues.apache.org/jira/browse/DERBY-269 > Project: Derby > Issue Type: New Feature > Components: SQL > Affects Versions: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.2.2.0, 10.3.1.4 > Reporter: Stan Bradbury > Assignee: Mamta A. Satoor > > Performance problems are being reported that can be resolved by updating the cardinality statistics used by the optimizer. Currently the only time the statistics are guaranteed to be an up-to-date is when the index is first created on a fully populated table. This is most easily accomplished on an existing table by using the command: > alter table compress [sequential] > Compress table is an I/O intensive task. A better way to achieve this would be to re-enable parser support for the 'update statistics' command or re-implement the update in some other fashion. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.