@@ -841,7 +841,7 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM
841
841
or as a default partition by using <literal>DEFAULT</literal>.
842
842
For each index in the target table, a corresponding
843
843
one will be created in the attached table; or, if an equivalent
844
- index already exists, will be attached to the target table's index,
844
+ index already exists, it will be attached to the target table's index,
845
845
as if <command>ALTER INDEX ATTACH PARTITION</command> had been executed.
846
846
Note that if the existing table is a foreign table, it is currently not
847
847
allowed to attach the table as a partition of the target table if there
@@ -864,23 +864,24 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM
864
864
already exist.
865
865
If any of the <literal>CHECK</literal> constraints of the table being
866
866
attached is marked <literal>NO INHERIT</literal>, the command will fail;
867
- such a constraint must be recreated without the <literal>NO INHERIT</literal>
868
- clause.
867
+ such constraints must be recreated without the
868
+ <literal>NO INHERIT</literal> clause.
869
869
</para>
870
870
871
871
<para>
872
872
If the new partition is a regular table, a full table scan is performed
873
- to check that no existing row in the table violates the partition
874
- constraint. It is possible to avoid this scan by adding a valid
875
- <literal>CHECK</literal> constraint to the table that would allow only
876
- the rows satisfying the desired partition constraint before running this
877
- command. It will be determined using such a constraint that the table
878
- need not be scanned to validate the partition constraint. This does not
879
- work, however, if any of the partition keys is an expression and the
880
- partition does not accept <literal>NULL</literal> values. If attaching
881
- a list partition that will not accept <literal>NULL</literal> values,
882
- also add <literal>NOT NULL</literal> constraint to the partition key
883
- column, unless it's an expression.
873
+ to check that existing rows in the table do not violate the partition
874
+ constraint. It is possible to avoid this scan by adding a valid
875
+ <literal>CHECK</literal> constraint to the table that allows only
876
+ rows satisfying the desired partition constraint before running this
877
+ command. The <literal>CHECK</literal> constraint will be used to
878
+ determine that the table need not be scanned to validate the partition
879
+ constraint. This does not work, however, if any of the partition keys
880
+ is an expression and the partition does not accept
881
+ <literal>NULL</literal> values. If attaching a list partition that will
882
+ not accept <literal>NULL</literal> values, also add
883
+ <literal>NOT NULL</literal> constraint to the partition key column,
884
+ unless it's an expression.
884
885
</para>
885
886
886
887
<para>
0 commit comments