Re: Drop big index
От | Vojtěch Rylko |
---|---|
Тема | Re: Drop big index |
Дата | |
Msg-id | 4F3D190D.9030103@seznam.cz обсуждение исходный текст |
Ответ на | Re: Drop big index (Marti Raudsepp <marti@juffo.org>) |
Список | pgsql-general |
Dne 16.2.2012 9:53, Marti Raudsepp napsal(a): > 2012/2/15 Vojtěch Rylko<vojta.rylko@seznam.cz>: >> this query performed so long and blocked table so I had to interrupt it. Is >> there any way how to drop large indexes in non-blocking or /faster/ way? > Usually the problem is not with the size of the index -- but some > other running transactions that hold a read lock on the table, and > preventing the DROP INDEX from getting an exclusive lock. If the > exclusive lock is granted, the drop index is usually very fast. > > Run 'select * from pg_stat_activity' and see if there are any "<IDLE> > in transaction" connections. It's normal to have these for a second or > few, but longer idle transactions usually indicate an application bug > -- it started a transaction, but "forgot" to rollback or commit. These > are problematic for this exact reason -- locks can't be released until > the transaction finishes. > > Regards, > Marti > Thanks! Caused by "IDLE in transaction". My nightmare solved. Droping 7 GB index in 2353 ms. Regards, Vojtěch R.
В списке pgsql-general по дате отправления: