On 18/04/13 15:20, dmitry potapov wrote:
Hello,
I recently stumbled upon on what could be a planner bug or a corner
case. If "<false condition> OR ..." is added to WHERE clause of SELECT
query, then the planner chooses a very inefficient plan. Consider a query:
If I comment out "1=2 OR", then the plan changes dramatically:
What happens if you substitute:
1. 1=3 OR
2. false OR
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-performance mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
