Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 49817 invoked from network); 19 Oct 2010 13:35:50 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 19 Oct 2010 13:35:50 -0000 Received: (qmail 75087 invoked by uid 500); 19 Oct 2010 13:35:50 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 75014 invoked by uid 500); 19 Oct 2010 13:35:48 -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 75007 invoked by uid 99); 19 Oct 2010 13:35:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Oct 2010 13:35:48 +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.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Oct 2010 13:35:47 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o9JDZRUq000357 for ; Tue, 19 Oct 2010 13:35:27 GMT Message-ID: <8230208.46001287495327471.JavaMail.jira@thor> Date: Tue, 19 Oct 2010 09:35:27 -0400 (EDT) From: "Kristian Waagan (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-4849) Re-compilation may cause duplicate entries in the XPLAIN table In-Reply-To: <2187405.138091287042456312.JavaMail.jira@thor> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922554#action_12922554 ] Kristian Waagan commented on DERBY-4849: ---------------------------------------- Lily, I can't see any performance issues with this patch. Some of the code is only executed if there is an exception, and the extra if's are "hidden behind" an existing if-condition (which is mostly false). Let me know if you were thinking of something in particular. As for the testing, it may seem as updating the statistics in a loop is good enough to trigger the invalidation just at the right spot. Of course, I can't do it only once due to the timing requirements, so I made the test run both the select and the invalidation code, in separate threads, in a loop for 10 seconds. Thanks, > Re-compilation may cause duplicate entries in the XPLAIN table > -------------------------------------------------------------- > > Key: DERBY-4849 > URL: https://issues.apache.org/jira/browse/DERBY-4849 > Project: Derby > Issue Type: Bug > Components: SQL > Affects Versions: 10.6.2.1, 10.7.0.0 > Reporter: Kristian Waagan > Assignee: Kristian Waagan > Priority: Minor > Attachments: derby-4849-1a-narrow_fix.diff, derby-4849-2a-broad_fix.diff, derby-4849-2b-broad_fix_with_test.diff, derby-4849-2b-broad_fix_with_test.stat, derby-4849-xplain_duplicate_stacktrace.txt > > > If happening at the right moment, a re-compilation request may cause duplicate entries in the XPLAIN statement tables. > I have only confirmed this for the SYSXPLAIN_STATEMENTS table, and I do not know if the other XPLAIN tables are affected. > The error is highly intermittent, and so far I have only been able to trigger it when testing the automatic index statistics update prototype. > See the attached stack-trace for some more details. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.