X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.193]) by svr1.postgresql.org (Postfix) with ESMTP id 6E9A530D6E1 for ; Tue, 10 Jun 2003 16:28:04 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (svr1.postgresql.org [64.117.224.193]) (amavisd-new, port 10024) with ESMTP id 14169-01 for ; Tue, 10 Jun 2003 13:27:53 -0300 (ADT) Received: from pns.mm.eutelsat.org (pns.mm.eutelsat.org [194.214.173.227]) by svr1.postgresql.org (Postfix) with ESMTP id C85FE30DF02 for ; Tue, 10 Jun 2003 13:27:51 -0300 (ADT) Received: from nts-03.mm.eutelsat.org (localhost [127.0.0.1]) by pns.mm.eutelsat.org (8.11.6/linuxconf) with ESMTP id h5AFSfD28698; Tue, 10 Jun 2003 17:28:41 +0200 Received: from GMENDOLA2 (gmendola2.mm.eutelsat.org [194.214.173.26]) by nts-03.mm.eutelsat.org (8.11.6/linuxconf) with SMTP id h5AGRaR30394; Tue, 10 Jun 2003 18:27:36 +0200 Message-ID: <012f01c32f6d$3b9495c0$152aa8c0@GMENDOLA2> From: "Mendola Gaetano" To: "Yudie" , References: <001b01c32f69$eda57120$8401a8c0@yudie> Subject: Re: trigger error Date: Tue, 10 Jun 2003 18:27:48 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Archive-Number: 200306/85 X-Sequence-Number: 13843 "Yudie" wrote: > Hi, > I',m trying to create trigger with plpgsql trigger function > then I got this error message when trigger executed: > Number: -2147467259 > Error while executing th query; > ERROR: fmgr_info: function 1546856080: cache lookup failed > Here is the function code: >CREATE FUNCTION TRIGGER_UPDATE_AXPRDT_STATUS() >RETURNS OPAQUE >[snipped] >LANGUAGE 'plpgsql'; >CREATE TRIGGER TRIGGER_AXPRDT_FUTURESTATUS >BEFORE UPDATE ON AXPRDT >FOR EACH ROW >EXECUTE PROCEDURE TRIGGER_UPDATE_AXPRDT_STATUS(); The errors mean that after the trigger definition you maded a modification on the function rebuilding it. Try to delete the trigger and define it again. The fact that you are using "RETURN OPAQUE" instead of "RETURN TRIGGER" means that you are using a Postgres version prior then 7.3.x. Using the version 7.3.x ( I suggest you the 7.3.3 ) you can define that funcion: "CREATE OR REPLACE .... " so you are not forced to delete it before and your problem should gone. Gaetano