aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeFunctionscan.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2018-07-12 12:28:43 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2018-07-12 12:28:43 -0400
commitb4900835d63cf0c56ab97b7b666d6407d3d98c22 (patch)
tree3127c3696b1e900b8f43556c8a9a1aeb8b64032d /src/backend/executor/nodeFunctionscan.c
parent19648375cc307eb5849906c0ddef737ddacf141a (diff)
downloadpostgresql-b4900835d63cf0c56ab97b7b666d6407d3d98c22.tar.gz
postgresql-b4900835d63cf0c56ab97b7b666d6407d3d98c22.zip
Doc: minor improvement in pl/pgsql FETCH/MOVE documentation.
Explain that you can use any integer expression for the "count" in pl/pgsql's versions of FETCH/MOVE, unlike the SQL versions which only allow a constant. Remove the duplicate version of this para under MOVE. I don't see a good reason to maintain two identical paras when we just said that MOVE works exactly like FETCH. Per Pavel Stehule, though I didn't use his text. Discussion: https://postgr.es/m/CAFj8pRAcvSXcNdUGx43bOK1e3NNPbQny7neoTLN42af+8MYWEA@mail.gmail.com
Diffstat (limited to 'src/backend/executor/nodeFunctionscan.c')
0 files changed, 0 insertions, 0 deletions