The following bug has been logged on the website:

Bug reference:      6712
Logged by:          Miroslav Šulc
Email address:      miroslav(dot)sulc(at)fordfrog(dot)com
PostgreSQL version: Unsupported/Unknown
Operating system:   Gentoo Linux
Description:        

here is the test case:

test=# create table test_constraints (id int, val1 varchar, val2 int, unique
(val1, val2));
NOTICE:  CREATE TABLE / UNIQUE will create implicit index
"test_constraints_val1_val2_key" for table "test_constraints"
CREATE TABLE
test=# create table test_constraints_inh () inherits (test_constraints);
CREATE TABLE
test=# alter table only test_constraints drop constraint
test_constraints_val1_val2_key;
ERROR:  constraint "test_constraints_val1_val2_key" of relation
"test_constraints_inh" does not exist


postgresql tries to drop the constraint even from descendant table though
"only" is specified.

Responses

• Re: BUG #6712: PostgreSQL 9.2 beta2: alter table drop constraint does not work on inherited master table at 2012-07-02 10:46:31 from Amit Kapila

pgsql-bugs by date

Next:	From: Tom Lane	Date: 2012-06-30 15:12:56
	Subject: Re: BUG #6706: pg_upgrade fails when plpgsql dropped/re-created
Previous:	From: Bruce Momjian	Date: 2012-06-30 05:08:51
	Subject: Re: BUG #6706: pg_upgrade fails when plpgsql dropped/re-created