| From: | Jean-Michel POURE <jm(dot)poure(at)freesurf(dot)fr> |
|---|---|
| To: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
| 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 21:01:01 |
| Message-ID: | 200202212101.g1LL11FP005391@www1.translationforge |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general pgsql-hackers |
> 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.
Dear all,
Please disregard my previous message. In pgAdmin2, I dropped the old tables
and functions pgadmin_*. But going too fast, I also dropped
plpgsql_call_handler by error. What a fool ...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-02-21 21:52:37 | Re: FATAL 1: configuration file 'postgresql.conf' has wrong |
| Previous Message | Stephan Szabo | 2002-02-21 20:54:50 | Re: [HACKERS] fmgr_info: function 20071: cache lookup failed |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oliver Elphick | 2002-02-21 21:02:21 | Re: copy notice |
| Previous Message | Tim Barnard | 2002-02-21 20:55:27 | Re: using libpq++.h |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rich Shepard | 2002-02-22 00:53:56 | Re: data mining or statistical analysis with postgresql |
| Previous Message | Stephan Szabo | 2002-02-21 20:54:50 | Re: [HACKERS] fmgr_info: function 20071: cache lookup failed |