diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2019-04-10 19:02:21 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2019-04-10 19:02:32 -0400 |
| commit | 930930c476634991d1fa9838b1e41801d024eebf (patch) | |
| tree | 18ce0786037d9f7102431ce5ba37e65a357431db | |
| parent | 036f7d3782e53573d2080e7d967fff375bc516b5 (diff) | |
| download | postgresql-930930c476634991d1fa9838b1e41801d024eebf.tar.gz postgresql-930930c476634991d1fa9838b1e41801d024eebf.zip | |
Fix backwards test in operator_precedence_warning logic.
Warnings about unary minus might have been wrong. It's a bit
surprising that nobody noticed yet ... probably the precedence-warning
feature hasn't really been used much in the field.
Rikard Falkeborn
Discussion: https://postgr.es/m/CADRDgG6fzA8A2oeygUw4=o7ywo4kvz26NxCSgpq22nMD73Bx4Q@mail.gmail.com
| -rw-r--r-- | src/backend/parser/parse_expr.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/parser/parse_expr.c b/src/backend/parser/parse_expr.c index 385e54a9b69..cd2338d659b 100644 --- a/src/backend/parser/parse_expr.c +++ b/src/backend/parser/parse_expr.c @@ -3154,7 +3154,7 @@ operator_precedence_group(Node *node, const char **nodename) *nodename = strVal(linitial(aexpr->name)); /* Ignore if op was always higher priority than IS-tests */ if (strcmp(*nodename, "+") == 0 || - strcmp(*nodename, "-")) + strcmp(*nodename, "-") == 0) group = 0; else group = PREC_GROUP_PREFIX_OP; |