From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
---|---|
To: | Jean-Michel POURE <jm(dot)poure(at)freesurf(dot)fr> |
Cc: | <pgsql-hackers(at)postgresql(dot)org>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] fmgr_info: function 20071: cache lookup failed |
Date: | 2002-02-21 20:54:50 |
Message-ID: | 20020221125337.H22089-100000@megazone23.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-general pgsql-hackers |
On Thu, 21 Feb 2002, Jean-Michel POURE wrote:
> Dear Stephan ,
>
> > Is 20071 the oid of the function in question?
> Yes, as from the error message. It is quite surprising.
Wanted to be sure it wasn't some other function that might be being
referenced therein.
> > Can you give a standalone example that gives the error?
> After updating a PLpgSQL function of a trigger on table foo with CREATE OR
> REPLACE using latest version of pgAdmin2.
>
> If I run "UPDATE TABLE foo SET foo_timestamp = 'now' WHERE .... sql clause"
> will return an error. It seems to be a migration problem.
Hmm, I just did a simple test of a before insert/update trigger and
updating with create or replace from psql and didn't have a problem. Can
you give the tables/functions involved?
From | Date | Subject | |
---|---|---|---|
Next Message | Jean-Michel POURE | 2002-02-21 21:01:01 | Re: [HACKERS] fmgr_info: function 20071: cache lookup failed |
Previous Message | Jean-Michel POURE | 2002-02-21 20:23:39 | Re: [HACKERS] fmgr_info: function 20071: cache lookup failed |
From | Date | Subject | |
---|---|---|---|
Next Message | Tim Barnard | 2002-02-21 20:55:27 | Re: using libpq++.h |
Previous Message | Jason Earl | 2002-02-21 20:36:33 | Re: ANY GOOD USER'S GUIDE ONLINE?? (with simple examples) |
From | Date | Subject | |
---|---|---|---|
Next Message | Jean-Michel POURE | 2002-02-21 21:01:01 | Re: [HACKERS] fmgr_info: function 20071: cache lookup failed |
Previous Message | PG Explorer | 2002-02-21 20:40:10 | Re: [HACKERS] foreign key is from different tables - what to do? |