because the parser has no idea — until it is too late — that ! is defined as a postfix operator, not an infix one. To get the desired behavior in this case, you must write SELECT (5 !) - 6; This is the price There are three possible syntaxes for an operator invocation: expression operator expression (binary infix operator) operator expression (unary prefix operator) expression operator (unary postfix operator) contains this operator oprowner int4 pg_shadow.usesysid Owner of the operator oprkind char b = infix (“both”), l = prefix (“left”), r = postfix (“right”) oprcanhash bool This operator supports hash

because the parser has no idea — until it is too late — that ! is defined as a postfix operator, not an infix one. To get the desired behavior in this case, you must write SELECT (5 !) - 6; This is the price There are three possible syntaxes for an operator invocation: expression operator expression (binary infix operator) operator expression (unary prefix operator) expression operator (unary postfix operator) contains this operator oprowner int4 pg_shadow.usesysid Owner of the operator oprkind char b = infix (“both”), l = prefix (“left”), r = postfix (“right”) oprcanhash bool This operator supports hash

because the parser has no idea — until it is too late — that ! is defined as a postfix operator, not an infix one. To get the desired behavior in this case, you must write SELECT (5 !) - 6; This is the price There are three possible syntaxes for an operator invocation: expression operator expression (binary infix operator) operator expression (unary prefix operator) expression operator (unary postfix operator) namespace that contains this operator oprowner oid pg_authid.oid Owner of the operator oprkind char b = infix (“both”), l = prefix (“left”), r = postfix (“right”) oprcanhash bool This operator supports hash

because the parser has no idea — until it is too late — that ! is defined as a postfix operator, not an infix one. To get the desired behavior in this case, you must write SELECT (5 !) - 6; This is the price There are three possible syntaxes for an operator invocation: expression operator expression (binary infix operator) operator expression (unary prefix operator) expression operator (unary postfix operator) namespace that contains this operator oprowner oid pg_authid.oid Owner of the operator oprkind char b = infix (“both”), l = prefix (“left”), r = postfix (“right”) oprcanhash bool This operator supports hash

because the parser has no idea — until it is too late — that ! is defined as a postfix operator, not an infix one. To get the desired behavior in this case, you must write SELECT (5 !) - 6; This is the price There are three possible syntaxes for an operator invocation: expression operator expression (binary infix operator) operator expression (unary prefix operator) expression operator (unary postfix operator) namespace that contains this operator oprowner oid pg_authid.oid Owner of the operator oprkind char b = infix (“both”), l = prefix (“left”), r = postfix (“right”) oprcanhash bool This operator supports hash

because the parser has no idea — until it is too late — that ! is defined as a postfix operator, not an infix one. To get the desired behavior in this case, you must write SELECT (5 !) - 6; This is the price There are three possible syntaxes for an operator invocation: expression operator expression (binary infix operator) operator expression (unary prefix operator) expression operator (unary postfix operator) namespace that contains this operator oprowner oid pg_authid.oid Owner of the operator oprkind char b = infix (“both”), l = prefix (“left”), r = postfix (“right”) oprcanhash bool This operator supports hash

because the parser has no idea — until it is too late — that ! is defined as a postfix operator, not an infix one. To get the desired behavior in this case, you must write: SELECT (5 !) - 6; This is the price There are three possible syntaxes for an operator invocation: expression operator expression (binary infix operator) operator expression (unary prefix operator) expression operator (unary postfix operator) namespace that contains this operator oprowner oid pg_authid.oid Owner of the operator oprkind char b = infix (“both”), l = prefix (“left”), r = postfix (“right”) oprcanmerge bool This operator supports merge

because the parser has no idea — until it is too late — that ! is defined as a postfix operator, not an infix one. To get the desired behavior in this case, you must write: SELECT (5 !) - 6; This is the price There are three possible syntaxes for an operator invocation: expression operator expression (binary infix operator) operator expression (unary prefix operator) expression operator (unary postfix operator) namespace that contains this operator oprowner oid pg_authid.oid Owner of the operator oprkind char b = infix (“both”), l = prefix (“left”), r = postfix (“right”) oprcanmerge bool This operator supports merge

because the parser has no idea — until it is too late — that ! is defined as a postfix operator, not an infix one. To get the desired behavior in this case, you must write: SELECT (5 !) - 6; This is the price There are three possible syntaxes for an operator invocation: expression operator expression (binary infix operator) 35 Chapter 4. SQL Syntax operator expression (unary prefix operator) expression operator namespace that contains this operator oprowner oid pg_authid.oid Owner of the operator oprkind char b = infix (“both”), l = prefix (“left”), r = postfix (“right”) oprcanmerge bool This operator supports merge

because the parser has no idea — until it is too late — that ! is defined as a postfix operator, not an infix one. To get the desired behavior in this case, you must write: SELECT (5 !) - 6; This is the price There are three possible syntaxes for an operator invocation: expression operator expression (binary infix operator) operator expression (unary prefix operator) expression operator (unary postfix operator) namespace that contains this operator oprowner oid pg_authid.oid Owner of the operator oprkind char b = infix (“both”), l = prefix (“left”), r = postfix (“right”) oprcanmerge bool This operator supports merge