| From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
|---|---|
| To: | laurenz(dot)albe(at)wien(dot)gv(dot)at |
| Cc: | jd(at)commandprompt(dot)com, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: Disabling an index temporarily |
| Date: | 2015-12-12 11:13:12 |
| Message-ID: | 20151212.201312.617523493525438049.t-ishii@sraoss.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Tatsuo Ishii wrote:
>>> Wouldn't something like:
>>>
>>> ALTER INDEX foo SET DISABLED;
>>>
>>> See more in line with our grammar?
>>
>> But this will affect other sessions, no?
>
> Not if it is used in a transaction that ends with a ROLLBACK,
> but then you might as well use DROP INDEX, except
> that DROP INDEX takes an access exclusive lock.
I thought about this. Problem with the transaction rollback technique
is, I would not be able to test with an application which runs
multiple transactions.
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 | Michael Paquier | 2015-12-12 11:29:12 | Re: Re: In-core regression tests for replication, cascading, archiving, PITR, etc. |
| Previous Message | Julien Rouhaud | 2015-12-12 11:01:22 | Re: Disabling an index temporarily |