Message-ID: <40C6D1FA.4010907@archonet.com>
Date: Wed, 09 Jun 2004 10:01:46 +0100
From: Richard Huxton <dev@archonet.com>
User-Agent: Mozilla Thunderbird 0.6 (X11/20040502)
MIME-Version: 1.0
To: phil@cobol-africa.com
Cc: pgsql-sql@postgresql.org
Subject: Re: Triggers
References: <NEBBKNKPCLAAGALDLMCBEEOPCHAA.phil@cobol-africa.com>
In-Reply-To: <NEBBKNKPCLAAGALDLMCBEEOPCHAA.phil@cobol-africa.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Philip J. Boonzaaier wrote:
> The technical reference gives an example of a trigger on a table - employee
> Just to test this, I have created the following table,
> CREATE TABLE employee
> (name VARCHAR(30),
> age int4,
> state VARCHAR(2),
> manager VARCHAR(3),
> adult VARCHAR(3)); 
> 
> The I created a simple Function, as follows :
> 
> CREATE FUNCTION trig_insert_update_check_emp() RETURNS opaque AS '

The "opaque" type has been split into several different ones, if you're 
using a recent version of PG, you'll want "RETURNS trigger".

[snip]
> Now, when I execute the following :
> 
> INSERT INTO employee (name,age,state,manager)
> VALUES ('sean',29,'tx','yes');
> 
> I get :
> 
> ERROR fmgr_info function 6264440 cache lookup failed

This usually means you redefined something - PG isn't smart enough (yet) 
to re-check all the dependencies in something like this. I'd guess you 
dropped/recreated the function after defining the trigger, yes?

The solution in older versions is to put the CREATE FUNCTION and CREATE 
TRIGGER in the same file so that you drop/recreate both together.

HTH
-- 
   Richard Huxton
   Archonet Ltd