Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am working on a function that allows me to add an index if it does not exist. I am running into the problem that I cannot get a list of indexes to compare to. Any thoughts?

This is a similar issue to the column creation one that is solved with this code:

share|improve this question
you can try: SELECT * from pg_indexes where schemaname = '[schemaname]' and indexname = '[indexname]'. Replace [schemaname] and [indexname] with proper values. Ref: – jbarrameda May 16 at 20:49
up vote 54 down vote accepted

Index names in PostgreSQL

  • Index names are unique across a single database schema.
  • Index names cannot be the same as any other index, (foreign) table, (materialized) view, sequence or user-defined composite type in the same schema.
  • Two tables in the same schema cannot have an index of the same name. (Follows logically.)

If you do not care about the name of the index, you can have Postgres auto-name it:

CREATE INDEX ON tbl1 (col1)

is (almost) the same as

CREATE INDEX tbl1_col1_idx ON tbl1 USING btree (col1);

Except that Postgres will avoid a naming collision and automatically pick the next free name:


Just try it. But obviously you would not want to create multiple redundant indexes. So it wouldn't be a good idea to just blindly create a new one.

Test for existence

Postgres 9.3 or older

A very simple way to test is to cast the schema-qualified name to regclass:

SELECT 'myschema.myname'::regclass

If it throws an exception, the name is free.
Or, to test the same without throwing an exception, used in a DO statement:

DO $$

    SELECT 1
    FROM   pg_class c
    JOIN   pg_namespace n ON n.oid = c.relnamespace
    WHERE  c.relname = 'my_name'
    AND    n.nspname = 'myschema' -- 'public' by default
    ) THEN

    CREATE INDEX my_name ON myschema.mytable (mycolumn);


This doesn't work for CREATE INDEX CONCURRENTLY, since that variant cannot be wrapped in an outer transaction. See comment by @Gregory below.

The DO statement was introduced with Postgres 9.0. In earlier versions you have to create a function to do the same.
Details about pg_class in the manual.
Basics about indexes in the manual.

Postgres 9.4

You can use the new function to_regclass() to check without throwing an exception:

SELECT to_regclass('myschema.myname');

Returns NULL if an index (or another object) of that name does not exist. Details:

Postgres 9.5

Now available:


Also works for CREATE INDEX CONCURRENTLY. However, per documentation:

Note that there is no guarantee that the existing index is anything like the one that would have been created.

It's a plain check for the object name.

share|improve this answer
While being a great answer, do note that you can't add indexes CONCURRENTLY this way. You'll get ERROR: CREATE INDEX CONCURRENTLY cannot be executed from a function or multi-command string. – Gregory Goltsov Aug 1 '14 at 11:59

protected by Paul White Jul 22 '15 at 6:19

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged or ask your own question.