| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Rohit Gaddi <rohitgaddi(at)yahoo(dot)co(dot)in> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: index selection by query planner |
| Date: | 2005-06-20 20:34:48 |
| Message-ID: | 200506201334.48766.josh@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Rohit,
> I have a table with two indices on the same column, one of which is a
> partial index. I would like the query planner to use the partial index
> whenever the query condition lies in the range of the partial index as it
> would yield better performance. Is there any way to enforce the ordering
> for the indices? How does the query planner decide which index to use when
> a particular query is fired? 'Explain Analyze' showed the total index
> being used in a situation that could be fulfiled by the partial index.
Please post the query, the table and index definitions, and the EXPLAIN
ANALYZE to the PGSQL-PERFORMANCE mailing list. Thanks!
--
Josh Berkus
Aglio Database Solutions
San Francisco
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-06-20 20:54:37 | Re: Issue with plpython write_file and read_file tests |
| Previous Message | Josh Berkus | 2005-06-20 20:26:20 | Re: Checkpointing problem with new buffer mgr. |