Skip to main content

Case Study: Deadlocks

  • Chapter
  • First Online:
MySQL Concurrency
  • 795 Accesses

Abstract

One of the lock issues causing the most concerns for database administrators is deadlocks. This is partly because of the name and partly because they unlike the other lock issues discussed always cause an error. However, there is as such nothing especially worrying about deadlocks compared to other locking issues. On the contrary, that they cause an error means that you know about them sooner and the lock issue resolves itself.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

eBook
USD 16.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 69.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Author information

Authors and Affiliations

Authors

Rights and permissions

Reprints and permissions

Copyright information

© 2021 Jesper Wisborg Krogh

About this chapter

Check for updates. Verify currency and authenticity via CrossMark

Cite this chapter

Krogh, J.W. (2021). Case Study: Deadlocks. In: MySQL Concurrency. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-6652-6_16

Download citation

Publish with us

Policies and ethics