@@ -857,7 +857,7 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM
857
857
or as a default partition by using <literal>DEFAULT</literal>.
858
858
For each index in the target table, a corresponding
859
859
one will be created in the attached table; or, if an equivalent
860
- index already exists, will be attached to the target table's index,
860
+ index already exists,it will be attached to the target table's index,
861
861
as if <command>ALTER INDEX ATTACH PARTITION</command> had been executed.
862
862
Note that if the existing table is a foreign table, it is currently not
863
863
allowed to attach the table as a partition of the target table if there
@@ -880,23 +880,24 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM
880
880
already exist.
881
881
If any of the <literal>CHECK</literal> constraints of the table being
882
882
attached is marked <literal>NO INHERIT</literal>, the command will fail;
883
- sucha constraint must be recreated without the <literal>NO INHERIT</literal>
884
- clause.
883
+ suchconstraints must be recreated without the
884
+ <literal>NO INHERIT</literal> clause.
885
885
</para>
886
886
887
887
<para>
888
888
If the new partition is a regular table, a full table scan is performed
889
- to check that no existing row in the table violates the partition
890
- constraint. It is possible to avoid this scan by adding a valid
891
- <literal>CHECK</literal> constraint to the table that would allow only
892
- the rows satisfying the desired partition constraint before running this
893
- command. It will be determined using such a constraint that the table
894
- need not be scanned to validate the partition constraint. This does not
895
- work, however, if any of the partition keys is an expression and the
896
- partition does not accept <literal>NULL</literal> values. If attaching
897
- a list partition that will not accept <literal>NULL</literal> values,
898
- also add <literal>NOT NULL</literal> constraint to the partition key
899
- column, unless it's an expression.
889
+ to check that existing rows in the table do not violate the partition
890
+ constraint. It is possible to avoid this scan by adding a valid
891
+ <literal>CHECK</literal> constraint to the table that allows only
892
+ rows satisfying the desired partition constraint before running this
893
+ command. The <literal>CHECK</literal> constraint will be used to
894
+ determine that the table need not be scanned to validate the partition
895
+ constraint. This does not work, however, if any of the partition keys
896
+ is an expression and the partition does not accept
897
+ <literal>NULL</literal> values. If attaching a list partition that will
898
+ not accept <literal>NULL</literal> values, also add
899
+ <literal>NOT NULL</literal> constraint to the partition key column,
900
+ unless it's an expression.
900
901
</para>
901
902
902
903
<para>