DBRaven
Start Review →
Relationship · Vulnerable To
write heavy transactionalVulnerable Tolong running transaction bloat
Source: Workload·Target: Failure Mode

Summary

Write-heavy transactional workloads are vulnerable to transaction bloat when transactions are held open during slow external calls, preventing PostgreSQL VACUUM from reclaiming dead tuples.

Evidence

  • ·long_running_transaction_bloat: PostgreSQL cannot VACUUM dead tuples visible to an open snapshot; triggered by holding a transaction open during slow external calls (failure_modes/long_running_transaction_bloat.yaml)
  • ·write_heavy_transactional's primary constraints are WAL pressure, lock contention, and index maintenance (workloads/write_heavy_transactional.yaml)

Evidence grounding

Grounded, 2 supporting items

High write volume plus a held-open transaction blocks VACUUM, compounding table/index bloat.

write_heavy_transactional vulnerable to long_running_transaction_bloat: DBRaven