pgsql: Fix unexpected side-effects of operator_precedence_warning.
pgsql: Fix unexpected side-effects of operator_precedence_warning.
От:
Tom Lane <tgl@sss.pgh.pa.us>
Дата:
Fix unexpected side-effects of operator_precedence_warning. The implementation of that feature involves injecting nodes into the raw parsetree where explicit parentheses appear. Various places in parse_expr.c that test to see "is this child node of type Foo" need to look through such nodes, else we'll get different behavior when operator_precedence_warning is on than when it is off. Note that we only need to handle this when testing untransformed child nodes, since the AEXPR_PAREN nodes will be gone anyway after transformExprRecurse. Per report from Scott Ribe and additional code-reading. Back-patch to 9.5 where this feature was added. Report: Branch ------ master Details ------- http://git.postgresql.org/pg/commitdiff/abb164655c703a5013b7fcf83f855a071895dc91 Modified Files -------------- src/backend/parser/parse_expr.c | 34 +++++++++++++++++++++++++++++----- 1 file changed, 29 insertions(+), 5 deletions(-)