On Thu, May 2, 2013 at 9:48 AM, Simon Riggs wrote:
>>> SELECT count(k0.id)
>>> FROM k0
>>> WHERE 1 = 2
>>> OR k0.id IN (
>>> SELECT k1.k0_id
>>> FROM k1
>>> WHERE k1.k1k2_id IN (
>>> SELECT k2.k1k2_id
>>> FROM k2
>>> WHERE
On 18 April 2013 15:46, Tom Lane wrote:
> dmitry potapov writes:
>> I recently stumbled upon on what could be a planner bug or a corner case.
>> If " OR ..." is added to WHERE clause of SELECT query,
>> then the planner chooses a very inefficient plan. Consider a query:
>
>> SELECT count(k0.id)
>
dmitry potapov writes:
> I recently stumbled upon on what could be a planner bug or a corner case.
> If " OR ..." is added to WHERE clause of SELECT query,
> then the planner chooses a very inefficient plan. Consider a query:
> SELECT count(k0.id)
> FROM k0
> WHERE 1 = 2
> OR k0.id IN (
>
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 " 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
Hello,
I recently stumbled upon on what could be a planner bug or a corner case.
If " OR ..." is added to WHERE clause of SELECT query,
then the planner chooses a very inefficient plan. Consider a query:
SELECT count(k0.id)
FROM k0
WHERE 1 = 2
OR k0.id IN (
SELECT k1.k0_id
FRO
