Skip site navigation (1) Skip section navigation (2)

Re: Inner join on two OR conditions dont use index

From: John A Meinel <john(at)arbash-meinel(dot)com>
To: Jocelyn Turcotte <turcotte(dot)j(at)gmail(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Inner join on two OR conditions dont use index
Date: 2005-05-25 20:18:52
Message-ID: 4294DDAC.1060908@arbash-meinel.com (view raw or flat)
Thread:
Lists: pgsql-performance
Jocelyn Turcotte wrote:

>Hi all
>i dont know if this is normal, but if yes i would like to know why and
>how I could do it another way other than using unions.
>
>

The only thing that *might* work is if you used an index on both keys.
So if you did:

CREATE INDEX rt_edge_start_end_node ON rt_edge(start_node_id,end_node_id);

The reason is that in an "OR" construct, you have to check both for being true. So in the general case where you don't know the correlation between the columns, you have to check all of the entries, because even if you know the status of one side of the OR, you don't know the other.

Another possibility would be to try this index:

CREATE INDEX rt_edge_stare_or_end ON rt_edge(start_node_id OR end_node_id);

I'm not sure how smart the planner can be, though.

John
=:->


In response to

Responses

pgsql-performance by date

Next:From: Mohan, RossDate: 2005-05-25 20:36:54
Subject: test - pls delete and ignore
Previous:From: Jocelyn TurcotteDate: 2005-05-25 20:12:00
Subject: Inner join on two OR conditions dont use index

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group