db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4849) Re-compilation may cause duplicate entries in the XPLAIN table
Date Tue, 19 Oct 2010 12:04:26 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Kristian Waagan updated DERBY-4849:

    Attachment: derby-4849-2b-broad_fix_with_test.stat

Thanks, Knut and Bryan, for the comments.

I'd prefer to handle the more general problem with failed executions under a separate issue.

In patch 2b, I have renamed the field/method, swapped the position of the constant and getMessageId,
and written a test.
The test fails consistently on my machine, but I'm not sure if that is the case on a single-core/-CPU
machine. It would be nice if someone else could run the test without the fix. The easiest
way to disable the fix is to comment out the following line in impl.sql.conn.GenericStatementContext:
+                statementWasInvalidated = true;

It was easiest to make many of the helper methods/structures in XplainStatisticsTest static,
I hope that is okay.

Patch ready for review.

> 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:,
>            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.

View raw message