aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/xml.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2014-02-21 17:10:46 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2014-02-21 17:10:46 -0500
commit77585bce03042e8fee62d8df0dde9c008a904699 (patch)
treea379fbf445a39b335d999714f46d794837cf634d /src/backend/utils/adt/xml.c
parent0c5783ff301ae3e470000c918bfc2395129de4c5 (diff)
downloadpostgresql-77585bce03042e8fee62d8df0dde9c008a904699.tar.gz
postgresql-77585bce03042e8fee62d8df0dde9c008a904699.zip
Do ScalarArrayOp estimation correctly when array is a stable expression.
Most estimation functions apply estimate_expression_value to see if they can reduce an expression to a constant; the key difference is that it allows evaluation of stable as well as immutable functions in hopes of ending up with a simple Const node. scalararraysel didn't get the memo though, and neither did gincost_opexpr/gincost_scalararrayopexpr. Fix that, and remove a now-unnecessary estimate_expression_value step in the subsidiary function scalararraysel_containment. Per complaint from Alexey Klyukin. Back-patch to 9.3. The problem goes back further, but I'm hesitant to change estimation behavior in long-stable release branches.
Diffstat (limited to 'src/backend/utils/adt/xml.c')
0 files changed, 0 insertions, 0 deletions