Jim Cross created DERBY-6939:
Summary: Update statement poor performance with index using where
in (select
Key: DERBY-6939
URL: https://issues.apache.org/jira/browse/DERBY-6939
Project: Derby
[
https://issues.apache.org/jira/browse/DERBY-6937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harshvardhan Gupta updated DERBY-6937:
--
Attachment: derby_script.sql
imdb.diff
Please find the attached files.
[
https://issues.apache.org/jira/browse/DERBY-6937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16038085#comment-16038085
]
Bryan Pendleton commented on DERBY-6937:
Yay! Your patch worked great for me, as did your updated
Hi Brett,
I just happened to see your post on my phone and what came to mind was I wonder
how the automatic statistics update is implemented and if that might somehow be
at play here. I may be totally off base but remember at one point this was
implemented and there was discussion of how and
Background:
* A large database approximately 750G
* derby.storage.pageCacheSize=64000
* Inserts going into the database about 125/second
* Other database updates and deletes are being performed at a lower
rate.
A query is run by the customer that does not
[
https://issues.apache.org/jira/browse/DERBY-6939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16037980#comment-16037980
]
Rick Hillegas commented on DERBY-6939:
--
Hi Jim,
Have you analyzed the query plan using
