[DERBY-6156] Starting Derby 10.9, we do not not keep statistics for single-column unique index. Check the code to see optimizer calculates correct cost even with the missing stats for such indexes

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Component/s: SQL, Store
• Labels: derby_triage10_11
• Urgency: Normal
• Assignee: Mamta A. Satoor
• Reporter: Mamta A. Satoor
• Created: 09/Apr/13 00:21
• Updated: 21/Jan/15 00:23
• Resolved: 10/Sep/13 23:07

Description

With DERBY-3790(Investigate if request for update statistics can be skipped for certain kind of indexes, one instance may be unique indexes based on one column.) we have stopped keeping statistics for single column unique index. But with DERBY-6045(in list multi-probe by primary key not chosen on tables with >256 rows), we found that optimizer code was not adjusted to tackle the missing stats and hence we were not picking index scan even though the single column unique index was the right choice. DERBY-6045 has been fixed but we should make sure there are no other places in the optimizer code where we have missed code changes to account for missing statistics for single-column unique indexes.

Issue Links

• relates to: DERBY-6045 in list multi-probe by primary key not chosen on tables with >256 rows
• relates to: DERBY-3790 Investigate if request for update statistics can be skipped for certain kind of indexes, one instance may be unique indexes based on one column.