postgresql vulnerable to long_running_transaction

postgresqlVulnerable Tolong running transaction bloat

Source: Technology·Target: Failure Mode

Summary

PostgreSQL's MVCC model prevents VACUUM from reclaiming dead tuples visible in any open transaction snapshot; long-running transactions cause table bloat and risk transaction ID wraparound.

Evidence

·long_running_transaction_bloat: PostgreSQL cannot VACUUM tuples visible in any open snapshot, risking XID wraparound; lists postgresql in affects_technologies (failure_modes/long_running_transaction_bloat.yaml)
·postgresql documents autovacuum blocking on high-write tables causing table/index bloat (technologies/postgresql.yaml known_failure_modes)

Evidence grounding

Grounded, 2 supporting items

PostgreSQL MVCC cannot VACUUM dead tuples still visible to an open transaction's snapshot.