Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 58615 invoked from network); 23 Mar 2009 23:16:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 23 Mar 2009 23:16:13 -0000 Received: (qmail 44612 invoked by uid 500); 23 Mar 2009 23:16:13 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 44579 invoked by uid 500); 23 Mar 2009 23:16:13 -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 44571 invoked by uid 99); 23 Mar 2009 23:16:13 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Mar 2009 23:16:13 +0000 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; Mon, 23 Mar 2009 23:16:11 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 6D8A2234C003 for ; Mon, 23 Mar 2009 16:15:50 -0700 (PDT) Message-ID: <1232515126.1237850150434.JavaMail.jira@brutus> Date: Mon, 23 Mar 2009 16:15:50 -0700 (PDT) From: "Kathey Marsden (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Created: (DERBY-4112) Make it possible to execute a statement with all considered plans MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org Make it possible to execute a statement with all considered plans ----------------------------------------------------------------- Key: DERBY-4112 URL: https://issues.apache.org/jira/browse/DERBY-4112 Project: Derby Issue Type: Improvement Components: SQL, Test Affects Versions: 10.6.0.0 Reporter: Kathey Marsden Priority: Minor Often we have bugs that occur only if a specific query plan is selected. These are often hard to reproduce or require a great deal of setup to reproduce the exact conditions of the failed execution (for example DERBY-3926). It would be very helpful for debugging user reports and also for expanding our testing, if there was a way to execute a query repeatedly with the different plans considered and identify the failing one. It would be slow, but Mike suggested maybe we could use optimizer directives to do this. If the query plans were numbered from 1 to the number considered and then you had a directive --DERBY-PROPERTIES QUERYPLAN= where N is the sequential number of the plan considered, the statement would just execute as soon as it had considered that many plans. It could throw an exception if N exceeded the number of considered plans. The calling test code could then just iterate until it identified the failing plan and look for the exception to know it was finished. If there was a problem with a plan the developers could reliably re-execute with the failing plan to debug. I think this could be a newcomer task with some guidance and would be a good low risk opportunity to learn about the optimizer. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.