Red Hat Bugzilla – Bug 130818
PostgreSQL can lose committed transactions
Last modified: 2013-07-02 23:01:47 EDT
Description of problem: Transactions committed just before the last
checkpoint before a database crash may be lost, in whole or in part,
Version-Release number of selected component (if applicable): All PG
How reproducible: Difficult to reproduce due to narrow window of
vulnerability, but a fairly reproducible test case is described at
Steps to Reproduce:
1. See link
Actual results: Lost data
Expected results: No lost data
Additional info: This is repaired in the most recent upstream
releases. For AS2.1, we are using the 7.1 series of PG releases, for
which there is no upstream patch; we will need to backport a fix.
Fix made for postgresql-7.1.3-6.rhel2.1AS. A side-effect of the fix
is that the commit_delay functionality is disabled ... but I doubt
anyone will miss it.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.