From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
---|---|
To: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Disabling an index temporarily |
Date: | 2015-12-12 02:25:36 |
Message-ID: | 20151212.112536.1628974191058745674.t-ishii@sraoss.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Sometimes I need to repeat creating and dropping indexes while doing
an SQL tuning work. As you might know, creating a large index takes
long time. So dropping the index and re-creating it is pain and
counter productive.
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.
Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp
From | Date | Subject | |
---|---|---|---|
Next Message | Noah Misch | 2015-12-12 02:37:45 | Re: Re: In-core regression tests for replication, cascading, archiving, PITR, etc. |
Previous Message | Peter Eisentraut | 2015-12-12 02:17:25 | strange CREATE INDEX tab completion cases |