Deadlocks. Everything that developer needs to know

Speaker(s)Denis Reznik

Duration: 60 minutes

Track: 1:Development

It's no secret that a deadlock - it's not very good. This is an exceptional situation, when two concurrent queries request same resources, but in a different order. Classic deadlock can occur when two concurrent transactions modifying data from the two tables in a different order. Unfortunatelly in real life deadlocks can be more complex and unobvious. One of the rules, which I always keep in mind, sounds: " You can not design a database, in which the occurrence of deadlock is impossible". So we should deal with them. The algorythm is following: catch, analyze, fix. The most challenging and interesting here is the analysis part. Once you understand why it was occured, you can fix it. In this session we will focus on the analysis of complex,

Back to Top