aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeModifyTable.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2017-01-18 18:10:23 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2017-01-18 18:10:23 -0500
commitf13a1277aa2df301583c6db9c2989d2e9d7f6483 (patch)
tree20bb69b2456b5c7a6d3f9f5bf768fa70499d5b0d /src/backend/executor/nodeModifyTable.c
parent69f4b9c85f168ae006929eec44fc44d569e846b9 (diff)
downloadpostgresql-f13a1277aa2df301583c6db9c2989d2e9d7f6483.tar.gz
postgresql-f13a1277aa2df301583c6db9c2989d2e9d7f6483.zip
Doc: improve documentation of new SRF-in-tlist behavior.
Correct a misstatement about how things used to work: we did allow nested SRFs before, as long as no function had more than one set-returning input. Also, attempt to document the fact that the new implementation changes the behavior for SRFs within conditional constructs (eg CASE): the conditional construct no longer gates whether the SRF is run, and thus cannot affect the number of rows emitted. We might want to change this behavior, but first it behooves us to see if we can explain it. Minor other wordsmithing on what I wrote yesterday, too. Discussion: https://postgr.es/m/20170118214702.54b2mdbxce5piwv5@alap3.anarazel.de
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions