diff options
| author | David Rowley <drowley@postgresql.org> | 2022-09-05 18:44:44 +1200 |
|---|---|---|
| committer | David Rowley <drowley@postgresql.org> | 2022-09-05 18:44:44 +1200 |
| commit | b70db6c83073b562a92aaba917aa787c46ea1b39 (patch) | |
| tree | 48dd55e30a9b1ed19de6febf6045c15f896549e7 | |
| parent | 0cc46c825135ff0feb17462398058fba00d88739 (diff) | |
| download | postgresql-b70db6c83073b562a92aaba917aa787c46ea1b39.tar.gz postgresql-b70db6c83073b562a92aaba917aa787c46ea1b39.zip | |
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
| -rw-r--r-- | doc/src/sgml/ddl.sgml | 13 |
1 files changed, 7 insertions, 6 deletions
diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml index 4ba45891cb6..1f7a352a66d 100644 --- a/doc/src/sgml/ddl.sgml +++ b/doc/src/sgml/ddl.sgml @@ -4055,12 +4055,13 @@ ALTER INDEX measurement_city_id_logdate_key <itemizedlist> <listitem> <para> - Unique constraints (and hence primary keys) on partitioned tables must - include all the partition key columns. This limitation exists because - the individual indexes making up the constraint can only directly - enforce uniqueness within their own partitions; therefore, the - partition structure itself must guarantee that there are not - duplicates in different partitions. + To create a unique or primary key constraint on a partitioned table, + the partition keys must not include any expressions or function calls + and the constraint's columns must include all of the partition key + columns. This limitation exists because the individual indexes making + up the constraint can only directly enforce uniqueness within their own + partitions; therefore, the partition structure itself must guarantee + that there are not duplicates in different partitions. </para> </listitem> |