Move pg_settings doc into the right section.

diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml
index b0b3f50f0f2a6cf00d481231b494aca432fe7e14..73d0da7e72fc480d0fa855bc6e2dcb58b0017e02 100644 (file)
--- a/doc/src/sgml/catalogs.sgml
+++ b/doc/src/sgml/catalogs.sgml
@@ -1,6 +1,6 @@
 <!--
  Documentation of the system catalogs, directed toward PostgreSQL developers
- $Header: /cvsroot/pgsql/doc/src/sgml/catalogs.sgml,v 2.57 2002/09/02 05:44:43 momjian Exp $
+ $Header: /cvsroot/pgsql/doc/src/sgml/catalogs.sgml,v 2.58 2002/09/02 05:52:34 momjian Exp $
  -->
 
 <chapter id="catalogs">
@@ -161,11 +161,6 @@
       <entry>database users</entry>
      </row>
 
-     <row>
-      <entry>pg_settings</entry>
-      <entry>current session run-time parameters</entry>
-     </row>
-
      <row>
       <entry>pg_statistic</entry>
       <entry>optimizer statistics</entry>
@@ -2871,62 +2866,6 @@
  </sect1>
 
 
- <sect1 id="catalog-pg-settings">
-  <title>pg_settings</title>
-
-  <para>
-   <structname>pg_settings</structname> virtual table allows display and update
-   of current session run-time parameters. There is one entry for each of the 
-   available parameters provided by <command>SHOW ALL</command>. But it is
-   in a form that allows it to be joined with other relations and have a
-   selection criteria applied.
-  </para>
-
-  <para>
-   An <command>UPDATE</command> performed on <structname>pg_settings</structname>
-   is equivalent to executing the <command>SET</command> command on that named
-   parameter. The change only affects the value used by the current session. If
-   an <command>UPDATE</command> is issued within a transaction that is later
-   aborted, the effects of the <command>UPDATE</command> command disappear when
-   the transaction is rolled back. Once the surrounding transaction is
-   committed, the effects will persist until the end of the session, unless
-   overridden by another <command>UPDATE</command> or <command>SET</command>.
-  </para>
-
-  <table>
-   <title>pg_settings Columns</title>
-
-   <tgroup cols=4>
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry>name</entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry>The name of a current session run-time parameter</entry>
-     </row>
-
-     <row>
-      <entry>setting</entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry>The value of a current session run-time parameter</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
- </sect1>
-
-
  <sect1 id="catalog-pg-statistic">
   <title>pg_statistic</title>
 

diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index d43461e61b7b9a954443c0ab1ee97a2065f65000..7a7533bff29530f46efc3a84d1b4e859adc23ada 100644 (file)
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.133 2002/09/02 05:42:54 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.134 2002/09/02 05:52:34 momjian Exp $
 -->
 
 <Chapter Id="runtime">
@@ -554,6 +554,60 @@ env PGOPTIONS='-c geqo=off' psql
     settings.
    </para>
 
+   <sect2 id="catalog-pg-settings">
+    <title>pg_settings</title>
+  
+    <para>
+     <structname>pg_settings</structname> virtual table allows display and update
+     of current session run-time parameters. There is one entry for each of the 
+     available parameters provided by <command>SHOW ALL</command>. But it is
+     in a form that allows it to be joined with other relations and have a
+     selection criteria applied.
+    </para>
+  
+    <para>
+     An <command>UPDATE</command> performed on <structname>pg_settings</structname>
+     is equivalent to executing the <command>SET</command> command on that named
+     parameter. The change only affects the value used by the current session. If
+     an <command>UPDATE</command> is issued within a transaction that is later
+     aborted, the effects of the <command>UPDATE</command> command disappear when
+     the transaction is rolled back. Once the surrounding transaction is
+     committed, the effects will persist until the end of the session, unless
+     overridden by another <command>UPDATE</command> or <command>SET</command>.
+    </para>
+  
+    <table>
+    <title>pg_settings Columns</title>
+  
+    <tgroup cols=4>
+     <thead>
+      <row>
+       <entry>Name</entry>
+       <entry>Type</entry>
+       <entry>References</entry>
+       <entry>Description</entry>
+      </row>
+     </thead>
+ 
+     <tbody>
+      <row>
+       <entry>name</entry>
+       <entry><type>text</type></entry>
+       <entry></entry>
+       <entry>The name of a current session run-time parameter</entry>
+      </row>
+ 
+      <row>
+       <entry>setting</entry>
+       <entry><type>text</type></entry>
+       <entry></entry>
+       <entry>The value of a current session run-time parameter</entry>
+      </row>
+     </tbody>
+    </tgroup>
+
+   </sect2>
+
    <sect2 id="runtime-config-optimizer">
     <title>Planner and Optimizer Tuning</title>