aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeFunctionscan.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2022-12-22 10:35:02 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2022-12-22 10:35:02 -0500
commit1a3daa5bb2e0ec10dd6cee38d120a52bed9213e0 (patch)
treeab678f03a1cf42f6192233593a3a6273bb05d7ae /src/backend/executor/nodeFunctionscan.c
parentb87037b373cf5605e6755e50c62348337a0d32c8 (diff)
downloadpostgresql-1a3daa5bb2e0ec10dd6cee38d120a52bed9213e0.tar.gz
postgresql-1a3daa5bb2e0ec10dd6cee38d120a52bed9213e0.zip
Add some recursion and looping defenses in prepjointree.c.
Andrey Lepikhov demonstrated a case where we spend an unreasonable amount of time in pull_up_subqueries(). Not only is that recursing with no explicit check for stack overrun, but the code seems not interruptable by control-C. Let's stick a CHECK_FOR_INTERRUPTS there, along with sprinkling some stack depth checks. An actual fix for the excessive time consumption seems a bit risky to back-patch; but this isn't, so let's do so. Discussion: https://postgr.es/m/703c09a2-08f3-d2ec-b33d-dbecd62428b8@postgrespro.ru
Diffstat (limited to 'src/backend/executor/nodeFunctionscan.c')
0 files changed, 0 insertions, 0 deletions