pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Vik Fearing <vik.fearing@2ndquadrant.com>
To: pgsql-docs@postgresql.org
Subject: No, that's backwards.
Date: Sun, 9 Jul 2017 15:30:54 +0200
Message-ID: <b6aaa23d-e26f-6404-a30d-e89431492d5d@2ndquadrant.com> (raw)
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-docs>

The documentation at
https://www.postgresql.org/docs/current/static/storage-vm.html says that
the visibility map "keeps track of which pages contain only unfrozen
tuples".

This is wrong; it keeps track of all-frozen pages not all-unfrozen.

Trivial patch attached.
-- 
Vik Fearing                                          +33 6 46 75 15 36
http://2ndQuadrant.fr     PostgreSQL : Expertise, Formation et Support

-- 
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs

Attachments:

unfrozen.patch (text/x-patch, 751B) download
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 <literal>_vm</> suffix. For example,
 if the filenode of a relation is 12345, the VM is stored in a file called

view thread (2+ messages)  latest in thread

Message-ID: <b6aaa23d-e26f-6404-a30d-e89431492d5d@2ndquadrant.com>
Permalink:  ../b6aaa23d-e26f-6404-a30d-e89431492d5d@2ndquadrant.com/
Also on:    postgresql.org/message-id/b6aaa23d-e26f-6404-a30d-e89431492d5d@2ndquadrant.com

copy link · copy postgr.es · copy git am

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: vik.fearing@2ndquadrant.com
  Subject: Re: No, that's backwards.
  In-Reply-To: <b6aaa23d-e26f-6404-a30d-e89431492d5d@2ndquadrant.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox