Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 16075476DB1 for ; Mon, 13 Jan 2003 10:59:26 -0500 (EST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 05565476E3D for ; Mon, 13 Jan 2003 10:58:54 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.6/8.12.6) with ESMTP id h0DFwj5u025406; Mon, 13 Jan 2003 10:58:45 -0500 (EST) To: geoff@metalogicplc.com Cc: "Pgsql-Admin (E-mail)" Subject: Re: Function problem. In-reply-to: References: Comments: In-reply-to "Geoff Ellis" message dated "Mon, 13 Jan 2003 15:05:08 +0000" Date: Mon, 13 Jan 2003 10:58:44 -0500 Message-ID: <25405.1042473524@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/123 X-Sequence-Number: 6965 "Geoff Ellis" writes: > === ERROR: fmgr_info: function 696542: cache lookup failed ===== This is on 7.3? My first guess would have been that you deleted and recreated the function without recreating the trigger that references it. But 7.3 should not let you do that. > I've tried to change the return type to opaque and remove the RETURN 1; But > if the condition isn't true then I don't have a return. In an update trigger, you RETURN NEW in the normal case where you want the update to proceed. regards, tom lane