From: Tom Lane Date: Sun, 9 Jul 2017 16:51:15 +0000 (-0400) Subject: Doc: fix backwards description of visibility map's all-frozen data. X-Git-Tag: REL_10_BETA2~11 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=485c515d0176d3210b5405ef23be8ed32cf5c93a;p=postgresql Doc: fix backwards description of visibility map's all-frozen data. Thinko in commit a892234f8. Vik Fearing Discussion: https://postgr.es/m/b6aaa23d-e26f-6404-a30d-e89431492d5d@2ndquadrant.com --- diff --git a/doc/src/sgml/storage.sgml b/doc/src/sgml/storage.sgml index a156693ec8..aed2cf8bca 100644 --- a/doc/src/sgml/storage.sgml +++ b/doc/src/sgml/storage.sgml @@ -630,7 +630,7 @@ can be used to examine the information stored in free space maps. Each heap relation has a Visibility Map (VM) to keep track of which pages contain only tuples that are known to be visible to all active transactions; it also keeps track of which pages contain -only unfrozen tuples. It's stored +only frozen tuples. It's stored alongside the main relation data in a separate relation fork, named after the filenode number of the relation, plus a _vm suffix. For example, if the filenode of a relation is 12345, the VM is stored in a file called