Second pass over run-time configuration system. Adjust priorities on some

option settings. Sort out SIGHUP vs BACKEND -- there is no total ordering
here, so make explicit checks. Add comments explaining all of this.
Removed permissions check on SHOW command.

Add examine_subclass to the game, rename to SQL_inheritance to fit the
official data model better. Adjust documentation.

Standalone backend needs to reset all options before it starts. To
facilitate that, have IsUnderPostmaster be set by the postmaster itself,
don't wait for the magic -p switch.

Also make sure that all environment variables and argv's survive
init_ps_display(). Use strdup where necessary.

Have initdb make configuration files (postgresql.conf, pg_hba.conf) mode
0600 -- having configuration files is no fun if you can't edit them.

doc/src/sgml/advanced.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/advanced.sgml,v 1.14 2000/06/14 13:12:52 thomas Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/advanced.sgml,v 1.15 2000/06/22 22:31:15 petere Exp $
 -->
 
  <chapter id="advanced">
@@ -116,22 +116,25 @@ SELECT name, altitude
     support this <quote>ONLY</quote> notation.
    </para>
 
-   <para>
-    Deprecated: In previous versions of postgres, the default was not to
-    get access to child classes. By experience this was found to be error
-    prone. Under the old syntax, to get the sub-classes you append "*"
-    to the table name. For example
-
-    <programlisting>
+   <note>
+    <title>Deprecated</title> 
+    <para>
+     In previous versions of <productname>Postgres</productname>, the
+     default was not to get access to child tables. This was found to
+     be error prone and is also in violation of SQL. Under the old
+     syntax, to get the sub-classes you append "*" to the table name.
+     For example
+<programlisting>
 SELECT * from cities*;
-    </programlisting>
-
-    This old behaviour is still available by using a SET command:
-
-    <programlisting>
-SET EXAMINE_SUBCLASS TO on;
-    </programlisting>     
-   </para>
+</programlisting>
+     To get the old behavior, the set configuration option
+     <literal>SQL_Inheritance</literal> to off, e.g.,
+<programlisting>
+SET SQL_Inheritance TO OFF;
+</programlisting>
+     or add a line in your <filename>postgresql.conf</filename> file.
+    </para>
+   </note>
   </sect1>
 
   <sect1>

doc/src/sgml/inherit.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/Attic/inherit.sgml,v 1.9 2000/06/14 13:12:52 thomas Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/Attic/inherit.sgml,v 1.10 2000/06/22 22:31:15 petere Exp $
 -->
 
  <chapter id="inherit">
@@ -96,19 +96,25 @@ CREATE TABLE capitals UNDER cities (
    <command>UPDATE</command> and <command>DELETE</command> --
    support this <quote>ONLY</quote> notation.
   </para>
-  <para>
-  Deprecated: In previous versions of postgres, the default was not to
-  get access to child classes. By experience this was found to be error
-  prone. Under the old syntax, to get the sub-classes you append "*"
-  to the table name. For example
-   <programlisting>
-   SELECT * from cities*;
-   </programlisting>     
-   This old behaviour is still available by using a SET command...    
-   <programlisting>
-   SET EXAMINE_SUBCLASS TO on;
-   </programlisting>     
-  </para>
+  <note>
+   <title>Deprecated</title> 
+   <para>
+    In previous versions of <productname>Postgres</productname>, the
+    default was not to get access to child tables. This was found to
+    be error prone and is also in violation of SQL. Under the old
+    syntax, to get the sub-classes you append "*" to the table name.
+    For example
+<programlisting>
+SELECT * from cities*;
+</programlisting>
+    To get the old behavior, the set configuration option
+    <literal>SQL_Inheritance</literal> to off, e.g.,
+<programlisting>
+SET SQL_Inheritance TO OFF;
+</programlisting>
+    or add a line in your <filename>postgresql.conf</filename> file.
+   </para>
+  </note>
  </chapter>
 
 <!-- Keep this comment at the end of the file

doc/src/sgml/ref/select.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/select.sgml,v 1.29 2000/06/09 01:44:00 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/select.sgml,v 1.30 2000/06/22 22:31:16 petere Exp $
 Postgres documentation
 -->
 
@@ -208,7 +208,7 @@ SELECT [ ALL | DISTINCT [ ON ( <replaceable class="PARAMETER">expression</replac
   This was previously the default result, and getting subclasses was
   obtained by appending <command>*</command> to the table name.
   The old behaviour is available via the command 
-  <command>SET EXAMINE_SUBCLASS TO 'on';</command>
+  <command>SET SQL_Inheritance TO OFF;</command>
   </para>
 
   <para>

doc/src/sgml/runtime.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.11 2000/06/18 21:24:51 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.12 2000/06/22 22:31:15 petere Exp $
 -->
 
 <Chapter Id="runtime">
@@ -914,6 +914,23 @@ env PGOPTIONS='--geqo=off' psql
        </para>
       </listitem>
      </varlistentry>
+
+     <varlistentry>
+      <term>SQL_INHERITANCE (<type>bool</type>)</term>
+      <listitem>
+       <para>
+        This controls the inheritance semantics, in particular whether
+        subtables are included into the consideration of various
+        commands by default. This was not the case in versions prior
+        to 7.1. If you need this behaviour you can set this variable
+        to off, but in the long run you are encouraged to change your
+        applications to use the <literal>ONLY</literal> keyword to
+        exclude subtables. See the SQL language reference and the
+        <citetitle>User's Guide</citetitle> for more information about
+        inheritance.
+       </para>
+      </listitem>
+     </varlistentry>
     </variablelist>
    </para>
    </sect2>