From: Álvaro Herrera Date: Thu, 7 Nov 2024 13:06:24 +0000 (+0100) Subject: doc: Reword ALTER TABLE ATTACH restriction on NO INHERIT constraints X-Git-Tag: REL_12_21~17 X-Git-Url: http://git.postgresql.org/gitweb/?a=commitdiff_plain;h=477830c1cb94beeb0440629820ef916c59beabb6;p=postgresql.git 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.zody6mld7vkw@alvherre.pgsql --- diff --git a/doc/src/sgml/ref/alter_table.sgml b/doc/src/sgml/ref/alter_table.sgml index 39df9d374fb..882e15f04ca 100644 --- a/doc/src/sgml/ref/alter_table.sgml +++ b/doc/src/sgml/ref/alter_table.sgml @@ -901,15 +901,12 @@ WITH ( MODULUS numeric_literal, 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 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.