Bug 7583

Summary:	[Update Request]Update postgresql packages to fix several potential data corruption issues [mga2]
Product:	Mageia	Reporter:	Funda Wang <fundawang>
Component:	RPM Packages	Assignee:	QA Team <qa-bugs>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	ed_rus099, sysadmin-bugs, tmb
Version:	2	Keywords:	validated_update
Target Milestone:	---
Hardware:	All
OS:	Linux
URL:	http://www.postgresql.org/about/news/1416/
Whiteboard:	MGA2-32-OK MGA2-64-OK
Source RPM:	postgresql9.1-9.1.6-1, postgresql9.0-9.0.10-1, postgresql8.4-8.4.14-1	CVE:
Status comment:

Description Funda Wang 2012-09-26 11:13:17 CEST

The PostgreSQL Global Development Group has released an update to all current versions of the PostgreSQL database system, including 9.2.1, 9.1.6, 9.0.10, 8.4.14 and 8.3.21. This update fixes critical issues for major versions 9.1 and 9.2, and users running those versions should apply it as soon as possible. Users of versions 8.3, 8.4 and 9.0 should plan to update at the next scheduled downtime.

The update fixes two potential data corruption issues present in the PostgreSQL 9.1 and 9.2 for any server which has crashed, been shutdown with "immediate", or was failed over to a standby. First, the PostgreSQL development team has discovered a chance of corruption of BTREE and GIN indexes for databases. Second, there is a significant chance of corruption of the visibility map. This update fixes both issues.

Packages in Mageia 2 and Mageia 1 has been updated to fix the issues and to provide other bug fixes to older branches of PostgreSQL.

Comment 1 Eduard Beliaev 2012-09-27 16:57:57 CEST

Testing on Mageia 2 i586.

CC: (none) => ed_rus099

David Walser 2012-09-27 17:42:03 CEST

Component: Security => RPM Packages
Whiteboard: (none) => MGA1TOO

Comment 2 David Walser 2012-09-27 17:43:32 CEST

SRPMS:
postgresql8.4-8.4.14-1.mga1
postgresql9.0-9.0.10-1.mga1
postgresql8.4-8.4.14-1.mga2
postgresql9.0-9.0.10-1.mga2
postgresql9.1-9.1.6-1.mga2

Comment 3 Eduard Beliaev 2012-09-27 17:52:44 CEST

Testing complete on Mageia 2 i586 using webmin. No problems.

Tested:
postgresql8.4-8.4.14-1.mga2
postgresql9.0-9.0.10-1.mga2
postgresql9.1-9.1.6-1.mga2

Whiteboard: MGA1TOO => MGA1TOO MGA2-32-OK

Comment 4 Eduard Beliaev 2012-09-27 21:01:42 CEST

Works ok on Mageia 2 x86_64, tested with webmin.

Packages tested:
postgresql8.4-8.4.14-1.mga2
postgresql9.0-9.0.10-1.mga2
postgresql9.1-9.1.6-1.mga2

Whiteboard: MGA1TOO MGA2-32-OK => MGA1TOO MGA2-32-OK MGA2-64-OK

Comment 5 claire robinson 2012-10-11 18:37:30 CEST

Splitting this bug so we can push mga2 to fix problems with php.

Validating for Mageia 2 ONLY.

Advisory
--------
The PostgreSQL Global Development Group has released an update to all current
versions of the PostgreSQL database system, including 9.2.1, 9.1.6, 9.0.10,
8.4.14 and 8.3.21. This update fixes critical issues for major versions 9.1 and
9.2, and users running those versions should apply it as soon as possible.
Users of versions 8.3, 8.4 and 9.0 should plan to update at the next scheduled
downtime.

The update fixes two potential data corruption issues present in the PostgreSQL
9.1 and 9.2 for any server which has crashed, been shutdown with "immediate",
or was failed over to a standby. First, the PostgreSQL development team has
discovered a chance of corruption of BTREE and GIN indexes for databases.
Second, there is a significant chance of corruption of the visibility map. This
update fixes both issues.
---------

SRPMs:
postgresql8.4-8.4.14-1.mga2
postgresql9.0-9.0.10-1.mga2
postgresql9.1-9.1.6-1.mga2

Bug 7770 created for Mageia 1

Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs
Summary: [Update Request]Update postgresql packages to fix several potential data corruption issues => [Update Request]Update postgresql packages to fix several potential data corruption issues [mga2]
Whiteboard: MGA1TOO MGA2-32-OK MGA2-64-OK => MGA2-32-OK MGA2-64-OK

Comment 6 Thomas Backlund 2012-10-11 19:29:44 CEST

Update pushed:
https://wiki.mageia.org/en/Support/Advisories/MGAA-2012-0209

Status: NEW => RESOLVED
CC: (none) => tmb
Resolution: (none) => FIXED