|
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 $ --> |
2 | 2 |
|
3 | 3 | <chapter id="ddl">
|
4 | 4 | <title>Data Definition</title>
|
@@ -2657,36 +2657,6 @@ ALTER TABLE measurement_y2006m02 INHERIT measurement;
|
2657 | 2657 | </para>
|
2658 | 2658 | </sect2>
|
2659 | 2659 |
|
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 |
| - |
2690 | 2660 | <sect2 id="ddl-partitioning-constraint-exclusion">
|
2691 | 2661 | <title>Partitioning and Constraint Exclusion</title>
|
2692 | 2662 |
|
@@ -2768,9 +2738,39 @@ EXPLAIN SELECT count(*) FROM measurement WHERE logdate >= DATE '2006-01-01';
|
2768 | 2738 | a large part of the partition or just a small part. An index will
|
2769 | 2739 | be helpful in the latter case but not the former.
|
2770 | 2740 | </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> |
2771 | 2771 |
|
2772 | 2772 | <para>
|
2773 |
| - The following caveats apply: |
| 2773 | + The following caveats apply to constraint exclusion: |
2774 | 2774 |
|
2775 | 2775 | <itemizedlist>
|
2776 | 2776 | <listitem>
|
|
0 commit comments