X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id BB7D5D1D46D for ; Tue, 20 Jan 2004 08:14:46 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 53638-06 for ; Tue, 20 Jan 2004 04:14:17 -0400 (AST) Received: from anchor-post-30.mail.demon.net (anchor-post-30.mail.demon.net [194.217.242.88]) by svr1.postgresql.org (Postfix) with ESMTP id A9E63D1D42F for ; Tue, 20 Jan 2004 04:14:15 -0400 (AST) Received: from mwynhau.demon.co.uk ([193.237.186.96] helo=mainbox.archonet.com) by anchor-post-30.mail.demon.net with esmtp (Exim 3.35 #1) id 1Air1Y-0003Sw-0U; Tue, 20 Jan 2004 08:14:16 +0000 Received: by mainbox.archonet.com (Postfix, from userid 529) id 6436017484; Tue, 20 Jan 2004 08:14:00 +0000 (GMT) Received: from client17.archonet.com (client17.archonet.com [192.168.1.17]) by mainbox.archonet.com (Postfix) with ESMTP id F213A17482; Tue, 20 Jan 2004 08:13:57 +0000 (GMT) From: Richard Huxton To: Neil Conway , Harald Fuchs Subject: Re: Trigger question Date: Tue, 20 Jan 2004 08:13:56 +0000 User-Agent: KMail/1.5 Cc: pgsql-performance@postgresql.org References: <400691EA.96598C34@t1.unisoftbg.com> <871xpvij42.fsf@mailbox.samurai.com> In-Reply-To: <871xpvij42.fsf@mailbox.samurai.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200401200813.57147.dev@archonet.com> X-Bogosity: No, tests=bogofilter, spamicity=0.000000, version=0.15.3 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/195 X-Sequence-Number: 5369 On Tuesday 20 January 2004 00:01, Neil Conway wrote: > Harald Fuchs writes: > > 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. > > Yeah, I didn't get around to implementing that. If anyone wants this > feature, I'd encourage them to step up to the plate -- I'm not sure > when I'll get the opportunity/motivation to implement this myself. I didn't think they'd be meaningful for a statement-level trigger. Surely OLD/NEW are by definition row-level details. -- Richard Huxton Archonet Ltd