As you probably know, Firebird Conference 2019 will include the practical workshops, and the article "How to track deadlocks in Firebird" is one of the sneaks peeks of the workshop "All About Transactions", which will be done by Vlad Khorsun, Firebird core developer, and Alexey Kovyazin from IBSurgeon.
To help developers investigate the update conflicts, Firebird puts into error messages the reference to the concurrent transaction – i.e., the transaction where the concurrent update is not yet committed. Together with Trace API, it gives us the ability to track both conflicting operations.
Let's consider the practical steps on how to do it: read the article "How to track deadlocks in Firebird".
en
br
Ru