Re: BUG #3424: Not able to drop trigger(RI_trigger*) on specific table.

From: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
To: S R Madhu <sraj_madhusr(at)yahoo(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #3424: Not able to drop trigger(RI_trigger*) on specific table.
Date: 2007-07-03 08:49:41
Message-ID: 468A0DA5.4020801@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

S R Madhu wrote:
> We have created a table "student".
> Foreign key and triggers are created in student. We are able to map triggers
> and constraints from pg_class table.
>
> We have used following mapping mechanism to get the trigger name.
> pg_class.relfilenode -> pg_trigger.tgrelid.
>
> We have used following mapping mechanism to get the constraint name.
> pg_class.relfilenode -> pg_constraint.conrelid.
>
> Problem : After ALTER TABLE command to this table, We are not able to map
> triggers/constraints and tables.
> relfilenode in pg_class is changed after ALTER TABLE.
> but this is not reflected in pg_constraint/pg_triggers.

pg_trigger.tgrelid and pg_constraint.conrelid reference the oid of the
relation, not relfilenode. Initially, relfilenode happens to have the
same value, but as you noticed, some commands like ALTER TABLE change it.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message David Flater 2007-07-03 15:59:31 BUG #3426: Rows disappear from complex join
Previous Message S R Madhu 2007-07-03 07:07:12 BUG #3424: Not able to drop trigger(RI_trigger*) on specific table.