Re: Disabling an index temporarily - Mailing list pgsql-hackers

From Joshua D. Drake
Subject Re: Disabling an index temporarily
Date
Msg-id 566B8E94.1080707@commandprompt.com
Whole thread Raw
In response to Disabling an index temporarily  (Tatsuo Ishii <ishii@postgresql.org>)
Responses Re: Disabling an index temporarily  (Tatsuo Ishii <ishii@postgresql.org>)
Re: Disabling an index temporarily  (Jaime Casanova <jaime.casanova@2ndquadrant.com>)
List pgsql-hackers
On 12/11/2015 06:25 PM, Tatsuo Ishii wrote:

> What about inventing a new SET command something like:
>
> SET disabled_index to <index-name>
>
> This adds <index-name> to "disabled index list". The disabled index
> list let the planner to disregard the indexes in the list.
>
> SET enabled_index to <index-name>
>
> This removes <index-name> from the disabled index list.
>
> SHOW disabled_index
>
> This shows the content of the disabled index list.

Wouldn't something like:

ALTER INDEX foo SET DISABLED;

See more in line with our grammar?

I assume the index is only disabled as far as the planner is concerned 
and all updates/inserts/deletes will still actually update the index 
appropriately?

JD




-- 
Command Prompt, Inc. - http://www.commandprompt.com/  503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Announcing "I'm offended" is basically telling the world you can't
control your own emotions, so everyone else should do it for you.



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: More on the libxml2 update situation
Next
From: Tatsuo Ishii
Date:
Subject: Re: Disabling an index temporarily