mirror/postgresql
2
0
Fork 0
mirror of https://git.postgresql.org/git/postgresql.git synced 2025-01-12 18:34:36 +08:00
Code Issues Packages Projects Releases Wiki Activity

Fix executor/README to reflect disallowing SRFs in UPDATE.

Browse Source 
The parenthetical comment here is obsoleted by commit a4c35ea1c.
Noted by Andres Freund.
This commit is contained in:
Tom Lane 2016-09-13 14:25:35 -04:00
parent a4c35ea1c2
commit fdc79e1909
1 changed files with 4 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
src/backend/executor/README
View File

@ -195,8 +195,7 @@ the entire row value in the join output row.
We disallow set-returning functions in the targetlist of SELECT FOR UPDATE, We disallow set-returning functions in the targetlist of SELECT FOR UPDATE,
so as to ensure that at most one tuple can be returned for any particular so as to ensure that at most one tuple can be returned for any particular
set of scan tuples. Otherwise we'd get duplicates due to the original set of scan tuples. Otherwise we'd get duplicates due to the original
query returning the same set of scan tuples multiple times. (Note: there query returning the same set of scan tuples multiple times. Likewise,
is no explicit prohibition on SRFs in UPDATE, but the net effect will be SRFs are disallowed in an UPDATE's targetlist. There, they would have the
that only the first result row of an SRF counts, because all subsequent effect of the same row being updated multiple times, which is not very
rows will result in attempts to re-update an already updated target row. useful --- and updates after the first would have no effect anyway.
This is historical behavior and seems not worth changing.)