[DERBY-4081] BTreeController.comparePreviousRecord() may fail to release latch on left-most leaf

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.4.2.0
• Fix Version/s: 10.4.2.1, 10.5.3.1, 10.6.1.0
• Component/s: Store
• Urgency: Normal
• Assignee: Knut Anders Hatlen
• Reporter: Knut Anders Hatlen
• Created: 03/Mar/09 11:02
• Updated: 05/Jul/10 16:39
• Resolved: 20/Aug/09 12:18

Description

If comparePreviousRecord() is called on some other leaf page than the left-most leaf, and all the rows to the left of the current position are deleted so that the position is moved all the way to slot 0 on the left-most leaf, comparePreviousRecord() will return without releasing the latch on the left-most leaf. Only the leaf on which comparePreviousRecord() is called should be latched when the method returns.

Since comparePreviousRecord() currently fails to continue after finding a deleted row, this bug is not possible to expose until DERBY-4028 is fixed.