Skip to main content

Working with Lock Conflicts

  • Chapter
  • First Online:
MySQL Concurrency
  • 795 Accesses

Abstract

The whole idea of locks is to restrict access to objects or records to avoid conflicting operations to concurrently access the object or records in a safe way. That means that, sometimes, a lock cannot be granted. What happens in that case? It depends on the locks requested and the circumstances. Metadata (including explicitly requested table locks) and InnoDB locks operate with a timeout, and for some, lock cases explicit deadlock detection exists.

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). Working with Lock Conflicts. In: MySQL Concurrency. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-6652-6_8

Download citation

Publish with us

Policies and ethics