Re: disabling an index without deleting it?
| От | Jeff Davis | 
|---|---|
| Тема | Re: disabling an index without deleting it? | 
| Дата | |
| Msg-id | 1204139818.16886.29.camel@dogma.ljc.laika.com обсуждение исходный текст | 
| Ответ на | Re: disabling an index without deleting it? (Tom Lane <tgl@sss.pgh.pa.us>) | 
| Ответы | Re: disabling an index without deleting it? | 
| Список | pgsql-performance | 
On Tue, 2008-02-26 at 17:22 -0500, Tom Lane wrote:
> "Joshua D. Drake" <jd@commandprompt.com> writes:
> > "Scott Marlowe" <scott.marlowe@gmail.com> wrote:
> >> begin;
> >> drop index abc_dx;
> >> select ....
> >> rollback;
> >>
> >> and viola, your index is still there.  note that there are likely some
> >> locking issues with this, so be careful with it in production.  But on
> >> a test box it's a very easy way to test various indexes.
>
> > Wouldn't you also bloat the index?
>
> No, what makes you think that?  The index won't change at all in the
> above example.  The major problem is, as Scott says, that DROP INDEX
> takes exclusive lock on the table so any other sessions will be locked
> out of it for the duration of your test query.
It may cause catalog bloat though, right?
Regards,
    Jeff Davis
		
	В списке pgsql-performance по дате отправления: