database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-05-17 06:41:24 +03:00
Code

Fix omission in partitioning limitation documentation

Browse Source 
UNIQUE and PRIMARY KEY constraints can be created on ONLY the
partitioned table.  We already had an example demonstrating that,
but forgot to mention it in the documentation of the limits of
partitioning.

Author: Laurenz Albe
Reviewed-By: shihao zhong, Shubham Khanna, Ashutosh Bapat
Backpatch-through: 12
Discussion: https://postgr.es/m/167299368731.659.16130012959616771853@wrigleys.postgresql.org
This commit is contained in:
Magnus Hagander 2024-01-11 14:27:10 +01:00
parent fb198942b3
commit 9a94e9ae7e
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/src/sgml/ddl.sgml
View File

@ -4150,7 +4150,9 @@ ALTER INDEX measurement_city_id_logdate_key
Using <literal>ONLY</literal> to add or drop a constraint on only Using <literal>ONLY</literal> to add or drop a constraint on only
the partitioned table is supported as long as there are no the partitioned table is supported as long as there are no
partitions. Once partitions exist, using <literal>ONLY</literal> partitions. Once partitions exist, using <literal>ONLY</literal>
will result in an error. Instead, constraints on the partitions will result in an error for any constraints other than
<literal>UNIQUE</literal> and <literal>PRIMARY KEY</literal>.
Instead, constraints on the partitions
themselves can be added and (if they are not present in the parent themselves can be added and (if they are not present in the parent
table) dropped. table) dropped.
</para> </para>