From 63cbee6a786028790abc6ae9b9606366bae5e01d Mon Sep 17 00:00:00 2001 From: Alvaro Herrera Date: Mon, 12 Mar 2018 13:28:52 -0300 Subject: doc: Reword restriction on partition keys in unique indexes New wording from David G. Johnston, who noticed the unreadable original also. Include his suggested test case as well. Fix a typo I noticed elsewhere while doing this. Discussion: https://postgr.es/m/CAKFQuwY4Ld7ecxL_KAmaxwt0FUu5VcPPN2L4dh+3BeYbrdBa5g@mail.gmail.com --- doc/src/sgml/ref/create_table.sgml | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 9e8e9d8f1cd..14a43b45e9a 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -791,11 +791,10 @@ WITH ( MODULUS numeric_literal, REM - When used on partitioned tables, unique constraints must include all the - columns of the partition key. - If any partitions are in turn partitioned, all columns of each partition - key are considered at each level below the UNIQUE - constraint. + When establishing a unique constraint for a multi-level partition + hierarchy, all the columns in the partition key of the target + partitioned table, as well as those of all its descendant partitioned + tables, must be included in the constraint definition. -- cgit v1.2.3