This threw ERROR, not the expected NOTICE, if the index didn't exist.
The bug was actually visible in not-as-expected regression test output,
so somebody wasn't paying too close attention in commit
8cb53654dbdb4c386369eb988062d0bbb6de725e.
Per report from Brendan Byrd.
                {
                    DropStmt *n = makeNode(DropStmt);
                    n->removeType = OBJECT_INDEX;
-                   n->missing_ok = FALSE;
+                   n->missing_ok = TRUE;
                    n->objects = $6;
                    n->arguments = NIL;
                    n->behavior = $7;
 
 --
 DROP INDEX CONCURRENTLY "concur_index2";               -- works
 DROP INDEX CONCURRENTLY IF EXISTS "concur_index2";     -- notice
-ERROR:  index "concur_index2" does not exist
+NOTICE:  index "concur_index2" does not exist, skipping
 -- failures
 DROP INDEX CONCURRENTLY "concur_index2", "concur_index3";
 ERROR:  DROP INDEX CONCURRENTLY does not support dropping multiple objects