| From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
|---|---|
| To: | Reiner Dassing <dassing(at)wettzell(dot)ifag(dot)de> |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Index of a table is not used (in any case) |
| Date: | 2001-10-23 04:27:07 |
| Message-ID: | Pine.BSF.4.21.0110222126040.49084-100000@megazone23.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-sql |
On Mon, 22 Oct 2001, Reiner Dassing wrote:
> Hello PostgreSQl Users!
>
> PostSQL V 7.1.1:
>
> I have defined a table and the necessary indices.
> But the index is not used in every SELECT. (Therefore, the selects are
> *very* slow, due to seq scan on
> 20 million entries, which is a test setup up to now)
>
> The definitions can be seen in the annex.
>
> Does some body know the reason and how to circumvent the seq scan?
>
> Is the order of index creation relevant? I.e., should I create the
> indices before inserting
> entries or the other way around?
>
Have you run a vacuum analyze to update the statistics after the data was
loaded?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2001-10-23 04:50:57 | Re: Index of a table is not used (in any case) |
| Previous Message | Bruce Momjian | 2001-10-23 04:24:24 | Re: [GENERAL] To Postgres Devs : Wouldn't changing the selectlimit |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2001-10-23 04:50:57 | Re: Index of a table is not used (in any case) |
| Previous Message | Christopher Kings-Lynne | 2001-10-23 04:08:14 | Re: [HACKERS] Index of a table is not used (in any case) |