Albe Laurenz <laurenz.albe@xxxxxxxxxx> wrote: > Vojtech Rylko wrote: > > I need to drop some b-tree indexes because they are not used anymore. > > Size of indexes vary between 700 MB and 7 GB. I tried common DROP > > INDEX... but 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? > > Unfortunately not (yet). > PostgreSQL 9.2 will have DROP INDEX CONCURRENTLY. Really? Great! I have a use-case for that: an partial index, daily re-created (the index based on the date and includes the last N days), and sometimes we have trouble with this. Andreas -- Really, I'm not out to destroy Microsoft. That will just be a completely unintentional side effect. (Linus Torvalds) "If I was god, I would recompile penguin with --enable-fly." (unknown) Kaufbach, Saxony, Germany, Europe. N 51.05082°, E 13.56889° -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
