From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | "Brian" <brian(at)mail(dot)pantalaimon(dot)net>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_trigger.tgtype question |
Date: | 2003-04-08 01:19:23 |
Message-ID: | 037601c2fd6c$e433a3c0$6500a8c0@fhp.internal |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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, but that's a ways off yet.
Chris
----- Original Message -----
From: "Brian" <brian(at)mail(dot)pantalaimon(dot)net>
To: <pgsql-hackers(at)postgresql(dot)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(at)mail(dot)pantalaimon(dot)net
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2003-04-08 01:24:37 | Re: Backpatch FK changes to 7.3 and 7.2? |
Previous Message | Doug Silver | 2003-04-08 00:15:07 | Re: [NOVICE] Timestamp with time zone change (error) in 7.3.2? |