| From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
|---|---|
| To: | Sebastian Böck <sebastianboeck(at)freenet(dot)de> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Bug with index-usage? |
| Date: | 2005-11-14 17:17:40 |
| Message-ID: | 1131988660.3582.1.camel@state.g2switchworks.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, 2005-11-14 at 11:07, Sebastian Böck wrote:
> Hello,
>
> I get unpredictibale results selecting from a view depending on
> index-usage.
PostgreSQL uses a cost based planner. So, it tends to not use the plan
you might expect, especially in "toy" test cases with small data sets.
I.e. why use an index to look up 10 values, when they all fit on the
same page. Just seq scan the data from the table.
Fill up your table with REAL data (or a close substitute) and test
again. Also, read up on the admin section, specifically the part on the
postgresql.conf file and what the settings in there mean, then read
http://www.varlena.com/varlena/GeneralBits/Tidbits/perf.html
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sebastian Böck | 2005-11-14 17:25:41 | Re: Bug with index-usage? |
| Previous Message | Sebastian Böck | 2005-11-14 17:07:40 | Bug with index-usage? |