diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2016-06-03 19:12:29 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2016-06-03 19:12:29 -0400 |
| commit | 05104f693646c0a4ae446e79cb89057497da17e4 (patch) | |
| tree | 6f039d998a0bd5da74a354a91b91ade10133a72b /src/backend/executor/nodeModifyTable.c | |
| parent | d50183c5786a21910bac566d2987f955c7bc1d62 (diff) | |
| download | postgresql-05104f693646c0a4ae446e79cb89057497da17e4.tar.gz postgresql-05104f693646c0a4ae446e79cb89057497da17e4.zip | |
Fix grammar's AND/OR flattening to work with operator_precedence_warning.
It'd be good for "(x AND y) AND z" to produce a three-child AND node
whether or not operator_precedence_warning is on, but that failed to
happen when it's on because makeAndExpr() didn't look through the added
AEXPR_PAREN node. This has no effect on generated plans because prepqual.c
would flatten the AND nest anyway; but it does affect the number of parens
printed in ruleutils.c, for example. I'd already fixed some similar
hazards in parse_expr.c in commit abb164655, but didn't think to search
gram.y for problems of this ilk. Per gripe from Jean-Pierre Pelletier.
Report: <fa0535ec6d6428cfec40c7e8a6d11156@mail.gmail.com>
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions