Home > Archive > PostgreSQL Discussion > April 2005 > Re: About index - "a query or data manipulation command can use at most one index per table&qu









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author Re: About index - "a query or data manipulation command can use at most one index per table&qu
Michael Fuhr

2005-04-26, 8:23 pm

On Tue, Apr 26, 2005 at 01:58:09PM -0400, Ying Lu wrote:
>
> A question about index. It mentioned in postgresql 8.0 doc "a query or
> data manipulation command can use *at most one index* *per table*". An
> example query is:
>
> select * from A left join B using (id) where A.type='apple' and
> A.isExport=true;
>
> "id" is the primary key for both table A & B. If index (type, isExport)
> has been created for table A. In the above query, will this index works?


You can use EXPLAIN to see the query plan, including which indexes
will be used. See "Using EXPLAIN" in the "Performance Tips" chapter
of the documentation.

http://www.postgresql.org/docs/8.0/...l#USING-EXPLAIN
http://www.postgresql.org/docs/8.0/...ql-explain.html

A query won't necessarily use an index if one is available: if the
planner thinks a sequential scan will be faster than using an index,
then it won't use the index. If you want to see whether an index
scan *could* be used, then set enable_seqscan to off before running
EXPLAIN.

--
Michael Fuhr
http://www.fuhr.org/~mfuhr/

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql
.org

Sponsored Links





Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive | Programming forum archive

Copyright 2008 droptable.com