Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit b70db6c

Browse files
committed
Doc: clarify partitioned table limitations
Improve documentation regarding the limitations of unique and primary key constraints on partitioned tables. The existing documentation didn't make it clear that the constraint columns had to be present in the partition key as bare columns. The reader could be led to believe that it was ok to include the constraint columns as part of a function call's parameters or as part of an expression. Additionally, the documentation didn't mention anything about the fact that we disallow unique and primary key constraints if the partition keys contain *any* function calls or expressions, regardless of if the constraint columns appear as columns elsewhere in the partition key. The confusion here was highlighted by a report on the general mailing list by James Vanns. Discussion: https://postgr.es/m/CAH7vdhNF0EdYZz3GLpgE3RSJLwWLhEk7A_fiKS9dPBT3Dz_3eA@mail.gmail.com Discussion: https://postgr.es/m/CAApHDvoU-u9iTqKjteYRFfi+UNEk7dbSAcyxEQD==vZt9B1KnA@mail.gmail.com Reviewed-by: Erik Rijkers Backpatch-through: 11
1 parent 0cc46c8 commit b70db6c

File tree

1 file changed

+7
-6
lines changed

1 file changed

+7
-6
lines changed

doc/src/sgml/ddl.sgml

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -4055,12 +4055,13 @@ ALTER INDEX measurement_city_id_logdate_key
40554055
<itemizedlist>
40564056
<listitem>
40574057
<para>
4058-
Unique constraints (and hence primary keys) on partitioned tables must
4059-
include all the partition key columns. This limitation exists because
4060-
the individual indexes making up the constraint can only directly
4061-
enforce uniqueness within their own partitions; therefore, the
4062-
partition structure itself must guarantee that there are not
4063-
duplicates in different partitions.
4058+
To create a unique or primary key constraint on a partitioned table,
4059+
the partition keys must not include any expressions or function calls
4060+
and the constraint's columns must include all of the partition key
4061+
columns. This limitation exists because the individual indexes making
4062+
up the constraint can only directly enforce uniqueness within their own
4063+
partitions; therefore, the partition structure itself must guarantee
4064+
that there are not duplicates in different partitions.
40644065
</para>
40654066
</listitem>
40664067

0 commit comments

Comments
 (0)