Re: How do I drop a Complicated Constraint Trigger After Delete Execute Procedure? - Mailing list pgsql-general

From Tom Lane
Subject Re: How do I drop a Complicated Constraint Trigger After Delete Execute Procedure?
Date
Msg-id 28511.1265860932@sss.pgh.pa.us
Whole thread Raw
In response to Re: How do I drop a Complicated Constraint Trigger After Delete Execute Procedure?  ("Wang, Mary Y" <mary.y.wang@boeing.com>)
Responses Re: How do I drop a Complicated Constraint Trigger After Delete Execute Procedure?  ("Wang, Mary Y" <mary.y.wang@boeing.com>)
List pgsql-general
"Wang, Mary Y" <mary.y.wang@boeing.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

pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: How do I drop a Complicated Constraint Trigger After Delete Execute Procedure?
Next
From: "Wang, Mary Y"
Date:
Subject: Re: How do I drop a Complicated Constraint Trigger After Delete Execute Procedure?