[postgresSQL] [bug] Two or more different types of constraints with same name creates ambiguity while drooping.

Hi Team,

While I was  working on constraints node in pgadmin4 I came across this scenario. Please let me know if it's correct behaviour or a bug.

If we execute above query for first time then it drops primary key first and if execute same query for second time then it drops foreign key.

Also in pgadmin3 if we right click on foreign key and try to drop it, it drops primary key and not the foreign key. We have to drop foreign key twice to actually drop the foreign key if primary key with same was there.


Note: Create foreign key first and then primary key with same name.