pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Harald Fuchs <hf99@protecting.net>
To: pgsql-performance@postgresql.org
Subject: Re: Trigger question
Date: 16 Jan 2004 14:05:20 +0100
Message-ID: <pud69kf3hr.fsf@srv.protecting.net> (raw)
References: <400691EA.96598C34@t1.unisoftbg.com>
	<200401151610.38270.dev@archonet.com>
	<1022542776.20040115180811@evilazrael.de>

In article <1022542776.20040115180811@evilazrael.de>,
Evil Azrael <evilazrael@evilazrael.de> writes:

> That not, but perhaps a STATEMENT Level Trigger could help. It´s a new
> feature in 7.4.x and rather undocumented. http://www.postgresql.org/docs/current/interactive/sql-createtrigger.html
> "FOR EACH STATEMENT" probably this can help you a bit.

Does anyone know how to access the affected values for statement-level
triggers?  I mean what the "old" and "new" pseudo-records are for
row-level triggers.




view thread (15+ messages)  latest in thread

Message-ID: <pud69kf3hr.fsf@srv.protecting.net>
Permalink:  ../pud69kf3hr.fsf@srv.protecting.net/
Also on:    postgresql.org/message-id/pud69kf3hr.fsf@srv.protecting.net

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: hf99@protecting.net
  Subject: Re: Trigger question
  In-Reply-To: <pud69kf3hr.fsf@srv.protecting.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox