Re: How can I view the definition of an existing trigger?

From: wsheldah(at)lexmark(dot)com
To: Bernie Holmes <holmes(at)msu(dot)edu>
Cc: Private_User(at)lexmark(dot)com, Justin Clift <justin(at)postgresql(dot)org>, pgsql-general(at)postgresql(dot)org
Subject: Re: How can I view the definition of an existing trigger?
Date: 2001-08-13 15:35:38
Message-ID: 200108131535.LAA15196@interlock2.lexmark.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

That's a good start, and I'm certainly going to hold on to this query. That
gave me a good list of triggers and their functions. The info I'm still looking
for is: on what events do the triggers get fired (insert, update, delete) and
what do the functions do? in other words, the actual text of the create
function statement that was used to create the function, or its equivalent.
Sort of like a \d for functions.

[ a short time passes ]

Ok, I finally got pgAdmin installed and working, thanks to a couple of tips in
the archives of this terrific group. It does show the definitions of functions,
but has it stuck in a real tiny box. But at least it's there. And I also have
the pg_dump -s option as well, which certainly ought to work. Looks like I have
a couple of working solutions. Thanks everyone!

--Wes Sheldahl

Bernie Holmes <holmes%msu(dot)edu(at)interlock(dot)lexmark(dot)com> on 08/13/2001 10:35:52 AM

To: "Wesley_Sheldahl/Lex/Lexmark.LEXMARK"@sweeper.lex.lexmark.com
cc: Justin Clift <justin%postgresql(dot)org(at)interlock(dot)lexmark(dot)com>,
pgsql-general%postgresql(dot)org(at)interlock(dot)lexmark(dot)com (bcc: Wesley
Sheldahl/Lex/Lexmark)
Subject: Re: [GENERAL] How can I view the definition of an existing trigger?

Wes,

Is this the kind of "trigger text" data you were interested in?

select relname as table_name,
tgname as trigger_name,
tgtype as trigger_type,
proname as trigger_function
from pg_class, pg_trigger, pg_proc
where pg_class.oid = tgrelid
and tgfoid = pg_proc.oid
and tgisconstraint = 'f'
order by table_name, trigger_name;

Bernie

wsheldah(at)lexmark(dot)com wrote:

>
>Thanks for the reply. I checked pg_trigger, but it only seems to have
>information *about* the trigger, and not the actual text of the trigger
command.
>As far as I can tell, the only way for me to hang on to trigger definitions is
>to put the create trigger commands in a file that I then source into psql. As
>for triggers already created, my best bet may be to drop what's there and
>recreate it so I know exactly what it does. Unless anyone has a better
idea....
>
>
>
>
>Justin Clift <justin%postgresql(dot)org(at)interlock(dot)lexmark(dot)com> on 08/11/2001
>04:59:52 PM
>
>To: "Wesley_Sheldahl/Lex/Lexmark.LEXMARK"@sweeper.lex.lexmark.com
>cc: (bcc: Wesley Sheldahl/Lex/Lexmark)
>Subject: Re: [GENERAL] How can I view the definition of an existing trigger?
>
>
>Hi Wes,
>
>Not sure exactly, but in theory it would be stored in one of
>PostgreSQL's special pg_* tables. So, also in theory, if you can
>isolate where they're stored, you might be able to find it.
>
>:-)
>
>Regards and best wishes,
>
>Justin Clift
>
>
>wsheldah(at)lexmark(dot)com wrote:
>
>>Is there any way short of a full database dump to view the "CREATE TRIGGER"
>>statement of a trigger after it's been created, preferable via a command line
>>tool like psql? Is it accessible via any of the GUI tools out there? Thanks,
>>
>>Wes
>>
>>---------------------------(end of broadcast)---------------------------
>>TIP 4: Don't 'kill -9' the postmaster
>>
>
>--
>"My grandfather once told me that there are two kinds of people: those
>who work and those who take the credit. He told me to try to be in the
>first group; there was less competition there."
> - Indira Gandhi
>
>
>
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 5: Have you checked our extensive FAQ?
>
>http://www.postgresql.org/users-lounge/docs/faq.html
>

Browse pgsql-general by date

  From Date Subject
Next Message Tim Barnard 2001-08-13 16:01:23 Re: delete columns from table!
Previous Message John Trambakoulos 2001-08-13 14:42:03 Calling stored procedures.