"Drop index concurrently" leaving behind invalid indexes - Mailing list pgsql-bugs

From Moppel, Kaarel
Subject "Drop index concurrently" leaving behind invalid indexes
Date
Msg-id CAAMYFukoVyH=yqhQ8FqstS1F0TWFNAFb-XvPDUjjVvvA9QT3Kw@mail.gmail.com
Whole thread Raw
List 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

pgsql-bugs by date:

Previous
From: s.beer@pyton.nl
Date:
Subject: BUG #12127: could not stat file
Next
From: Tom Lane
Date:
Subject: Re: BUG #12126: Empty tsvector as output of to_tsvector function