Skip site navigation (1) Skip section navigation (2)

Re: Feature request from irc...

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
Cc: Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Feature request from irc...
Date: 2005-06-29 04:23:49
Message-ID: 4677.1120019029@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> writes:
> Is it possible for a pl/pgsql trigger function to look at the sql 
> command that caused it to be triggered?  If not, is this an idea?

What exactly is the use case for this?  It cannot have anything to do
with assuming that you know what has happened or will happen, since
you cannot know how the original query behavior has been modified by
triggers that fired before you did or will fire after you.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Robert TreatDate: 2005-06-29 04:28:34
Subject: Re: Implementing SQL/PSM for PG 8.2 - debugger
Previous:From: Tom LaneDate: 2005-06-29 04:18:07
Subject: Re: Odd message with initdb on latest HEAD

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group