postgres.git / summary / log / commit / refs

commit    18d51c0bb19097191182e57bc755c197ee6a4fc4
Author:   Magnus Hagander <magnus@hagander.net>
Date:     Thu Jan 11 13:27:10 2024 +0000
First released in: 17.0, 12.18, 13.14, 14.11, 15.6, 16.2

    Fix omission in partitioning limitation documentation
    
    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


 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 3a53b55ca41..08b8d3797ed 100644
--- a/doc/src/sgml/ddl.sgml
+++ b/doc/src/sgml/ddl.sgml
@@ -4144,7 +4144,9 @@ ALTER INDEX measurement_city_id_logdate_key
         Using <literal>ONLY</literal> to add or drop a constraint on only
         the partitioned table is supported as long as there are no
         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
         table) dropped.
        </para>


[parent: 469d836a90cc]