aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeFunctionscan.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2005-04-23 04:42:53 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2005-04-23 04:42:53 +0000
commit56c88772911b4e4c8fbb86d8687d95c3acd38a4f (patch)
treed6ce8d5fb75838b0ef40380709e72c1f99d29dd6 /src/backend/executor/nodeFunctionscan.c
parent25434e32cb1cf4e7c61a21482832ecc5b33e1f5a (diff)
downloadpostgresql-56c88772911b4e4c8fbb86d8687d95c3acd38a4f.tar.gz
postgresql-56c88772911b4e4c8fbb86d8687d95c3acd38a4f.zip
Turns out that my recent elimination of the 'redundant' flatten_andors()
code in prepqual.c had a small drawback: the flatten_andors code was able to cope with deeply nested AND/OR structures (like 10000 ORs in a row), whereas eval_const_expressions tends to recurse until it overruns the stack. Revise eval_const_expressions so that it doesn't choke on deeply nested ANDs or ORs.
Diffstat (limited to 'src/backend/executor/nodeFunctionscan.c')
0 files changed, 0 insertions, 0 deletions