Bug 130818 - PostgreSQL can lose committed transactions
Summary: PostgreSQL can lose committed transactions
Alias: None
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: postgresql
Version: 2.1
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Tom Lane
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2004-08-24 21:59 UTC by Tom Lane
Modified: 2013-07-03 03:01 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2005-02-16 16:25:39 UTC

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2005:150 important SHIPPED_LIVE Important: postgresql security update 2005-02-16 05:00:00 UTC

Description Tom Lane 2004-08-24 21:59:02 UTC
Description of problem: Transactions committed just before the last
checkpoint before a database crash may be lost, in whole or in part,
after recovery.

Version-Release number of selected component (if applicable): All PG
versions 7.1-7.4

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.

Comment 1 Tom Lane 2005-02-10 18:28:47 UTC
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.

Comment 2 Josh Bressers 2005-02-16 16:25:39 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.