Re: Huge speed penalty using <>TRUE instead of =FALSE - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Huge speed penalty using <>TRUE instead of =FALSE
Date
Msg-id 29292.1247840503@sss.pgh.pa.us
Whole thread Raw
In response to Re: Huge speed penalty using <>TRUE instead of =FALSE  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: Huge speed penalty using <>TRUE instead of =FALSE  (Greg Stark <stark@mit.edu>)
Re: Huge speed penalty using <>TRUE instead of =FALSE  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-bugs
Peter Eisentraut <peter_e@gmx.net> writes:
> ... But again, this is data type specific knowledge.

Actually, now that I think about it, the planner already has
datatype-specific knowledge about boolean equality (see
simplify_boolean_equality).  It would take just a few more lines of code
there to recognize "x <> true" and "x <> false" as additional variant
spellings of the generic "x" or "NOT x" constructs.  Not sure if it's
worth the trouble though; how many people really write such things?

If you really wanted to take it to extremes, you could also reduce
cases like "x > false", but that's starting to get a bit silly.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Huge speed penalty using <>TRUE instead of =FALSE
Next
From: Greg Stark
Date:
Subject: Re: Huge speed penalty using <>TRUE instead of =FALSE