doc: Reword ALTER TABLE ATTACH restriction on NO INHERIT constraints

The previous wording is easy to read incorrectly; this change makes it
simpler, less ambiguous, and less prominent.

Backpatch to all live branches.

Reviewed-by: Amit Langote 
Discussion: https://postgr.es/m/202411051201[email protected]

diff --git a/doc/src/sgml/ref/alter_table.sgml b/doc/src/sgml/ref/alter_table.sgml
index 1a49f321cf702c9ca0352dd427049731f2f2d557..c6ab432df1483d3bf3865646125f55616a045a35 100644 (file)
--- a/doc/src/sgml/ref/alter_table.sgml
+++ b/doc/src/sgml/ref/alter_table.sgml
@@ -1010,20 +1010,18 @@ WITH ( MODULUS numeric_literal, REM
      
       A partition using FOR VALUES uses same syntax for
       partition_bound_spec as
-      CREATE TABLE.  The partition bound specification
+      CREATE TABLE.
+      The partition bound specification
       must correspond to the partitioning strategy and partition key of the
       target table.  The table to be attached must have all the same columns
       as the target table and no more; moreover, the column types must also
       match.  Also, it must have all the NOT NULL and
-      CHECK constraints of the target table.  Currently
+      CHECK constraints of the target table, not marked
+      NO INHERIT.  Currently
       FOREIGN KEY constraints are not considered.
       UNIQUE and PRIMARY KEY constraints
       from the parent table will be created in the partition, if they don't
       already exist.
-      If any of the CHECK constraints of the table being
-      attached are marked NO INHERIT, the command will fail;
-      such constraints must be recreated without the
-      NO INHERIT clause.