From: | Andreas Kretschmer <akretschmer(at)spamfence(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: DROP INDEX CASCADE doesn't want to drop unique constraints? |
Date: | 2017-04-24 12:38:14 |
Message-ID: | 20170424123814.GA20971@tux |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Ivan Voras <ivoras(at)gmail(dot)com> wrote:
> Hello,
>
> On trying to drop an index named "employer_employerid_key" which supports a
> unique constraint:
>
> "employer_employerid_key" UNIQUE CONSTRAINT, btree (employerid)
>
> I get this error:
>
> ERROR: cannot drop index employer_employerid_key because constraint
> employer_employerid_key on table employer requires it
> HINT: You can drop constraint employer_employerid_key on table employer
> instead.
>
> I'm using the CASCADE and IF EXISTS arguments and the docs say nothing about
> any special cases (https://www.postgresql.org/docs/9.3/static/
> sql-dropindex.html). This is with PostgreSQL 9.3.15.
>
> The actual command is:
>
> drop index if exists employer_employerid_key cascade;
>
> Any ideas if this is normal or why it happens?
Drop the constraint:
alter table employer drop constraint employer_employerid_key;
Regards, Andreas Kretschmer
--
Andreas Kretschmer
http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2017-04-24 13:05:33 | Re: [pgadmin-hackers] file permission on ssl key |
Previous Message | Ivan Voras | 2017-04-24 12:11:59 | DROP INDEX CASCADE doesn't want to drop unique constraints? |