Refer to tables by id, not by "the following table", because tables are in

theory floating elements.

diff --git a/doc/src/sgml/cube.sgml b/doc/src/sgml/cube.sgml
index 2242e3983098c8d15cddb22ab13ca89745d3c732..64ab40598d5c99f193a468f825d567f313781a76 100644 (file)
--- a/doc/src/sgml/cube.sgml
+++ b/doc/src/sgml/cube.sgml
@@ -16,12 +16,13 @@
   <title>Syntax</title>
 
   <para>
-   The following are valid external representations for the <type>cube</>
-   type.  <replaceable>x</>, <replaceable>y</>, etc denote floating-point
-   numbers:
+   <xref linkend="cube-repr-table"> shows the valid external
+   representations for the <type>cube</>
+   type.  <replaceable>x</>, <replaceable>y</>, etc. denote
+   floating-point numbers.
   </para>
 
-  <table>
+  <table id="cube-repr-table">
    <title>Cube external representations</title>
    <tgroup cols="2">
     <tbody>
@@ -159,10 +160,10 @@ a &lt;@ b                Contained in
   </para>
 
   <para>
-   The following functions are available:
+   <xref linkend="cube-functions-table"> shows the available functions.
   </para>
 
-  <table>
+  <table id="cube-functions-table">
    <title>Cube functions</title>
    <tgroup cols="2">
     <tbody>

diff --git a/doc/src/sgml/ecpg.sgml b/doc/src/sgml/ecpg.sgml
index 52d642cb7e041e4da9bd89e9400d517c574257ec..3d005f0f4706faaf707cb25062a179fc93904251 100644 (file)
--- a/doc/src/sgml/ecpg.sgml
+++ b/doc/src/sgml/ecpg.sgml
@@ -1137,8 +1137,9 @@ date PGTYPESdate_from_asc(char *str, char **endptr);
         currently no variable to change that within ecpg.
        </para>
        <para>
-        The following input formats are allowed:
-        <table>
+        <xref linkend="ecpg-pgtypesdate-from-asc-table"> shows the allowed input formats.
+       </para>
+        <table id="ecpg-pgtypesdate-from-asc-table">
          <title>Valid input formats for <function>PGTYPESdate_from_asc</function></title>
          <tgroup cols="2">
           <thead>
@@ -1219,7 +1220,6 @@ date PGTYPESdate_from_asc(char *str, char **endptr);
           </tbody>
          </tgroup>
         </table>
-       </para>
       </listitem>
      </varlistentry>
 
@@ -1392,10 +1392,11 @@ int PGTYPESdate_fmt_asc(date dDate, char *fmtstring, char *outbuf);
         All other characters are copied 1:1 to the output string.
        </para>
        <para>
-        The following table indicates a few possible formats. This will give
+        <xref linkend="ecpg-pgtypesdate-fmt-asc-example-table"> indicates a few possible formats. This will give
         you an idea of how to use this function. All output lines are based on
-        the same date: November, 23rd, 1959.
-        <table>
+        the same date: November 23, 1959.
+       </para>
+        <table id="ecpg-pgtypesdate-fmt-asc-example-table">
          <title>Valid input formats for <function>PGTYPESdate_fmt_asc</function></title>
          <tgroup cols="2">
           <thead>
@@ -1456,7 +1457,6 @@ int PGTYPESdate_fmt_asc(date dDate, char *fmtstring, char *outbuf);
           </tbody>
          </tgroup>
         </table>
-       </para>
       </listitem>
      </varlistentry>
 
@@ -1483,9 +1483,10 @@ int PGTYPESdate_defmt_asc(date *d, char *fmt, char *str);
         day.
        </para>
        <para>
-        The following table indicates a few possible formats. This will give
+        <xref linkend="ecpg-rdefmtdate-example-table"> indicates a few possible formats. This will give
         you an idea of how to use this function.
-        <table>
+       </para>
+        <table id="ecpg-rdefmtdate-example-table">
          <title>Valid input formats for <function>rdefmtdate</function></title>
          <tgroup cols="3">
           <thead>
@@ -1564,7 +1565,6 @@ int PGTYPESdate_defmt_asc(date *d, char *fmt, char *str);
           </tbody>
          </tgroup>
         </table>
-       </para>
       </listitem>
      </varlistentry>
     </variablelist>
@@ -1612,8 +1612,9 @@ timestamp PGTYPEStimestamp_from_asc(char *str, char **endptr);
         specifiers are silently discarded.
        </para>
        <para>
