On April 29, 2025, Jepsen released a report on transaction visibility behavior in Amazon RDS for PostgreSQL and its Multi-AZ clusters, which has been acknowledged since at least 2013. The report identifies a Long Fork anomaly affecting the visibility order of transactions between primary and replica nodes in cluster configurations, which does not lead to data loss or corruption and is absent in Single-AZ deployments. This anomaly allows two readers to see transactions in different sequences, breaching Snapshot Isolation. It affects all isolation levels in community PostgreSQL and can also occur in self-managed deployments. The issue has been discussed extensively in the PostgreSQL community, and potential solutions, including synchronizing visibility with commit order using Commit Sequence Numbers, have been proposed. AWS has established the PostgreSQL Contributors Team to address this anomaly and enhance PostgreSQL's capabilities.