X-Original-To: pgsql-performance@postgresql.org Received: from davinci.ethosmedia.com (unknown [209.10.40.251]) by postgresql.org (Postfix) with ESMTP id 0924F47655E for ; Thu, 6 Mar 2003 12:06:33 -0500 (EST) Received: from [63.195.55.98] (HELO spooky) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 2882891; Thu, 06 Mar 2003 09:06:23 -0800 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Organization: Aglio Database Solutions To: Andreas Pflug , pgsql-performance@postgresql.org Subject: Re: How to notice column changes in trigger Date: Thu, 6 Mar 2003 09:05:37 -0800 User-Agent: KMail/1.4.3 References: <3E6762AA.8070206@web.de> <1046966484.20270.94.camel@linda.lfix.co.uk> <3E6772C4.5010005@web.de> In-Reply-To: <3E6772C4.5010005@web.de> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200303060905.37760.josh@agliodbs.com> X-Archive-Number: 200303/41 X-Sequence-Number: 1339 Andreas, > This doesn't cover case 3, since UPDATE ... SET b=b will lead to > NEW.b=OLD.b Why do you care about SET b = b? And shouldn't this discussion be on the PGSQL-SQL list? -- Josh Berkus Aglio Database Solutions San Francisco