A newer version of this documentation is available. Use the version menu above to view the most up-to-date release of the Greenplum 6.x documentation.
Removes an index.
DROP INDEX [ CONCURRENTLY ] [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ]
DROP INDEX drops an existing index from the database system. To execute this command you must be the owner of the index.
- Drop the index without locking out concurrent selects, inserts, updates, and deletes on the index's table. A normal DROP INDEX acquires an exclusive lock on the table, blocking other accesses until the index drop can be completed. With this option, the command instead waits until conflicting transactions have completed.
- There are several caveats to be aware of when using this option. Only one index name can be specified, and the CASCADE option is not supported. (Thus, an index that supports a UNIQUE or PRIMARY KEY constraint cannot be dropped this way.) Also, regular DROP INDEX commands can be performed within a transaction block, but DROP INDEX CONCURRENTLY cannot.
- IF EXISTS
- Do not throw an error if the index does not exist. A notice is issued in this case.
- The name (optionally schema-qualified) of an existing index.
- Automatically drop objects that depend on the index.
- Refuse to drop the index if any objects depend on it. This is the default.
Remove the index title_idx:
DROP INDEX title_idx;
DROP INDEX is a Greenplum Database language extension. There are no provisions for indexes in the SQL standard.