Revision 6ce4c4d83101886e0a9fea026faa3480a572bc84 authored by David Rowley on 05 September 2022, 06:43:36 UTC, committed by David Rowley on 05 September 2022, 06:43:36 UTC
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 46b588a
File | Mode | Size |
---|---|---|
src | ||
KNOWN_BUGS | -rw-r--r-- | 163 bytes |
MISSING_FEATURES | -rw-r--r-- | 163 bytes |
Makefile | -rw-r--r-- | 469 bytes |
TODO | -rw-r--r-- | 76 bytes |
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...