| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | pgus-general(at)postgresql(dot)org |
| Cc: | Julius Tuskenis <julius(dot)tuskenis(at)gmail(dot)com> |
| Subject: | Re: why sequential scan is used on indexed column ??? |
| Date: | 2008-06-15 20:33:16 |
| Message-ID: | 200806151333.16798.josh@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgus-general |
Julius,
> I have a question concerning performance. One of my queries take a long
> to execute. I tried to do "explain analyse" and I see that the
> sequential scan is being used, although I have indexes set on columns
> that are used in joins. The question is - WHY, and how to change that
> behavior???
This is not the right mailing list for your question. Please send it to
pgsql-performance mailing list instead.
--
Josh Berkus
PostgreSQL @ Sun
San Francisco
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2008-06-16 17:58:22 | Re: Draft bylaws are now available |
| Previous Message | Julius Tuskenis | 2008-06-14 14:41:20 | why sequential scan is used on indexed column ??? |