postgres.git / summary / log / commit / refs

commit    f534e38914eb89b86fca8294c03d21ff72fd0719
Author:   Álvaro Herrera <alvherre@alvh.no-ip.org>
Date:     Thu Nov 07 13:06:24 2024 +0000
First released in: 18.0, 12.21, 13.17, 14.14, 15.9, 16.5, 17.1

    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 <amitlangote09@gmail.com>
    Discussion: https://postgr.es/m/202411051201.zody6mld7vkw@alvherre.pgsql


 doc/src/sgml/ref/alter_table.sgml | 7 ++-----
 1 file changed, 2 insertions(+), 5 deletions(-)

diff --git a/doc/src/sgml/ref/alter_table.sgml b/doc/src/sgml/ref/alter_table.sgml
index 0e5fdb8cff5..c888b57eb43 100644
--- a/doc/src/sgml/ref/alter_table.sgml
+++ b/doc/src/sgml/ref/alter_table.sgml
@@ -922,15 +922,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>


[parent: e88d824a4127]