[DERBY-5687] Back out the concurrency improvements for identity columns introduced by derby-4437

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.9.1.0
• Fix Version/s: 10.9.1.0
• Component/s: SQL
• Labels: derby_backport_reject_10_8
• Assignee: Richard N. Hillegas
• Reporter: Richard N. Hillegas
• Created: 09/Apr/12 12:58
• Updated: 27/Jun/13 22:21
• Resolved: 27/Jun/13 22:21

Description

DERBY-4437 attempted to improve the concurrency of identity columns by using SYSSEQUENCE-style sequence generators. These improvements caused NsTest to behave differently than it used to and they disclosed a problem in clearing the identity cache. The community lost confidence in this solution and it was backed out of the 10.8 branch under issue DERBY-5448. This new issue is filed to back the improvements out of the 10.9 trunk. Further useful discussion about how to improve the concurrency and correctness of identity columns has been taking place on DERBY-5443 and DERBY-5493.

For the 10.9 release, identity columns will return to their old behavior of being ill-suited for high concurrency applications. Applications which need higher concurrency should be re-coded to use sequences rather than identity columns.

Issue Links

• relates to: DERBY-5671 NsTest does not run on trunk do multiple issues stemming from concurrency improvements
• relates to: DERBY-4437 Concurrent inserts into table with identity column perform poorly
• relates to: DERBY-5307 Document the behavior of the derby.language.sequence.preallocator property.