summaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>2008-10-06 14:13:17 +0000
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>2008-10-06 14:13:17 +0000
commit5f853c655663bf829c02895de2b445a5f3caa24b (patch)
tree3dc2757ce91d5409d1def38bbbf666fbfd8aae6d /doc/src
parente59ad5fbb6d71b43a6c4e50875fda56e88527532 (diff)
Use fork names instead of numbers in the file names for additional
relation forks. While the file names are not visible to users, for those that do peek into the data directory, it's nice to have more descriptive names. Per Greg Stark's suggestion.
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/pageinspect.sgml8
-rw-r--r--doc/src/sgml/storage.sgml9
2 files changed, 8 insertions, 9 deletions
diff --git a/doc/src/sgml/pageinspect.sgml b/doc/src/sgml/pageinspect.sgml
index 94249399e10..e510d202aa4 100644
--- a/doc/src/sgml/pageinspect.sgml
+++ b/doc/src/sgml/pageinspect.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/pageinspect.sgml,v 1.4 2008/09/30 10:52:09 heikki Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/pageinspect.sgml,v 1.5 2008/10/06 14:13:17 heikki Exp $ -->
<sect1 id="pageinspect">
<title>pageinspect</title>
@@ -19,7 +19,7 @@
<variablelist>
<varlistentry>
<term>
- <function>get_raw_page(relname text, forknum int, blkno int) returns bytea</function>
+ <function>get_raw_page(relname text, fork text, blkno int) returns bytea</function>
</term>
<listitem>
@@ -27,8 +27,8 @@
<function>get_raw_page</function> reads the specified block of the named
table and returns a copy as a <type>bytea</> value. This allows a
single time-consistent copy of the block to be obtained.
- <literal>forknum</literal> should be 0 for the main data fork, or 1 for
- the FSM.
+ <literal>fork</literal> should be <literal>'main'</literal> for the main
+ data fork, or <literal>'fsm'</literal> for the FSM.
</para>
</listitem>
</varlistentry>
diff --git a/doc/src/sgml/storage.sgml b/doc/src/sgml/storage.sgml
index 51f8a2fe165..9b93ea5599b 100644
--- a/doc/src/sgml/storage.sgml
+++ b/doc/src/sgml/storage.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/storage.sgml,v 1.25 2008/09/30 10:52:10 heikki Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/storage.sgml,v 1.26 2008/10/06 14:13:17 heikki Exp $ -->
<chapter id="storage">
@@ -134,8 +134,7 @@ or index's <firstterm>filenode</> number, which can be found in
main file (aka. main fork), a <firstterm>free space map</> (see
<xref linkend="storage-fsm">) that stores information about free space
available in the relation, is stored in a file named after the filenode
-number, with the the _1 suffix. For example, if the table's filenode number
-is 12345, the FSM file is named <filename>12345_1</>.
+number, with the the <literal>_fsm</> suffix.
</para>
<caution>
@@ -385,9 +384,9 @@ comparison table, in which all the HTML pages were cut down to 7 kB to fit.
A Free Space Map is stored with every heap and index relation, except for
hash indexes, to keep track of available space in the relation. It's stored
along the main relation data, in a separate FSM relation fork, named after
-relfilenode of the relation, but with a <literal>_1</> suffix. For example,
+relfilenode of the relation, but with a <literal>_fsm</> suffix. For example,
if the relfilenode of a relation is 12345, the FSM is stored in a file called
-<filename>12345_1</>, in the same directory as the main relation file.
+<filename>12345_fsm</>, in the same directory as the main relation file.
</para>
<para>