"Tobias Brox" <[EMAIL PROTECTED]> writes
> Is it any way to attempt to force the planner to use some specific index
> while creating the plan? Other than eventually dropping all the other
> indices (which is obiously not a solution in production setting anyway)?
>
I don't think currently PG suppo
HI all,
I also would like to know if there is a way to force a use of a
specific index for a specific query. I am currently using Postgresql
7.4.6
In my case I have a relatively big table (several millions of records)
that are frequently used to join with other tables (explicit join or
through vie
A pretty awful way is to mangle the sql statement so the other field
logical statements are like so:
select * from mytable where 0+field = 100
Tobias Brox wrote:
Is it any way to attempt to force the planner to use some specific index
while creating the plan? Other than eventually dropping
Is it any way to attempt to force the planner to use some specific index
while creating the plan? Other than eventually dropping all the other
indices (which is obiously not a solution in production setting anyway)?
I have one case where I have added 16 indices to a table, many of them
beeing par
