"Drop index concurrently" leaving behind invalid indexes

From: "Moppel, Kaarel" <kaarel(dot)moppel(at)zalando(dot)de>
To: pgsql-bugs(at)postgresql(dot)org
Subject: "Drop index concurrently" leaving behind invalid indexes
Date: 2014-12-02 09:55:00
Message-ID: CAAMYFukoVyH=yqhQ8FqstS1F0TWFNAFb-XvPDUjjVvvA9QT3Kw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

On a busy database I've been recently getting invalid indexes, what looks
like a result of 'drop index concurrently' timing out. Could not repeat the
behaviour though with a simple local test setup.

The docs (http://www.postgresql.org/docs/9.3/static/sql-dropindex.html)
don't mention this possibility also as opposed to 'create index
concurrently' and I didn't find anything from the archives.
Any thoughts on that?

Thanks,
Kaarel

Browse pgsql-bugs by date

  From Date Subject
Next Message marcin.ogorzalek 2014-12-02 10:34:02 BUG #12126: Empty tsvector as output of to_tsvector function
Previous Message Devrim Gündüz 2014-12-01 23:32:28 Re: BUG #12072: init script creates pid file with wrong owner