From: Bruce Momjian <bruce@momjian.us>
Date: Thu, 22 Sep 2005 23:47:44 +0000 (+0000)
Subject: Move table constraint patch up into the main new features section of the
X-Git-Tag: REL8_1_0BETA3~136
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=ec294fc6cbfa60f6ef259f36b05a5abc6e79b8c1;p=thirdparty%2Fpostgresql.git

Move table constraint patch up into the main new features section of the
release notes.
---

diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml
index 61d7a9ce2a4..10980a359df 100644
--- a/doc/src/sgml/release.sgml
+++ b/doc/src/sgml/release.sgml
@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.370 2005/09/22 23:24:58 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.371 2005/09/22 23:47:44 momjian Exp $
 
 Typical markup:
 
@@ -217,6 +217,27 @@ pg_[A-Za-z0-9_]                 <application>
       </listitem>
      </varlistentry>
 
+     <varlistentry>
+      <term>
+       Improve performance for partitioned tables (Simon)
+      </term>
+
+      <listitem>
+       <para>
+        The new <varname>constraint_exclusion</varname> configuration
+        parameter avoids lookups on child tables where constraints indicate
+        that no matching rows exist in the child table.
+       </para>
+       <para>
+        This allows for a basic type of table partitioning. If child tables
+        store separate key ranges and this is enforced using appropriate
+        <command>CHECK</> constraints, the optimizer will skip child
+        table accesses when the constraint guarantees no matching rows
+        exist in the child table.
+       </para>
+      </listitem>
+     </varlistentry>
+
     </variablelist>
    </sect2>
  
@@ -510,21 +531,6 @@ pg_[A-Za-z0-9_]                 <application>
        </para>
       </listitem>
 
-      <listitem>
-       <para>
-        Add <varname>constraint_exclusion</varname> configuration
-        parameter to restrict child table lookups based on table
-        constraints (Simon)
-       </para>
-       <para>
-        This allows for a basic type of table partitioning. If child tables
-        store separate key ranges and this is enforced using appropriate
-        <command>CHECK</> constraints, the optimizer will skip child
-        table accesses when the constraint guarantees no matching rows
-        exist in the child table.
-       </para>
-      </listitem>
-
       <listitem>
        <para>
         Use <literal>O_DIRECT</> if available when using