Blog

Your dream job? Lets Git IT.
Interactive technical interview preparation platform designed for modern developers.

XGitHub

Platform

  • Categories

Resources

  • Blog
  • About the app
  • FAQ
  • Feedback

Legal

  • Privacy Policy
  • Terms of Service

© 2025 LetsGit.IT. All rights reserved.

LetsGit.IT/Categories/Databases
Databaseshard

Why are long transactions dangerous in production databases?

Tags
#transactions#locks#mvcc#bloat#replication
Back to categoryPractice quiz

Answer

Long transactions can hold locks for a long time, block other queries, and increase contention. In MVCC databases they can also prevent cleanup of old row versions, leading to bloat. They can also increase replication lag and make failures harder to recover from.

Related questions

Databases
Autocommit vs explicit transactions: when does it matter?
#database#transactions#autocommit
Databases
Isolation levels: what’s the difference between Read Committed, Repeatable Read, and Serializable?
#database#transactions#isolation
Databases
Deadlock: what is it and how do databases resolve it?
#database#transactions#locks
Databases
What is a deadlock in a database and how do you reduce it?
#deadlock#locking#transactions
Databases
Replication vs sharding — what problem does each solve?
#replication#sharding#scaling
Databases
What is an isolation level (and why do we care)?
#transactions#isolation#concurrency