diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2021-03-08 18:54:55 -0500 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2021-03-08 18:54:55 -0500 |
| commit | d4545dc19b8ea670bf62e06d22b0e4e6fcb45153 (patch) | |
| tree | 876687b611af2b5d936d260c796fc79012b3c6af /contrib/postgres_fdw/sql/postgres_fdw.sql | |
| parent | fed10d4eec79242688382d03ddca82007160ee6f (diff) | |
| download | postgresql-d4545dc19b8ea670bf62e06d22b0e4e6fcb45153.tar.gz postgresql-d4545dc19b8ea670bf62e06d22b0e4e6fcb45153.zip | |
Complain if a function-in-FROM returns a set when it shouldn't.
Throw a "function protocol violation" error if a function in FROM
tries to return a set though it wasn't marked proretset. Although
such cases work at the moment, it doesn't seem like something we
want to guarantee will keep working. Besides, there are other
negative consequences of not setting the proretset flag, such as
potentially bad plans.
No back-patch, since if there is any third-party code violating
this expectation, people wouldn't appreciate us breaking it in
a minor release.
Discussion: https://postgr.es/m/1636062.1615141782@sss.pgh.pa.us
Diffstat (limited to 'contrib/postgres_fdw/sql/postgres_fdw.sql')
0 files changed, 0 insertions, 0 deletions