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

From Wang, Mary Y
Subject Re: How do I drop a Complicated Constraint Trigger After Delete Execute Procedure?
Date
Msg-id FA20D4C4FEBFD148B1C0CB09913825FC01EBDA2FBC@XCH-SW-06V.sw.nos.boeing.com
Whole thread Raw
In response to Re: How do I drop a Complicated Constraint Trigger After Delete Execute Procedure?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
I guess I could just use
"DELETE FROM pg_trigger WHERE tgname = "RI_ConstraintTrigger_9217018"
I just wanted to make sure that I don't mess up the system table.

Mary

-----Original Message-----
From: Wang, Mary Y
Sent: Wednesday, February 10, 2010 8:10 PM
To: 'Tom Lane'
Cc: pgsql-general@postgresql.org
Subject: RE: [GENERAL] How do I drop a Complicated Constraint Trigger After Delete Execute Procedure?

Wow!! Good memory.
I didn't get anything with the 'select * from pg_trigger where tgname = 'bug_assigned_to_fk';' but I got something here
:
 select * from pg_trigger where tgconstrname = 'bug_assigned_to_fk';
 tgrelid |            tgname            | tgfoid | tgtype | tgenabled | tgisconstr                  aint |
tgconstrname   | tgconstrrelid | tgdeferrable | tginitdeferred | tgnarg                  s | tgattr |
              tgargs                                                 
---------+------------------------------+--------+--------+-----------+-----------
-----+--------------------+---------------+--------------+----------------+-------
--+--------+----------------------------------------------------------------------                 ---- 
 7335118 | RI_ConstraintTrigger_9217018 |   1655 |     17 | t         | t                                |
bug_assigned_to_fk|       7329978 | f            | f              |                         6 |        |
bug_assigned_to_fk\000bug\000users\000FULL\000assigned_to\000user_id\                 000 
 7335118 | RI_ConstraintTrigger_9217016 |   1654 |      9 | t         | t                                |
bug_assigned_to_fk|       7329978 | f            | f              |                         6 |        |
bug_assigned_to_fk\000bug\000users\000FULL\000assigned_to\000user_id\                 000 
 7329978 | RI_ConstraintTrigger_9217014 |   1644 |     21 | t         | t                                |
bug_assigned_to_fk|       7335118 | f            | f              |                         6 |        |
bug_assigned_to_fk\000bug\000users\000FULL\000assigned_to\000user_id\                 000 
(3 rows)

What do I do with them?
------------------------------------------------
Mary Y Wang

-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Wednesday, February 10, 2010 8:02 PM
To: Wang, Mary Y
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] How do I drop a Complicated Constraint Trigger After Delete Execute Procedure?

"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
beprinting 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: u235sentinel
Date:
Subject: Postgres Triggers issue
Next
From: Tom Lane
Date:
Subject: Re: How do I drop a Complicated Constraint Trigger After Delete Execute Procedure?