Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDavid Rowley2022-09-05 06:43:03 +0000
committerDavid Rowley2022-09-05 06:43:03 +0000
commit519be095f2bf7150fe7a36c4f5cd0c1825126427 (patch)
treeae89cf416183848333542762cf2ab8dc01e32cef /src/tools/pginclude/cpluspluscheck
parent2fe6b2a806f20f2dbf02c6e79783dbc2777a1840 (diff)
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
Diffstat (limited to 'src/tools/pginclude/cpluspluscheck')
0 files changed, 0 insertions, 0 deletions