This bug was fixed in the package postgresql-9.5 - 9.5.5-0ubuntu0.16.10
---------------
postgresql-9.5 (9.5.5-0ubuntu0.16.10) yakkety; urgency=medium
* New upstream bug fix release (LP: #1637236)
- Fix WAL-logging of truncation of relation free space maps and visibility
maps.
It was possible for these files to not be correctly restored during
crash recovery, or to be written incorrectly on a standby server. Bogus
entries in a free space map could lead to attempts to access pages that
have been truncated away from the relation itself, typically producing
errors like "could not read block XXX: read only 0 of 8192 bytes".
Checksum failures in the visibility map are also possible, if
checksumming is enabled.
Procedures for determining whether there is a problem and repairing it
if so are discussed at
https://wiki.postgresql.org/wiki/Free_Space_Map_Problems.
- Details about other changes:
http://www.postgresql.org/docs/9.5/static/release-9-5-5.html
-- Martin Pitt <[email protected]> Thu, 27 Oct 2016 17:51:11
+0200
** Changed in: postgresql-9.1 (Ubuntu Precise)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1637236
Title:
New upstream microreleases 9.1.24, 9.3.15, 9.5.5
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-9.1/+bug/1637236/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
