From: Bruno Wolff III <bruno@wolff.to>
To: V Chitra <vchitra@techbooks.com>
Cc: pgsql-admin@postgresql.org
Cc: pgsql-performance@postgresql.org
Subject: Re: Index called with Union but not with OR clause
Date: Fri, 20 Feb 2004 14:11:39 -0600
Message-ID: <20040220201139.GA25578@wolff.to> (raw)
In-Reply-To: <008401c3f77e$a78f1d20$18dda8c0@VICHITRA>
References: <008401c3f77e$a78f1d20$18dda8c0@VICHITRA>
This discussion really belongs on the performance list and I am copying
that list with mail-followup-to set.
On Fri, Feb 20, 2004 at 12:26:22 +0530,
V Chitra <vchitra@techbooks.com> wrote:
> Hi All,
>
> I have a select statement
>
> select * from v_func_actual_costs
> where parent_project='10478' or proj_pk = '10478'
>
> both the fields parent_project and proj_pk have indexes based on them, but when I ran explain plan on this statement I found that none of the indexes are being called. But, if I make two separate statement and combine them with Union ALL, the indexes are being called. The select statement in this case is
>
> select * from ct_admin.v_func_actual_costs
> where parent_project='10478'
> union all
> select * from ct_admin.v_func_actual_costs
> where proj_pk = '10478'
>
> Can anybody help me to find a reason for the same. This is just a part of the query so I cannot use the Union ALL clause.
Have you analyzed the databases recently?
Can you supply explain analyze output for the queries?
It isn't necessarily faster to use two index scans instead of one sequential
scan depending on the fraction of the table being returned and some other
factors. If the planner is making the wrong choice in your case, you need
to supply the list with more information to get help figuring out why
the wrong choice is being made.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: bruno@wolff.to, vchitra@techbooks.com, pgsql-admin@postgresql.org
Subject: Re: Index called with Union but not with OR clause
In-Reply-To: <20040220201139.GA25578@wolff.to>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox