| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | akp geek <akpgeek(at)gmail(dot)com> |
| Cc: | Dann Corbit <DCorbit(at)connx(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Index question on postgres |
| Date: | 2010-01-08 05:29:59 |
| Message-ID: | dcc563d11001072129u33eb6c78q68021d010b23ecc6@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Jan 7, 2010 at 10:04 PM, akp geek <akpgeek(at)gmail(dot)com> wrote:
> the explain from both enviroments ??? need to be posted.
> just one quick question. Why would the index I have created not being used?
> Regards
Better explain analyze than plain eplain.
If the retrieval of data by seq scan is deemed "cheaper" than index
acces by postgresql's rather impressive planner system then a seq scan
is chosen. There are many methods for joining and so on, so picking
the right one can give you much better speed than a simple nested loop
only planner etc.
You might want to attach the query plans as a text file to preserve format.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yan Cheng Cheok | 2010-01-08 06:20:49 | check the execution status of stored procedure |
| Previous Message | akp geek | 2010-01-08 05:04:22 | Re: Index question on postgres |