From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Thu, 13 May 2010 18:54:23 +0000 (+0000)
Subject: Use "TOAST table" in place of the vague, not-used-elsewhere phrase
X-Git-Tag: REL8_4_4~4
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=099aff05c3468de94626d1827ea1b39bda4ed6da;p=postgresql

Use "TOAST table" in place of the vague, not-used-elsewhere phrase
"supplementary storage table".
---

diff --git a/doc/src/sgml/ref/alter_table.sgml b/doc/src/sgml/ref/alter_table.sgml
index cccbfd2da6..ad7080139d 100644
--- a/doc/src/sgml/ref/alter_table.sgml
+++ b/doc/src/sgml/ref/alter_table.sgml
@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/alter_table.sgml,v 1.106 2009/05/03 20:45:43 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/alter_table.sgml,v 1.106.2.1 2010/05/13 18:54:23 tgl Exp $
 PostgreSQL documentation
 -->
 
@@ -163,7 +163,8 @@ where <replaceable class="PARAMETER">action</replaceable> is one of:
     <listitem>
      <para>
       This form sets the storage mode for a column. This controls whether this
-      column is held inline or in a supplementary table, and whether the data
+      column is held inline or in a secondary <acronym>TOAST</> table, and
+      whether the data
       should be compressed or not. <literal>PLAIN</literal> must be used
       for fixed-length values such as <type>integer</type> and is
       inline, uncompressed. <literal>MAIN</literal> is for inline,
@@ -171,9 +172,9 @@ where <replaceable class="PARAMETER">action</replaceable> is one of:
       uncompressed data, and <literal>EXTENDED</literal> is for external,
       compressed data.  <literal>EXTENDED</literal> is the default for most
       data types that support non-<literal>PLAIN</literal> storage.
-      Use of <literal>EXTERNAL</literal> will
-      make substring operations on <type>text</type> and <type>bytea</type>
-      columns faster, at the penalty of increased storage space.  Note that
+      Use of <literal>EXTERNAL</literal> will make substring operations on
+      very large <type>text</type> and <type>bytea</type> values run faster,
+      at the penalty of increased storage space.  Note that
       <literal>SET STORAGE</> doesn't itself change anything in the table,
       it just sets the strategy to be pursued during future table updates.
       See <xref linkend="storage-toast"> for more information.
diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml
index ad64cd32b7..1d0b8a4904 100644
--- a/doc/src/sgml/ref/create_table.sgml
+++ b/doc/src/sgml/ref/create_table.sgml
@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/create_table.sgml,v 1.114.2.1 2009/10/27 14:00:15 alvherre Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/create_table.sgml,v 1.114.2.2 2010/05/13 18:54:23 tgl Exp $
 PostgreSQL documentation
 -->
 
@@ -696,11 +696,12 @@ and <replaceable class="PARAMETER">table_constraint</replaceable> is:
     indexes are documented in <xref linkend="SQL-CREATEINDEX"
     endterm="sql-createindex-title">.  The storage parameters currently
     available for tables are listed below.  For each parameter, unless noted,
-    there is an additional, identically named parameter, prefixed with
-    <literal>toast.</literal> which can be used to control the behavior of the
-    supplementary storage table, if any; see <xref linkend="storage-toast">.
-    Note that the supplementary storage table inherits the
-    <literal>autovacuum</literal> values from its parent table, if there are
+    there is an additional parameter with the same name prefixed with
+    <literal>toast.</literal>, which can be used to control the behavior of the
+    table's secondary <acronym>TOAST</> table, if any
+    (see <xref linkend="storage-toast"> for more information about TOAST).
+    Note that the TOAST table inherits the
+    <literal>autovacuum_*</literal> values from its parent table, if there are
     no <literal>toast.autovacuum_*</literal> settings set.
    </para>
 
@@ -719,8 +720,7 @@ and <replaceable class="PARAMETER">table_constraint</replaceable> is:
       original, which is more efficient than placing it on a different page.
       For a table whose entries are never updated, complete packing is the
       best choice, but in heavily updated tables smaller fillfactors are
-      appropriate.  This parameter cannot be set for the supplementary
-      storage table.
+      appropriate.  This parameter cannot be set for TOAST tables.
      </para>
     </listitem>
    </varlistentry>