| From: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Release changes |
| Date: | 2003-08-05 17:40:17 |
| Message-ID: | 20030805103424.E62947-100000@megazone.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 5 Aug 2003, Bruce Momjian wrote:
> How are statement level triggers supposed to work? Are they just
> triggers deferred until the end of the statement? You mentioned access
> to the affected rows, but I don't understand how that is supposed to
> happen.
ILTM like you're supposed to (optionally) get table references that
presumably contains the OLD/NEW rows. Before someone jumps on me for
putting optionally up there, it's a create trigger time option. And
the old/new table references are not available for before triggers.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jenny - | 2003-08-05 17:57:23 | Re: this is in plain text (row level locks) |
| Previous Message | Andrew Dunstan | 2003-08-05 17:37:18 | Re: logging stuff |