diff --git a/doc/src/sgml/ref/alter_table.sgml b/doc/src/sgml/ref/alter_table.sgml
index 8b251f9..5e3cd4d 100644
--- a/doc/src/sgml/ref/alter_table.sgml
+++ b/doc/src/sgml/ref/alter_table.sgml
@@ -743,18 +743,25 @@ ALTER TABLE [ IF EXISTS ] name
- A full table scan is performed on the table being attached to check that
- no existing row in the table violates the partition constraint. It is
- possible to avoid this scan by adding a valid CHECK
- constraint to the table that would allow only the rows satisfying the
- desired partition constraint before running this command. It will be
- determined using such a constraint that the table need not be scanned
- to validate the partition constraint. This does not work, however, if
- any of the partition keys is an expression and the partition does not
- accept NULL values. If attaching a list partition
- that will not accept NULL values, also add
- NOT NULL constraint to the partition key column,
- unless it's an expression.
+ If the table being attached is a regular table, A full table scan is
+ performed on the table being attached to check that no existing row in
+ the table violates the partition constraint. It is possible to avoid
+ this scan by adding a valid CHECK constraint to the
+ table that would allow only the rows satisfying the desired partition
+ constraint before running this command. It will be determined using such
+ a constraint that the table need not be scanned to validate the partition
+ constraint. This does not work, however, if any of the partition keys is
+ an expression and the partition does not accept NULL
+ values. If attaching a list partition that will not accept
+ NULL values, also add NOT NULL
+ constraint to the partition key column, unless it's an expression.
+
+
+
+ If the table being attached is a foreign table, nothing is done to verify
+ that all the rows in the foreign table obey the partition constraint.
+ (See the discussion in about
+ constraints on the foreign table.)