X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org
Received: from localhost (av.hub.org [200.46.204.144])
	by postgresql.org (Postfix) with ESMTP id 1F9F09DC98C
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Fri, 24 Feb 2006 12:06:08 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 45568-02
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Fri, 24 Feb 2006 12:06:06 -0400 (AST)
X-Greylist: from auto-whitelisted by SQLgrey-
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
	by postgresql.org (Postfix) with ESMTP id 97AD89DC899
	for <pgsql-sql@postgresql.org>; Fri, 24 Feb 2006 12:06:05 -0400 (AST)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id k1OG62W0003650;
	Fri, 24 Feb 2006 11:06:02 -0500 (EST)
To: Achilleus Mantzios <achill@matrix.gatewaynet.com>
cc: pgsql-sql@postgresql.org
Subject: Re: After Trigger assignment to NEW 
In-reply-to: <Pine.LNX.4.44.0602241831280.19738-100000@matrix.gatewaynet.com> 
References: <Pine.LNX.4.44.0602241831280.19738-100000@matrix.gatewaynet.com>
Comments: In-reply-to Achilleus Mantzios <achill@matrix.gatewaynet.com>
	message dated "Fri, 24 Feb 2006 18:44:08 +0200"
Date: Fri, 24 Feb 2006 11:06:02 -0500
Message-ID: <3649.1140797162@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, score=0.111 required=5 tests=[AWL=0.111]
X-Spam-Score: 0.111
X-Spam-Level: 
X-Archive-Number: 200602/296
X-Sequence-Number: 24306

Achilleus Mantzios <achill@matrix.gatewaynet.com> writes:
> Is there a reason that the NEW values should remain unchanged in AFTER 
> row triggers?

By definition, an AFTER trigger is too late to change what was stored.
Use a BEFORE trigger.

			regards, tom lane