diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml
index 4c1d2f607bb..110f6b46570 100644
--- a/doc/src/sgml/ddl.sgml
+++ b/doc/src/sgml/ddl.sgml
@@ -3856,27 +3856,6 @@ ALTER TABLE measurement ATTACH PARTITION measurement_y2008m02
-
-
- When an UPDATE causes a row to move from one
- partition to another, there is a chance that another concurrent
- UPDATE or DELETE will get a
- serialization failure error. Suppose session 1 is performing an
- UPDATE on a partition key, and meanwhile a concurrent
- session 2 for which this row is visible performs an
- UPDATE or DELETE operation on this
- row. In such case, session 2's UPDATE or
- DELETE, will detect the row movement and raise a
- serialization failure error (which always returns with an SQLSTATE code
- '40001'). Applications may wish to retry the transaction if this
- occurs. In the usual case where the table is not partitioned, or where
- there is no row movement, session 2 would have identified the newly
- updated row and carried out the
- UPDATE/DELETE on this new row
- version.
-
-
-
BEFORE ROW triggers, if necessary, must be defined
diff --git a/doc/src/sgml/ref/create_foreign_table.sgml b/doc/src/sgml/ref/create_foreign_table.sgml
index 37a45b26dbc..19eb5341e7d 100644
--- a/doc/src/sgml/ref/create_foreign_table.sgml
+++ b/doc/src/sgml/ref/create_foreign_table.sgml
@@ -160,6 +160,18 @@ CHECK ( expression ) [ NO INHERIT ]
+
+ PARTITION OF parent_table FOR VALUES partition_bound_spec
+
+
+ This form can be used to create the foreign table as partition of
+ the given parent table with specified partition bound values.
+ See the similar form of
+ for more details.
+
+
+
+
CONSTRAINT constraint_name
@@ -308,6 +320,12 @@ CHECK ( expression ) [ NO INHERIT ]
responsibility to ensure that the constraint definition matches
reality.
+
+
+ While rows can be moved from local partitions to a foreign-table partition
+ (provided the foreign data wrapper supports tuple routing), they cannot be
+ moved from a foreign-table partition to another partition.
+
diff --git a/doc/src/sgml/ref/update.sgml b/doc/src/sgml/ref/update.sgml
index 77430a586cb..f58dcd8877b 100644
--- a/doc/src/sgml/ref/update.sgml
+++ b/doc/src/sgml/ref/update.sgml
@@ -287,13 +287,30 @@ UPDATE count
row satisfies its partition constraint, then the row is moved to that
partition. If there is no such partition, an error will occur. Behind the
scenes, the row movement is actually a DELETE and
- INSERT operation. However, there is a possibility that a
- concurrent UPDATE or DELETE on the
- same row may miss this row. For details see the section
- .
- Currently, rows cannot be moved from a partition that is a
- foreign table to some other partition, but they can be moved into a foreign
- table if the foreign data wrapper supports it.
+ INSERT operation.
+
+
+
+ There is a possibility that a concurrent UPDATE or
+ DELETE on the row being moved will get a serialization
+ failure error. Suppose session 1 is performing an UPDATE
+ on a partition key, and meanwhile a concurrent session 2 for which this
+ row is visible performs an UPDATE or
+ DELETE operation on this row. In such case,
+ session 2's UPDATE or DELETE will
+ detect the row movement and raise a serialization failure error (which
+ always returns with an SQLSTATE code '40001'). Applications may wish to
+ retry the transaction if this occurs. In the usual case where the table
+ is not partitioned, or where there is no row movement, session 2 would
+ have identified the newly updated row and carried out the
+ UPDATE/DELETE on this new row
+ version.
+
+
+
+ Note that while rows can be moved from local partitions to a foreign-table
+ partition (provided the foreign data wrapper supports tuple routing), they
+ cannot be moved from a foreign-table partition to another partition.