aboutsummaryrefslogtreecommitdiff
path: root/src/backend/parser/parse_expr.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2008-08-26 02:16:31 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2008-08-26 02:16:31 +0000
commit6734182c169a1ecb74dd8495004e896ee4519adb (patch)
tree938ca54b31b0bfe010052740dfc53e79552eeeb5 /src/backend/parser/parse_expr.c
parent6741688b169acc5fbcc4f198b209e9f3177579c9 (diff)
downloadpostgresql-6734182c169a1ecb74dd8495004e896ee4519adb.tar.gz
postgresql-6734182c169a1ecb74dd8495004e896ee4519adb.zip
Teach eval_const_expressions() to simplify an ArrayCoerceExpr to a constant
when its input is constant and the element coercion function is immutable (or nonexistent, ie, binary-coercible case). This is an oversight in the 8.3 implementation of ArrayCoerceExpr, and its result is that certain cases involving IN or NOT IN with constants don't get optimized as they should be. Per experimentation with an example from Ow Mun Heng.
Diffstat (limited to 'src/backend/parser/parse_expr.c')
0 files changed, 0 insertions, 0 deletions