At 01:16 28/06/2005, Karl O. Pinc wrote:
>"If you do not succeed in adjusting the costs to be more
>appropriate, then you may have to resort to forcing index
>Is there a way to force a query to use a particular index?
Not that I know of.
>If not, what does this sentence mean?
That you can force the planner to use an index (any one) over not using an
index (and using seq scans instead) by setting enable_seqscan to off.
In response to
pgsql-performance by date
|Next:||From: Karl O. Pinc||Date: 2005-06-27 23:09:26|
|Subject: Poor index choice -- multiple indexes of the same columns|
|Previous:||From: Josh Berkus||Date: 2005-06-27 22:37:41|
|Subject: Re: Poor index choice -- multiple indexes of the same columns|