| From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
|---|---|
| To: | Kris Kiger <kris(at)musicrebellion(dot)com> |
| Cc: | <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Crazy Triggers |
| Date: | 2003-05-28 22:12:51 |
| Message-ID: | 20030528151115.V41165-100000@megazone23.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
sszabo(at)bigpanda(dot)com
On Wed, 28 May 2003, Kris Kiger wrote:
> This will probably be a quick question for some of you with more
> experience than I. When you define a trigger to occur before or after
> an event, does this mean that the trigger is spawned as part of the
> current event transaction, or is it completed as a seperate transaction
> after the event is processed? In advance, thanks for the help!
It's part of the same transaction. If I'm remembering the details right,
the before triggers happen right before the event, currently non-deferred
after triggers happen at the end of the statement that caused the event
(although this may change in the future) and deferred after triggers (for
deferred foreign keys) happen at the end of the transaction during the
commit.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | rakesh | 2003-05-29 04:06:55 | Identifying databases. |
| Previous Message | Divya Jain | 2003-05-28 21:15:41 | modifying system table |