Thread: pg_trigger.tgtype question

pg_trigger.tgtype question

From
Brian
Date:
I was wondering if there was a way, given the information in pg_trigger,
specifically pg_trigger.tgtype, to find out on what events a trigger is
fired, and whether it is fired before or after those events.

I've looked through the code a little in src/backend/commands/trigger.c
and think I'm on the right track, thanks to some help given to me on the
#postgresql irc channel, but I'm not much of a C programmer and I'm not
very familiar with postgresql internals.

Basically I'm looking for a way to connect to a postgres database and get
back all the stored procs (which I can do), triggers (which I can do), and
when those triggers fire (which I haven't figured out).

Thanks.

Brian Knox
brian@mail.pantalaimon.net



Re: pg_trigger.tgtype question

From
"Christopher Kings-Lynne"
Date:
Hi Brian,

Just look at the pg_dump source code.

In 7.4, there will be a pg_get_triggerdef function that will return the entire CREATE TRIGGER statement for a trigger,
butthat's a ways off yet.
 

Chris

----- Original Message ----- 
From: "Brian" <brian@mail.pantalaimon.net>
To: <pgsql-hackers@postgresql.org>
Sent: Tuesday, April 08, 2003 3:39 AM
Subject: [HACKERS] pg_trigger.tgtype question


> 
> I was wondering if there was a way, given the information in pg_trigger,
> specifically pg_trigger.tgtype, to find out on what events a trigger is
> fired, and whether it is fired before or after those events.
> 
> I've looked through the code a little in src/backend/commands/trigger.c
> and think I'm on the right track, thanks to some help given to me on the
> #postgresql irc channel, but I'm not much of a C programmer and I'm not
> very familiar with postgresql internals.
> 
> Basically I'm looking for a way to connect to a postgres database and get
> back all the stored procs (which I can do), triggers (which I can do), and
> when those triggers fire (which I haven't figured out).
> 
> Thanks.
> 
> Brian Knox
> brian@mail.pantalaimon.net
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>