summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorÁlvaro Herrera <alvherre@alvh.no-ip.org>2024-11-07 14:06:24 +0100
committerÁlvaro Herrera <alvherre@alvh.no-ip.org>2024-11-07 14:06:24 +0100
commitd291e819be0c21691e5acfe000738b47deaaf0c9 (patch)
tree2607991f937f68712f0bc91af73060d7203f23cd
parent19bf81c06a372a138215d25e9844e68ddde35313 (diff)
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
-rw-r--r--doc/src/sgml/ref/alter_table.sgml10
1 files changed, 4 insertions, 6 deletions
diff --git a/doc/src/sgml/ref/alter_table.sgml b/doc/src/sgml/ref/alter_table.sgml
index eee1f4bc771..2907afd790d 100644
--- a/doc/src/sgml/ref/alter_table.sgml
+++ b/doc/src/sgml/ref/alter_table.sgml
@@ -980,20 +980,18 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM
<para>
A partition using <literal>FOR VALUES</literal> uses same syntax for
<replaceable class="parameter">partition_bound_spec</replaceable> as
- <link linkend="sql-createtable"><command>CREATE TABLE</command></link>. The partition bound specification
+ <link linkend="sql-createtable"><command>CREATE TABLE</command></link>.
+ 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 <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>