Move table constraint patch up into the main new features section of the

release notes.
This commit is contained in:
Bruce Momjian 2005-09-22 23:47:44 +00:00
parent d7e4fd99e5
commit ec294fc6cb

View file

@ -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