Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 439149FB2F8 for ; Wed, 28 Mar 2007 13:17:20 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 47716-05 for ; Wed, 28 Mar 2007 13:17:09 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id B39B79FB514 for ; Wed, 28 Mar 2007 13:17:08 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id l2SGH6dv026420; Wed, 28 Mar 2007 12:17:06 -0400 (EDT) To: Ray Madigan cc: Pgsql-Sql Subject: Re: Rules with sequence columns In-reply-to: <460A96ED.9000001@madigans.org> References: <460A96ED.9000001@madigans.org> Comments: In-reply-to Ray Madigan message dated "Wed, 28 Mar 2007 08:25:17 -0800" Date: Wed, 28 Mar 2007 12:17:05 -0400 Message-ID: <26419.1175098625@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200703/336 X-Sequence-Number: 27974 Ray Madigan writes: > Does anyone have any suggestion? Use a trigger to propagate the data to the other table. You can't make this work reliably with a rule, because rules are macros and hence inherently subject to double-evaluation problems when dealing with volatile functions. regards, tom lane