summaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistbuild.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2021-07-09 13:38:24 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2021-07-09 13:38:24 -0400
commitd23ac62afa646b7073a7f0db0a137308459a263b (patch)
tree46553e634f9d88fe207ea8ce0e5bf23ac494363b /src/backend/access/gist/gistbuild.c
parentd0a02bdb8c2576b5aa607f127320e444080bd579 (diff)
downloadpostgresql-d23ac62afa646b7073a7f0db0a137308459a263b.tar.gz
Avoid creating a RESULT RTE that's marked LATERAL.
Commit 7266d0997 added code to pull up simple constant function results, converting the RTE_FUNCTION RTE to a dummy RTE_RESULT RTE since it no longer need be scanned. But I forgot to clear the LATERAL flag if the RTE has it set. If the function reduced to a constant, it surely contains no lateral references so this simplification is logically OK. It's needed because various other places will Assert that RESULT RTEs aren't LATERAL. Per bug #17097 from Yaoguang Chen. Back-patch to v13 where the faulty code came in. Discussion: https://postgr.es/m/17097-3372ef9f798fc94f@postgresql.org
Diffstat (limited to 'src/backend/access/gist/gistbuild.c')
0 files changed, 0 insertions, 0 deletions