[
https://issues.apache.org/jira/browse/DERBY-2107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469806
]
Daniel John Debrunner commented on DERBY-2107:
----------------------------------------------
I agree that any timeout on the latch wait should be a separate patch & I
believe a separate Jira issue.
For one thing it will change the api to use patches, e.g. this logic would no
longer work:
Page page = getPage(...);
try {
// do something with page
} finally {
page.unlatch();
}
as obviously with a timeout there would be a path through the finally block
where the page is not latched.
I'm not sure I see the value of a timeout though, though that discussion should
be in any new issue.
> Move page latching out of the lock manager
> ------------------------------------------
>
> Key: DERBY-2107
> URL: https://issues.apache.org/jira/browse/DERBY-2107
> Project: Derby
> Issue Type: Improvement
> Components: Performance, Services, Store
> Affects Versions: 10.3.0.0
> Reporter: Knut Anders Hatlen
> Assigned To: Knut Anders Hatlen
> Priority: Minor
> Attachments: derby-2107-1a.diff, derby-2107-1a.stat,
> derby-2107-1b.diff, derby-2107-1c.diff, derby-2107-1c.stat, derby-2107-1d.diff
>
>
> Latching of pages could be done more efficiently locally in store than in the
> lock manager. See the discussion here:
> http://thread.gmane.org/gmane.comp.apache.db.derby.devel/33135
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
