[
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-2a-broad_fix.diff
derby-4849-1a-narrow_fix.diff
Attaching patches 1a and 2a.
The former sets the flag explicitly when needed, whereas the latter moves this
logic into the cleanupOnError-method and automates setting the flag.
This is the first time we need this mechanism, so I don't know for sure which
one is best, but I'm leaning towards patch 2a due to its more general nature.
Any opinions on that?
I'll try writing a test too.
Manual testing (running XplainStatisticsTest with the auto index stats
prototype) indicates that both patches address the reported problem. Running
full regression tests now.
> 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
> Priority: Minor
> Attachments: derby-4849-1a-narrow_fix.diff,
> derby-4849-2a-broad_fix.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.
