We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Automatic Lock-Escalation from Row- to Extent-Level
Db2 is mainly using row-level locking and tries to avoid lock-escalation to table-level. This behavior is helpful in most of Db2s use cases, but there are some particular situations when locking on a higher level than row would be beneficial. Consider a kind of Data Warehouse environment which contains data for a defined time window, e.g. the last 2 years (24 months).
New data is inserted into the Db2 tables and 'old' data is deleted. The new data is inserted 'en bloc', physically stored beneath each other in continuing pages/extents. The removal of the old data deletes the continuous rows.
These actions process several millions of rows, acquiring at least several millions of rows. If Db2 would detect the 'mass insertion' and 'mass deletion' as a sequential operation which locks a significant mount of rows in an extent, Db2 could 'escalate' the locking level from row to extent.
On the one hand this would reduce the resource consumption without on he other hand reducing the concurrency (since a significant amount of rows per extent must be locked anyway).
Do not place IBM confidential, company confidential, or personal information into any field.