On Sun, Jun 8, 2008 at 11:45 AM, Tom Lane <[EMAIL PROTECTED]> wrote: > Viktor Rosenfeld <[EMAIL PROTECTED]> 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 -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
