Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 150328c

Browse files
committed
I noticed that the Partitioning section of the docs has *two* sections
of caveats in different places, but close together. One called caveats, one not. That looks like it just led to somebody not reading some appropriate caveats in the second group of caveats (on -admin). Simon Riggs
1 parent 414c7a5 commit 150328c

File tree

1 file changed

+32
-32
lines changed

1 file changed

+32
-32
lines changed

doc/src/sgml/ddl.sgml

Lines changed: 32 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/ddl.sgml,v 1.67 2006/10/23 18:10:30 petere Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/ddl.sgml,v 1.68 2006/11/21 03:44:55 momjian Exp $ -->
22

33
<chapter id="ddl">
44
<title>Data Definition</title>
@@ -2657,36 +2657,6 @@ ALTER TABLE measurement_y2006m02 INHERIT measurement;
26572657
</para>
26582658
</sect2>
26592659

2660-
<sect2 id="ddl-partitioning-caveats">
2661-
<title>Caveats</title>
2662-
2663-
<para>
2664-
The following caveats apply to partitioned tables:
2665-
<itemizedlist>
2666-
<listitem>
2667-
<para>
2668-
There is currently no way to verify that all of the
2669-
<literal>CHECK</literal> constraints are mutually
2670-
exclusive. Care is required by the database designer.
2671-
</para>
2672-
</listitem>
2673-
2674-
<listitem>
2675-
<para>
2676-
There is currently no simple way to specify that rows must not be
2677-
inserted into the master table. A <literal>CHECK (false)</literal>
2678-
constraint on the master table would be inherited by all child
2679-
tables, so that cannot be used for this purpose. One possibility is
2680-
to set up an <literal>ON INSERT</> trigger on the master table that
2681-
always raises an error. (Alternatively, such a trigger could be
2682-
used to redirect the data into the proper child table, instead of
2683-
using a set of rules as suggested above.)
2684-
</para>
2685-
</listitem>
2686-
</itemizedlist>
2687-
</para>
2688-
</sect2>
2689-
26902660
<sect2 id="ddl-partitioning-constraint-exclusion">
26912661
<title>Partitioning and Constraint Exclusion</title>
26922662

@@ -2768,9 +2738,39 @@ EXPLAIN SELECT count(*) FROM measurement WHERE logdate &gt;= DATE '2006-01-01';
27682738
a large part of the partition or just a small part. An index will
27692739
be helpful in the latter case but not the former.
27702740
</para>
2741+
</sect2>
2742+
2743+
<sect2 id="ddl-partitioning-caveats">
2744+
<title>Caveats</title>
2745+
2746+
<para>
2747+
The following caveats apply to partitioned tables:
2748+
<itemizedlist>
2749+
<listitem>
2750+
<para>
2751+
There is currently no way to verify that all of the
2752+
<literal>CHECK</literal> constraints are mutually
2753+
exclusive. Care is required by the database designer.
2754+
</para>
2755+
</listitem>
2756+
2757+
<listitem>
2758+
<para>
2759+
There is currently no simple way to specify that rows must not be
2760+
inserted into the master table. A <literal>CHECK (false)</literal>
2761+
constraint on the master table would be inherited by all child
2762+
tables, so that cannot be used for this purpose. One possibility is
2763+
to set up an <literal>ON INSERT</> trigger on the master table that
2764+
always raises an error. (Alternatively, such a trigger could be
2765+
used to redirect the data into the proper child table, instead of
2766+
using a set of rules as suggested above.)
2767+
</para>
2768+
</listitem>
2769+
</itemizedlist>
2770+
</para>
27712771

27722772
<para>
2773-
The following caveats apply:
2773+
The following caveats apply to constraint exclusion:
27742774

27752775
<itemizedlist>
27762776
<listitem>

0 commit comments

Comments
 (0)