Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f2EIUvx60272 for ; Wed, 14 Mar 2001 13:30:57 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f2EIUtt28460; Wed, 14 Mar 2001 13:30:56 -0500 (EST) To: Tim Perdue cc: pgsql-sql@postgresql.org Subject: Re: Rule/currval() issue In-reply-to: <20010314121335.S670@mail.perdue.net> References: <20010314115015.R670@mail.perdue.net> <28311.984593358@sss.pgh.pa.us> <20010314121335.S670@mail.perdue.net> Comments: In-reply-to Tim Perdue message dated "Wed, 14 Mar 2001 12:13:35 -0600" Date: Wed, 14 Mar 2001 13:30:55 -0500 Message-ID: <28457.984594655@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200103/286 X-Sequence-Number: 1950 Tim Perdue writes: >> You probably should be using a trigger, not a rule at all. > OK - so another rule like this one, is probably ill-advised as well? It seems > a lot easier than going into the triggers: > CREATE RULE forum_delete_agg AS > ON DELETE TO forum > DO UPDATE forum_agg_msg_count SET count=count-1 > WHERE group_forum_id=old.group_forum_id; That seems OK offhand, although it's hard to guess whether it will be more or less efficient than a trigger. regards, tom lane