12.03.2014 Tech Alert: Data Corruption Issue in PostgreSQL 9.3
We strongly recommend upgrading to a version that fixes the issue when available. Although a fix has been committed to the postgresql community repository, no new release is available yet.
- Servers running PostgreSQL 9.3.0, 9.3.1, 9.3.2, 9.3.3
- Replicated servers using the built-in replication mechanism, including streaming replication, archive based replication and point in time recovery.
- Servers that have been restarted with pg_ctl stop -m immediate, server crashes or by hardware crashes.
Prerequisites for corruption:
- Several concurrent sessions performing UPDATEs
- Foreign keys or explicit usage of SELECT ... FOR NO KEY SHARE
Data corruption symptoms include:
- Updated rows are visible in sequential scans, but not in index scans
- Updated versions of rows are lost
To diagnose whether you are affected we recommend rechecking all your foreign key dependencies, for example using this script (click here). Please open a support ticket if you have reasons to believe you are affected by the issue.