aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeSubqueryscan.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
commit93532dbb5d91280400d337197752f4f91f29349f (patch)
treecf6effeb8e032f3d9d887d3779ecc9df198c2644 /src/backend/executor/nodeSubqueryscan.c
parent11abea37d5d16e553a93fc96fd95421090d78fe0 (diff)
downloadpostgresql-93532dbb5d91280400d337197752f4f91f29349f.tar.gz
postgresql-93532dbb5d91280400d337197752f4f91f29349f.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/nodeSubqueryscan.c')
0 files changed, 0 insertions, 0 deletions