-        The following table contains a few examples for input strings:
-        <table>
+        <xref linkend="ecpg-pgtypestimestamp-from-asc-example-table"> contains a few examples for input strings.
+       </para>
+        <table id="ecpg-pgtypestimestamp-from-asc-example-table">
          <title>Valid input formats for <function>PGTYPEStimestamp_from_asc</function></title>
          <tgroup cols="2">
           <thead>
@@ -1642,7 +1643,6 @@ timestamp PGTYPEStimestamp_from_asc(char *str, char **endptr);
           </tbody>
          </tgroup>
         </table>
-       </para>
       </listitem>
      </varlistentry>
 

diff --git a/doc/src/sgml/isn.sgml b/doc/src/sgml/isn.sgml
index b9f4767e609abaada0d2e7342a1f08f7c807a7ce..ce961189610b1f3e8620f44418832a1043733b85 100644 (file)
--- a/doc/src/sgml/isn.sgml
+++ b/doc/src/sgml/isn.sgml
@@ -210,11 +210,12 @@
   <para>
    The <filename>isn</> module provides the standard comparison operators,
    plus btree and hash indexing support for all these datatypes.  In
-   addition there are several specialized functions.  In this table,
-   <type>isn</> means any one of the module's data types:
+   addition there are several specialized functions; shown in <xref linkend="isn-functions">.
+   In this table,
+   <type>isn</> means any one of the module's data types.
   </para>
 
-  <table>
+  <table id="isn-functions">
    <title><filename>isn</> functions</title>
    <tgroup cols="3">
     <thead>

diff --git a/doc/src/sgml/pgbuffercache.sgml b/doc/src/sgml/pgbuffercache.sgml
index 1ac538641d58455a3e4129f32f542152f7238f33..45a859091f99b53a0b538a9bfd60c8c26f0f52dc 100644 (file)
--- a/doc/src/sgml/pgbuffercache.sgml
+++ b/doc/src/sgml/pgbuffercache.sgml
@@ -28,10 +28,10 @@
   <title>The <structname>pg_buffercache</structname> view</title>
 
   <para>
-   The definitions of the columns exposed by the view are:
+   The definitions of the columns exposed by the view are shown in <xref linkend="pgbuffercache-columns">.
   </para>
 
-  <table>
+  <table id="pgbuffercache-columns">
    <title><structname>pg_buffercache</> Columns</title>
 
    <tgroup cols="4">

diff --git a/doc/src/sgml/pgcrypto.sgml b/doc/src/sgml/pgcrypto.sgml
index 2a4f6c3505d141ca4a037682b51a88fb2b90f839..787cebf171920374067ee67814ef8364c5a58b92 100644 (file)
--- a/doc/src/sgml/pgcrypto.sgml
+++ b/doc/src/sgml/pgcrypto.sgml
@@ -217,10 +217,11 @@
     too high a count the time to calculate a hash may be several years
     &mdash; which is somewhat impractical.  If the <parameter>iter_count</>
     parameter is omitted, the default iteration count is used.
-    Allowed values for <parameter>iter_count</> depend on the algorithm:
+    Allowed values for <parameter>iter_count</> depend on the algorithm and
+    are shown in <xref linkend="pgcrypto-icfc-table">.
    </para>
 
-   <table>
+   <table id="pgcrypto-icfc-table">
     <title>Iteration counts for <function>crypt()</></title>
     <tgroup cols="4">
      <thead>
@@ -262,7 +263,7 @@
    </para>
 
    <para>
-    Here is a table that gives an overview of the relative slowness
+    <xref linkend="pgcrypto-hash-speed-table"> gives an overview of the relative slowness
     of different hashing algorithms.
     The table shows how much time it would take to try all
     combinations of characters in an 8-character password, assuming
@@ -273,7 +274,7 @@
     <function>gen_salt</function>.
    </para>
 
-   <table>
+   <table id="pgcrypto-hash-speed-table">
     <title>Hash algorithm speeds</title>
     <tgroup cols="4">
      <thead>
@@ -1224,8 +1225,7 @@
    <filename>pgcrypto</filename> uses code from the following sources:
   </para>
 
-  <table>
-   <title>Credits</title>
+  <informaltable>
    <tgroup cols="3">
     <thead>
      <row>
@@ -1277,7 +1277,7 @@
      </row>
     </tbody>
    </tgroup>
-  </table>
+  </informaltable>
  </sect2>
 
 </sect1>

diff --git a/doc/src/sgml/pgrowlocks.sgml b/doc/src/sgml/pgrowlocks.sgml
index 9a42406dae98df24f453fb37252ee42f295c2bdb..4f538e7104757703b454f3a3c8789d5b2e600cbb 100644 (file)
--- a/doc/src/sgml/pgrowlocks.sgml
+++ b/doc/src/sgml/pgrowlocks.sgml
@@ -15,17 +15,17 @@
  <sect2>
   <title>Overview</title>
 
