![]() ![]() The latter error would almost always lead to a pg_upgrade failure due to the map file appearing to be the wrong length. On Windows, the old map was read using text mode, leading to incorrect results if the map happened to contain consecutive bytes that matched a carriage return/line feed sequence. On big-endian machines, bytes of the new visibility map were written in the wrong order, leading to a completely incorrect map. Fix possible data corruption when pg_upgrade rewrites a relation visibility map into 9.6 format (Tom Lane) Procedures for determining whether there is a problem and repairing it if so are discussed at. Checksum failures in the visibility map are also possible, if checksumming is enabled. ![]() 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". ![]() It was possible for these files to not be correctly restored during crash recovery, or to be written incorrectly on a standby server. Fix WAL-logging of truncation of relation free space maps and visibility maps (Pavan Deolasee, Heikki Linnakangas) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |