mirror of
https://github.com/postgres/postgres.git
synced 2025-04-22 23:02:54 +03:00
Move table constraint patch up into the main new features section of the
release notes.
This commit is contained in:
parent
d7e4fd99e5
commit
ec294fc6cb
@ -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:
|
Typical markup:
|
||||||
|
|
||||||
@ -217,6 +217,27 @@ pg_[A-Za-z0-9_] <application>
|
|||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</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>
|
</variablelist>
|
||||||
</sect2>
|
</sect2>
|
||||||
|
|
||||||
@ -510,21 +531,6 @@ pg_[A-Za-z0-9_] <application>
|
|||||||
</para>
|
</para>
|
||||||
</listitem>
|
</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>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Use <literal>O_DIRECT</> if available when using
|
Use <literal>O_DIRECT</> if available when using
|
||||||
|
Loading…
x
Reference in New Issue
Block a user