Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <3310366.191541288695865222.JavaMail.jira@thor>
Date: Tue, 2 Nov 2010 07:04:25 -0400 (EDT)
From: "Knut Anders Hatlen (JIRA)" <jira@apache.org>
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


    [ https://issues.apache.org/jira/browse/DERBY-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927359#action_12927359 ] 

Knut Anders Hatlen commented on DERBY-4849:
-------------------------------------------

Thanks, now I see what you mean. Note that the approach with nested transactions with NO_WAIT and retry in the parent transaction is first and foremost used to resolve self-deadlocks (lock conflicts between a nested tx and its parent tx). In this test, the deadlock involves multiple transactions, and even if a retry may resolve a deadlock, it is still possible that the retry in the parent transaction runs into a similar deadlock.

> 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.1.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-2c-broad_fix_with_test.diff, 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.