From: | "Jaime Casanova" <systemguards(at)gmail(dot)com> |
---|---|
To: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
Cc: | "Viktor Rosenfeld" <rosenfel(at)informatik(dot)hu-berlin(dot)de>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: temporarily deactivate an index |
Date: | 2008-06-08 13:55:48 |
Message-ID: | c2d9e70e0806080655t52aab50s8eed0d75675b8117@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sun, Jun 8, 2008 at 1:34 AM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
> On Sat, Jun 7, 2008 at 5:16 PM, Viktor Rosenfeld
> <rosenfel(at)informatik(dot)hu-berlin(dot)de> wrote:
>>>
>>> Try this:
>>>
>>> begin;
>>> drop indexname;
>>> explain analyze select ...;
>>> rollback;
>>
>> That works, but I'm still looking for another way to deactivate the index.
>> The reason being, that my query load is randomly generated by a Java
>> program and I don't want to go and change the SQL compiler.
>
> Sorry, I'm out of ideas. I mean, you can turn off all indexes with
> set enable_indexscan=off but there's no other way to do it cheaply and
> in such a fine grained way.
>
with "enable_indexscan=off" you're not turning indexes off but putting
a high cost in using them... the effect, most of the time, is that
indexes will not be used but you can't be sure...
the better solution was the first one: dropping the index inside a
transaction, execute the explain analyze of the query and rollback the
transaction
--
regards,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Guayaquil - Ecuador
Cel. (593) 87171157
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2008-06-08 16:09:30 | Re: temporarily deactivate an index |
Previous Message | Oliver Kohll | 2008-06-08 10:55:45 | libpq.so.4 |