BUG #6712: PostgreSQL 9.2 beta2: alter table drop constraint does not work on inherited master table

From: miroslav(dot)sulc(at)fordfrog(dot)com
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #6712: PostgreSQL 9.2 beta2: alter table drop constraint does not work on inherited master table
Date: 2012-06-30 10:58:11
Message-ID: E1SkvNT-00066C-C4@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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

Browse pgsql-bugs by date

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