diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2021-07-09 13:38:24 -0400 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2021-07-09 13:38:24 -0400 |
commit | 9807b9aedc6e8b8a497db161b3d2d9f83648ea5b (patch) | |
tree | d2b1d162a20d8aee3874f9c6a14d0d931e1bb6cf /src/backend/utils/adt/numeric.c | |
parent | 55cccdfdf1ee63fd8e818c2aa885f4d357773adc (diff) | |
download | postgresql-9807b9aedc6e8b8a497db161b3d2d9f83648ea5b.tar.gz postgresql-9807b9aedc6e8b8a497db161b3d2d9f83648ea5b.zip |
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/utils/adt/numeric.c')
0 files changed, 0 insertions, 0 deletions