aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeProjectSet.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2018-12-07 16:40:58 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2018-12-07 16:40:58 -0500
commit1f66c657f2b4eb55c68593d5c14256115aa6a0ea (patch)
tree676ddb2c22016dc429747e71161ffc0b5e3c45e3 /src/backend/executor/nodeProjectSet.c
parent1464755fc490a9911214817fe83077a3689250ab (diff)
downloadpostgresql-1f66c657f2b4eb55c68593d5c14256115aa6a0ea.tar.gz
postgresql-1f66c657f2b4eb55c68593d5c14256115aa6a0ea.zip
Doc: document that we expect CHECK constraint conditions to be immutable.
This restriction is implicit in the check-only-once implementation we use for table and domain constraints, but it wasn't spelled out anywhere, nor was there any advice about how to alter a constraint's behavior safely. Improve that. I was also dissatisfied with the documentation of ALTER DOMAIN VALIDATE CONSTRAINT, which entirely failed to explain the use of that feature; and thence decided that ALTER TABLE VALIDATE CONSTRAINT could be documented better as well. Perhaps we should back-patch this, along with the related commit 36d442a25, but for now I refrained. Discussion: https://postgr.es/m/12539.1544107316@sss.pgh.pa.us
Diffstat (limited to 'src/backend/executor/nodeProjectSet.c')
0 files changed, 0 insertions, 0 deletions