aboutsummaryrefslogtreecommitdiff
path: root/src/backend/parser/parse_expr.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2019-04-10 19:02:21 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2019-04-10 19:02:21 -0400
commit4cae471d1b6bec7493dcb2ca156382bef738f293 (patch)
treeebfdfddae05a736bba92eb21b758b0e6564923c1 /src/backend/parser/parse_expr.c
parent765525c8c2c6e55abe8c0cd43bf5c728926d76d4 (diff)
downloadpostgresql-4cae471d1b6bec7493dcb2ca156382bef738f293.tar.gz
postgresql-4cae471d1b6bec7493dcb2ca156382bef738f293.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
Diffstat (limited to 'src/backend/parser/parse_expr.c')
-rw-r--r--src/backend/parser/parse_expr.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/parser/parse_expr.c b/src/backend/parser/parse_expr.c
index 20d923203f4..8e136a79818 100644
--- a/src/backend/parser/parse_expr.c
+++ b/src/backend/parser/parse_expr.c
@@ -3236,7 +3236,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;