- Issued:
- 2005-04-28
- Updated:
- 2005-04-28
RHBA-2005:240 - Bug Fix Advisory
Synopsis
postgresql bug fix update
Type/Severity
Bug Fix Advisory
Topic
Updated postgresql packages that fix a loss-of-data scenario are now available.
Description
PostgreSQL is an advanced Object-Relational database management system
(DBMS) that supports almost all SQL constructs (including
transactions, subselects, and user-defined types and functions).
In the original release of PostgreSQL 7.1, a certain type of possible data
corruption was treated as a PANIC-grade error, causing the server to shut
down. If this situation occurred again while trying to restart the server,
there was no way to persuade the server to start at all; yet, there
might not actually be anything wrong with the user data in the database.
The situation is rare but has been seen several times in the field. This
update allows the server to restart by downgrading the error condition to a
NOTICE when it is seen during restart.
All users who are running a PostgreSQL 7.1 server are advised to upgrade to
these updated packages. Note that the same change has already been made in
PostgreSQL 7.2 and later releases.
Solution
Before applying this update, make sure that all previously-released
errata relevant to your system have been applied. Use Red Hat
Network to download and update your packages. To launch the Red Hat
Update Agent, use the following command:
up2date
For information on how to install packages manually, refer to the
following Web page for the System Administration or Customization
guide specific to your system:
Affected Products
- Red Hat Enterprise Linux Server 2 ia64
- Red Hat Enterprise Linux Server 2 i386
- Red Hat Enterprise Linux Workstation 2 ia64
- Red Hat Enterprise Linux Workstation 2 i386
Fixes
- BZ - 149760 - PostgreSQL 7.1 won't restart if it encounters corrupt data
CVEs
(none)
References
(none)
The Red Hat security contact is secalert@redhat.com. More contact details at https://access.redhat.com/security/team/contact/.