> > update pg_language set lanplcallfoid=374578 where
> > lanname='plpgsql';
>
> > Is it correct ?
>
> Right.
Ok, it's working fine now.
Thanks you very very much.
Bye
Laurent
=
The misspelling master is on the Web.
_100 % Dictionnary Free !
//(
/ Dico / /
--- Tom Lane <[EMAIL PROTECTED]> a écrit :
> Well, that looks reasonable, but what's its OID?
> (should've asked for
> select oid,* from ...)
scheduling=# select oid, * from pg_proc where
proname='plpgsql_call_handler';
oid | proname| proowner | prolang |
proisinh | proistrus
Hi all,
Oups, I forgot to put the ML in copy of my reply :-(
[...]
> > ERROR: fmgr_info: function 16594: cache lookup
> failed
> Most likely this means something happened to the
> call handler function
> for plpgsql. Look in pg_language to see the
> "lanplcallfoid" value for
> plpgsql; is i
Hello!
On Thu, 7 Mar 2002, Tom Lane wrote:
[skip]
> The easiest way to get back to a working database is to UPDATE the
> pg_language row with the correct OID of the call handler function.
> I'd be interested to know how you got into this state, though.
pg_dumpall|psql -p5454 ?8) typical mistake
I don't know about details, but in the 7.2 PostgreSQL
documentation, at Schema Manipulation topic, says:
New CREATE OR REPLACE FUNCTIONS to alter existing
function (preserving the OID) (by Gavin Sherry)
I think that you need to use this new resource.
Juliano S. Ignacio
[EMAIL PROTECTED]
---
=?iso-8859-1?q?Laurent=20FAILLIE?= <[EMAIL PROTECTED]> writes:
>> The easiest way to get back to a working database is
>> to UPDATE the
>> pg_language row with the correct OID of the call
>> handler function.
> Hum, so I may try
> update pg_language set lanplcallfoid=374578 where
> lanname='plpg
=?iso-8859-1?q?Laurent=20FAILLIE?= <[EMAIL PROTECTED]> writes:
> scheduling=# select * from pg_proc where
> proname='plpgsql_call_handler';
>proname| proowner | prolang | proisinh
> | proistrusted | proiscachable | proisstrict |
> pronargs | proretset | prorettype | proargtypes |
[EMAIL PROTECTED] writes:
> All is working Ok but a call to an PL/SQL function which fails w/ the following code.
> ERROR: fmgr_info: function 16594: cache lookup failed
Most likely this means something happened to the call handler function
for plpgsql. Look in pg_language to see the "lanplcal
Laurent Faillie ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
cache lookup failed
Long Description
Hi all,
I have just upgraded my 1.7.3 database to 7.2, following documentation's instruction
(pg_dumpall + psql < dumpfile).
