Re: temporarily deactivate an index

From: "Jaime Casanova" <systemguards(at)gmail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Viktor Rosenfeld" <rosenfel(at)informatik(dot)hu-berlin(dot)de>, "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: temporarily deactivate an index
Date: 2008-06-08 17:37:13
Message-ID: c2d9e70e0806081037q3e4cb02fx6f5c32e14148079d@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sun, Jun 8, 2008 at 11:45 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Viktor Rosenfeld <rosenfel(at)informatik(dot)hu-berlin(dot)de> writes:
>> 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.
>
> Well, you're going to have to change *something* on the client side,
> assuming you want this behavioral change to affect only some queries.
>
> Otherwise, in versions that have CREATE INDEX CONCURRENTLY you could
> mark the index not ready to use yet (see pg_index.indisvalid or
> pg_index.indisready depending on version).
>

if i mark the index not ready (using pg_index.indisvalid or
pg_index.indisready depending on version), will the index be updated
if in another transaction i make an insert?

--
regards,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Guayaquil - Ecuador
Cel. (593) 87171157

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alvaro Herrera 2008-06-08 18:18:05 Re: temporarily deactivate an index
Previous Message Tom Lane 2008-06-08 17:01:54 Re: libpq.so.4