Re: How do I drop a Complicated Constraint Trigger After Delete Execute Procedure?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Wang, Mary Y" <mary(dot)y(dot)wang(at)boeing(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: How do I drop a Complicated Constraint Trigger After Delete Execute Procedure?
Date: 2010-02-11 04:02:12
Message-ID: 28511.1265860932@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Wang, Mary Y" <mary(dot)y(dot)wang(at)boeing(dot)com> writes:
> Ok. I typed the correct name this time, and got the same error.
> "drop trigger bug_assigned_to_fk on users;
> ERROR: DropTrigger: there is no trigger bug_assigned_to_fk on relation users "
> "drop trigger bug_assigned_to_fk on bug;
> ERROR: DropTrigger: there is no trigger bug_assigned_to_fk on relation bug"

Huh. Do you get anything from
select * from pg_trigger where tgname = 'bug_assigned_to_fk';
or
select * from pg_trigger where tgconstrname = 'bug_assigned_to_fk';
? If I recall the 7.1 code at all, it has to be printing one or the
other of those fields as the name shown in the FK error message ...

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Wang, Mary Y 2010-02-11 04:09:34 Re: How do I drop a Complicated Constraint Trigger After Delete Execute Procedure?
Previous Message Adrian Klaver 2010-02-11 03:41:37 Re: How do I drop a Complicated Constraint Trigger After Delete Execute Procedure?