Re: Recognizing range constraints (was Re: Plan for relatively simple query seems to be very inefficient) - Mailing list pgsql-performance

From Mischa
Subject Re: Recognizing range constraints (was Re: Plan for relatively simple query seems to be very inefficient)
Date
Msg-id 1112909198.4255a58eae0d8@webmail.telus.net
Whole thread Raw
In response to Re: Recognizing range constraints (was Re: Plan for relatively simple query seems to be very inefficient)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Recognizing range constraints (was Re: Plan for relatively simple query seems to be very inefficient)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-performance
Quoting Tom Lane <tgl@sss.pgh.pa.us>:

> Yeah, the whole thing is only a heuristic anyway.  I've been coming
> around to the view that relation membership shouldn't matter, because
> of cases like
>
>     WHERE a.x > b.y AND a.x < 42
>
> which surely should be taken as a range constraint.

Out of curiosity, will the planner induce "b.y < 42" out of this?

--
"Dreams come true, not free."


pgsql-performance by date:

Previous
From: Adam Palmblad
Date:
Subject: Re: Building postmaster with Profiling Support WAS "Tweaking a C
Next
From: "Jim C. Nasby"
Date:
Subject: Re: [HACKERS] Recognizing range constraints (was Re: Plan for relatively simple query seems to be very inefficient)