aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gist.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2017-12-22 12:08:34 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2017-12-22 12:08:34 -0500
commita84e90bb249d3ece4041f46651b4de566b7f6684 (patch)
treeaf9918c0b5eeee19432b46c990a0211a444a106b /src/backend/access/gist/gist.c
parent195516c9a6d72603969597bb0e495dd269e1ce22 (diff)
downloadpostgresql-a84e90bb249d3ece4041f46651b4de566b7f6684.tar.gz
postgresql-a84e90bb249d3ece4041f46651b4de566b7f6684.zip
Disallow UNION/INTERSECT/EXCEPT over no columns.
Since 9.4, we've allowed the syntax "select union select" and variants of that. However, the planner wasn't expecting a no-column set operation and ended up treating the set operation as if it were UNION ALL. Pre-v10, there seem to be some executor issues that would need to be fixed to support such cases, and it doesn't really seem worth expending much effort on. Just disallow it, instead. Per report from Victor Yegorov. Discussion: https://postgr.es/m/CAGnEbojGJrRSOgJwNGM7JSJZpVAf8xXcVPbVrGdhbVEHZ-BUMw@mail.gmail.com
Diffstat (limited to 'src/backend/access/gist/gist.c')
0 files changed, 0 insertions, 0 deletions