mirror of
https://github.com/postgres/postgres.git
synced 2025-04-24 10:47:04 +03:00
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
This commit is contained in:
parent
0b022ddf3e
commit
344ac149cf
@ -948,20 +948,18 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM
|
|||||||
<para>
|
<para>
|
||||||
A partition using <literal>FOR VALUES</literal> uses same syntax for
|
A partition using <literal>FOR VALUES</literal> uses same syntax for
|
||||||
<replaceable class="parameter">partition_bound_spec</replaceable> as
|
<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
|
must correspond to the partitioning strategy and partition key of the
|
||||||
target table. The table to be attached must have all the same columns
|
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
|
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
|
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>FOREIGN KEY</literal> constraints are not considered.
|
||||||
<literal>UNIQUE</literal> and <literal>PRIMARY KEY</literal> constraints
|
<literal>UNIQUE</literal> and <literal>PRIMARY KEY</literal> constraints
|
||||||
from the parent table will be created in the partition, if they don't
|
from the parent table will be created in the partition, if they don't
|
||||||
already exist.
|
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>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
|
Loading…
x
Reference in New Issue
Block a user