From 5a0f480e8ebf26be8dd84ca76dd9217bb7eea860 Mon Sep 17 00:00:00 2001 From: Laurenz Albe Date: Mon, 4 Dec 2023 21:07:19 +0100 Subject: [PATCH] Doc: Fix omission in partitioning limitations 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 Discussion: https://postgr.es/m/167299368731.659.16130012959616771853@wrigleys.postgresql.org --- doc/src/sgml/ddl.sgml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml index 4490e82aa5..922766ef1c 100644 --- a/doc/src/sgml/ddl.sgml +++ b/doc/src/sgml/ddl.sgml @@ -4341,7 +4341,9 @@ ALTER INDEX measurement_city_id_logdate_key Using ONLY to add or drop a constraint on only the partitioned table is supported as long as there are no partitions. Once partitions exist, using ONLY - will result in an error. Instead, constraints on the partitions + will result in an error (unless you use ONLY to + create UNIQUE and PRIMARY KEY + constraints as shown above). Instead, constraints on the partitions themselves can be added and (if they are not present in the parent table) dropped. -- 2.43.0