From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
---|---|
To: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>, "Mladen Gogala" <mladen(dot)gogala(at)vmsinfo(dot)com> |
Subject: | Re: Postgres 9.0 has a bias against indexes |
Date: | 2011-01-27 15:49:38 |
Message-ID: | 4D413FB20200002500039E93@gw.wicourts.gov |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Mladen Gogala <mladen(dot)gogala(at)vmsinfo(dot)com> wrote:
> The optimizer will not use index, not even when I turn off both
> hash and merge joins. This is not particularly important for a
> table with 14 rows, but for a larger table, this is a problem.
If it still does that with a larger table. Do you have an example
of that? Showing that it goes straight to the data page when the
table only has one, without first wasting time going through the
index page, doesn't prove that it won't use the index when it might
actually help -- much less point to the cause of the issue in the
larger table, which might lead to a solution.
-Kevin
From | Date | Subject | |
---|---|---|---|
Next Message | J Sisson | 2011-01-27 15:51:16 | Re: Postgres 9.0 has a bias against indexes |
Previous Message | Kenneth Marshall | 2011-01-27 15:45:39 | Re: Postgres 9.0 has a bias against indexes |