Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id fBG24cm61845 for ; Sat, 15 Dec 2001 21:04:38 -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.4/8.11.4) with ESMTP id fBG24Ki11554; Sat, 15 Dec 2001 21:04:20 -0500 (EST) To: marc@oscar.eng.cv.net (Marc Spitzer) cc: pgsql-sql@postgresql.org Subject: Re: should this be a trigger or a rule? In-reply-to: References: Comments: In-reply-to marc@oscar.eng.cv.net (Marc Spitzer) message dated "Sun, 16 Dec 2001 00:16:52 +0000" Date: Sat, 15 Dec 2001 21:04:20 -0500 Message-ID: <11551.1008468260@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200112/159 X-Sequence-Number: 5982 marc@oscar.eng.cv.net (Marc Spitzer) writes: > I have 3 tables: pings, curr_state, ping_log and here is what I want > to happen: > when I insert a row into pings it checks to see if the ping was > sucessful or not. Anything that's most naturally described as driven by insert (or update or delete) of individual rows is best done as a trigger, IMHO. regards, tom lane