doc: Improve references to term "FSM" in pageinspect and pgfreespacemap

Author: Dong Wook Lee
Reviewed-by: Laurenz Albe
Discussion: https://postgr.es/m/CAAcBya+=F=HaHxJ7tGjAM1r=A=+bDbimpsex8Vqrb4GjqFDYsQ@mail.gmail.com

diff --git a/doc/src/sgml/pageinspect.sgml b/doc/src/sgml/pageinspect.sgml
index 24b5e463ed9a39b9baa986c27c58b43b51e83a16..55513cf522a7cf97ae0a85e55f8bf6e0c14e5f90 100644 (file)
--- a/doc/src/sgml/pageinspect.sgml
+++ b/doc/src/sgml/pageinspect.sgml
@@ -31,9 +31,11 @@
       relation and returns a copy as a bytea value.  This allows a
       single time-consistent copy of the block to be obtained.
       fork should be 'main' for
-      the main data fork, 'fsm' for the free space map,
-      'vm' for the visibility map, or 'init'
-      for the initialization fork.
+      the main data fork, 'fsm' for the
+      free space map,
+      'vm' for the
+      visibility map, or
+      'init' for the initialization fork.
      
     
    
@@ -136,7 +138,7 @@ test=# SELECT page_checksum(get_raw_page('pg_class', 0), 0);
     
      
       fsm_page_contents shows the internal node structure
-      of an FSM page.  For example:
+      of an FSM page.  For example:
 
 test=# SELECT fsm_page_contents(get_raw_page('pg_class', 'fsm', 0));
 
@@ -147,7 +149,7 @@ test=# SELECT fsm_page_contents(get_raw_page('pg_class', 'fsm', 0));
      
      
       See src/backend/storage/freespace/README for more
-      information on the structure of an FSM page.
+      information on the structure of an FSM page.
      
     
    

diff --git a/doc/src/sgml/pgfreespacemap.sgml b/doc/src/sgml/pgfreespacemap.sgml
index 5025498249d87267101643b26d3a1ecbb75603f6..1f7867d9b9f60f3322b6f0769374c9ec63c06ec0 100644 (file)
--- a/doc/src/sgml/pgfreespacemap.sgml
+++ b/doc/src/sgml/pgfreespacemap.sgml
@@ -9,10 +9,10 @@
 
  
   The pg_freespacemap module provides a means for examining the
-  free space map (FSM). It provides a function called
-  pg_freespace, or two overloaded functions, to be
-  precise. The functions show the value recorded in the free space map for
-  a given page, or for all pages in the relation.
+  free space map (FSM).
+  It provides a function called pg_freespace, or two
+  overloaded functions, to be precise. The functions show the value recorded in
+  the free space map for a given page, or for all pages in the relation.
  
 
  
@@ -36,7 +36,7 @@
     
      
       Returns the amount of free space on the page of the relation, specified
-      by blkno, according to the FSM.
+      by blkno, according to the FSM.
      
     
    
@@ -50,7 +50,8 @@
     
      
       Displays the amount of free space on each page of the relation,
-      according to the FSM. A set of (blkno bigint, avail int2)
+      according to the FSM. A set of
+      (blkno bigint, avail int2)
       tuples is returned, one tuple for each page in the relation.
      
     
@@ -112,8 +113,8 @@ postgres=# SELECT * FROM pg_freespace('foo', 7);
 
   
    Original version by Mark Kirkwood [email protected].
-   Rewritten in version 8.4 to suit new FSM implementation by Heikki
-   Linnakangas [email protected]
+   Rewritten in version 8.4 to suit new FSM implementation
+   by Heikki Linnakangas [email protected]
   
  
 

diff --git a/doc/src/sgml/storage.sgml b/doc/src/sgml/storage.sgml
index 7136bbe7a32fde278f0afc3bae5e8a58ee1f0c5b..f4b9f665899cb8cc6db20c9a1742ab10bf0ee6b7 100644 (file)
--- a/doc/src/sgml/storage.sgml
+++ b/doc/src/sgml/storage.sgml
@@ -603,10 +603,11 @@ tuple would otherwise be too big.
 
 
 Each heap and index relation, except for hash indexes, has a Free Space Map
-(FSM) to keep track of available space in the relation. It's stored
-alongside the main relation data in a separate relation fork, named after the
-filenode number of the relation, plus a _fsm suffix. For example,
-if the filenode of a relation is 12345, the FSM is stored in a file called
+(FSM) to keep track of available space in the relation.
+It's stored alongside the main relation data in a separate relation fork,
+named after the filenode number of the relation, plus a _fsm
+suffix. For example, if the filenode of a relation is 12345, the
+FSM is stored in a file called
 12345_fsm, in the same directory as the main relation file.