-  <synopsis>
+<synopsis>
 pgrowlocks(text) returns setof record
-  </synopsis>
+</synopsis>
 
   <para>
    The parameter is the name of a table.  The result is a set of records,
    with one row for each locked row within the table.  The output columns
-   are:
+   are shown in <xref linkend="pgrowlocks-columns">.
   </para>
 
-  <table>
+  <table id="pgrowlocks-columns">
    <title><function>pgrowlocks</> output columns</title>
 
    <tgroup cols="3">

diff --git a/doc/src/sgml/pgstatstatements.sgml b/doc/src/sgml/pgstatstatements.sgml
index 4b8658dd440de4cda1127b9410b6cb3f32e8629e..2003a169bc3a132ddc50ad8a168e4cef31a3bf7d 100644 (file)
--- a/doc/src/sgml/pgstatstatements.sgml
+++ b/doc/src/sgml/pgstatstatements.sgml
@@ -27,10 +27,10 @@
    named <structname>pg_stat_statements</>.  This view contains one row for
    each distinct query text, database ID, and user ID (up to the maximum
    number of distinct statements that the module can track).  The columns
-   of the view are:
+   of the view are shown in <xref linkend="pgstatstatements-columns">.
   </para>
 
-  <table>
+  <table id="pgstatstatements-columns">
    <title><structname>pg_stat_statements</> columns</title>
 
    <tgroup cols="4">

diff --git a/doc/src/sgml/pgstattuple.sgml b/doc/src/sgml/pgstattuple.sgml
index 821f631fc7acf6eb328f1a941663a1107f05724f..742541d24cca3e17476bc4b4ebe01920aa0272bf 100644 (file)
--- a/doc/src/sgml/pgstattuple.sgml
+++ b/doc/src/sgml/pgstattuple.sgml
@@ -28,8 +28,7 @@
       to determine whether vacuum is necessary or not.  The argument is the
       target relation's name (optionally schema-qualified).
       For example:
-     </para>
-     <programlisting>
+<programlisting>
 test=> SELECT * FROM pgstattuple('pg_catalog.pg_proc');
 -[ RECORD 1 ]------+-------
 table_len          | 458752
@@ -41,13 +40,11 @@ dead_tuple_len     | 3157
 dead_tuple_percent | 0.69
 free_space         | 8932
 free_percent       | 1.95
-     </programlisting>
-
-    <para>
-     The output columns are:
+</programlisting>
+     The output columns are described in <xref linkend="pgstattuple-columns">.
     </para>
 
-    <table>
+    <table id="pgstattuple-columns">
      <title><function>pgstattuple</function> output columns</title>
      <tgroup cols="3">
       <thead>

diff --git a/doc/src/sgml/seg.sgml b/doc/src/sgml/seg.sgml
index d75cf76c1766befe49ffffcabc6697220f24a232..6d3b79437cd2d0a143b56f0282ceb98dc5109c01 100644 (file)
--- a/doc/src/sgml/seg.sgml
+++ b/doc/src/sgml/seg.sgml
@@ -89,13 +89,13 @@ test=> select '6.25 .. 6.50'::seg as "pH";
   </para>
 
   <para>
-   In the following table, <replaceable>x</>, <replaceable>y</>, and
+   In <xref linkend="seg-repr-table">, <replaceable>x</>, <replaceable>y</>, and
    <replaceable>delta</> denote
    floating-point numbers.  <replaceable>x</> and <replaceable>y</>, but
-   not <replaceable>delta</>, can be preceded by a certainty indicator:
+   not <replaceable>delta</>, can be preceded by a certainty indicator.
   </para>
 
-  <table>
+  <table id="seg-repr-table">
    <title><type>seg</> external representations</title>
    <tgroup cols="2">
     <tbody>

diff --git a/doc/src/sgml/xml2.sgml b/doc/src/sgml/xml2.sgml
index 5ed0124daf4b8c13c1a688259b40fbcca6b48639..35076847a3045fce58e36927b3343f03c7cdca31 100644 (file)
--- a/doc/src/sgml/xml2.sgml
+++ b/doc/src/sgml/xml2.sgml
@@ -34,11 +34,12 @@
   <title>Description of functions</title>
 
   <para>
+   <xref linkend="xml2-functions-table"> shows the functions provided by this module.
    These functions provide straightforward XML parsing and XPath queries.
    All arguments are of type <type>text</>, so for brevity that is not shown.
   </para>
 
-  <table>
+  <table id="xml2-functions-table">
    <title>Functions</title>
    <tgroup cols="2">
     <tbody>