doc: Reword ALTER TABLE ATTACH restriction on NO INHERIT constraints
authorÁlvaro Herrera <[email protected]>
Thu, 7 Nov 2024 13:06:24 +0000 (14:06 +0100)
committerÁlvaro Herrera <[email protected]>
Thu, 7 Nov 2024 13:06:24 +0000 (14:06 +0100)
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 <[email protected]>
Discussion: https://postgr.es/m/202411051201[email protected]

doc/src/sgml/ref/alter_table.sgml

index 39df9d374fb4c11817bc74b423b5089fec1f037d..882e15f04cacf918970bec4f54b46e6d1487ca2a 100644 (file)
@@ -901,15 +901,12 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM
       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 <literal>NOT NULL</literal> and
-      <literal>CHECK</literal> constraints of the target table.  Currently
+      <literal>CHECK</literal> constraints of the target table, not marked
+      <literal>NO INHERIT</literal>.  Currently
       <literal>FOREIGN KEY</literal> constraints are not considered.
       <literal>UNIQUE</literal> and <literal>PRIMARY KEY</literal> constraints
       from the parent table will be created in the partition, if they don't
       already exist.
-      If any of the <literal>CHECK</literal> constraints of the table being
-      attached are marked <literal>NO INHERIT</literal>, the command will fail;
-      such constraints must be recreated without the
-      <literal>NO INHERIT</literal> clause.
      </para>
 
      <para>