Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commitaf36f19

Browse files
committed
Fix omission in partitioning limitation documentation
UNIQUE and PRIMARY KEY constraints can be created on ONLY thepartitioned table. We already had an example demonstrating that,but forgot to mention it in the documentation of the limits ofpartitioning.Author: Laurenz AlbeReviewed-By: shihao zhong, Shubham Khanna, Ashutosh BapatBackpatch-through: 12Discussion:https://postgr.es/m/167299368731.659.16130012959616771853@wrigleys.postgresql.org
1 parentba33775 commitaf36f19

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

‎doc/src/sgml/ddl.sgml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4299,7 +4299,9 @@ ALTER INDEX measurement_city_id_logdate_key
42994299
Using <literal>ONLY</literal> to add or drop a constraint on only
43004300
the partitioned table is supported as long as there are no
43014301
partitions. Once partitions exist, using <literal>ONLY</literal>
4302-
will result in an error. Instead, constraints on the partitions
4302+
will result in an error for any constraints other than
4303+
<literal>UNIQUE</literal> and <literal>PRIMARY KEY</literal>.
4304+
Instead, constraints on the partitions
43034305
themselves can be added and (if they are not present in the parent
43044306
table) dropped.
43054307
</para>

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp