[
https://issues.apache.org/jira/browse/DERBY-2107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-2107:
--------------------------------------
Attachment: derby-2107-4a.stat
derby-2107-4a.diff
Attaching a patch (4a) to address comment #3 from Suresh. It adds an assert
which fails when a transaction attempts to latch the same page twice. Also
needed to update the test case added by the 3a patch, since it now throws an
assert failure instead of hanging when using a sane build. All the tests ran
cleanly.
> 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, derby-2107-2a.diff, derby-2107-2a.diff,
> derby-2107-2a.stat, derby-2107-2a.stat, derby-2107-3a.diff,
> derby-2107-3a.stat, derby-2107-4a.diff, derby-2107-4a.stat
>
>
> 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.