aboutsummaryrefslogtreecommitdiff
path: root/contrib/postgres_fdw/postgres_fdw.c
diff options
context:
space:
mode:
authorDavid Rowley <drowley@postgresql.org>2022-09-05 18:43:36 +1200
committerDavid Rowley <drowley@postgresql.org>2022-09-05 18:43:36 +1200
commit6ce4c4d83101886e0a9fea026faa3480a572bc84 (patch)
treef1fd322b977de535d18f2efebd2e0ac999f3dbef /contrib/postgres_fdw/postgres_fdw.c
parent46b588afcdc6891bb0972bdeb6bc36bad5c01033 (diff)
downloadpostgresql-6ce4c4d83101886e0a9fea026faa3480a572bc84.tar.gz
postgresql-6ce4c4d83101886e0a9fea026faa3480a572bc84.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
Diffstat (limited to 'contrib/postgres_fdw/postgres_fdw.c')
0 files changed, 0 insertions, 0 deletions