[
https://issues.apache.org/jira/browse/DERBY-5067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-5067:
--------------------------------------
Attachment: pk.diff
Attaching a patch that moves the definition of primary key constraints from the
table definitions to separate ALTER TABLE statements after the tables have been
populated. It looks like CREATE INDEX statements already are placed after
populating the tables.
> Performance regression tests should populate tables before creating indexes
> ---------------------------------------------------------------------------
>
> Key: DERBY-5067
> URL: https://issues.apache.org/jira/browse/DERBY-5067
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.8.0.0
> Reporter: Knut Anders Hatlen
> Assignee: Knut Anders Hatlen
> Attachments: pk.diff
>
>
> I've noticed that the results from some of the performance regression tests
> have become more unstable the last two weeks. See for example here:
> http://home.online.no/~olmsan/derby/perf/select_30d.html
> I suspect it's because the automatic index statistics thread is running (the
> instability started at about the same time as it was enabled). We should make
> the test clients create indexes after the tables have been populated so that
> the statistics will be up to date and no work in the background is needed.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
