Thread: Re: Bug #608: cache lookup failed

Laurent FAILLIE <l_faillie@yahoo.com> writes:
>  scheduling=# select * from pg_proc where
> proname='plpgsql_call_handler';
>        proname        | proowner | prolang | proisinh
> | proistrusted | proiscachable | proisstrict |
> pronargs | proretset | prorettype | proargtypes |
> probyte_pct | pro
> perbyte_cpu | propercall_cpu | prooutin_ratio |
> prosrc        |             probin
>
----------------------+----------+---------+----------+--------------+---------------+-------------+----------+-----------+------------+-------------+-------------+----
> ------------+----------------+----------------+----------------------+---------------------------------
>  plpgsql_call_handler |        1 |      13 | f
> | t            | f             | f           |
> 0 | f         |          0 |             |         100
> |
>           0 |              0 |            100 |
> plpgsql_call_handler | /usr/local/pgsql/lib/plpgsql.sl

Well, that looks reasonable, but what's its OID?  (should've asked for
select oid,* from ...)

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.
I have to think that you dropped and recreated the handler function
without going through the full 'droplang'/'createlang' cycle.
        regards, tom lane

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, should be in FAQ mentioned
below. IMHO.


> http://www.postgresql.org/users-lounge/docs/faq.html



--
WBR, Yury Bokhoncovich, Senior System Administrator, NOC of F1 Group.
Phone: +7 (3832) 106228, ext.140, E-mail: byg@center-f1.ru.
Unix is like a wigwam -- no Gates, no Windows, and an Apache inside.

--- Tom Lane <tgl@sss.pgh.pa.us> 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 | proistrusted | proiscachable | proisstrict
| pronargs | proretset | prorettype | proargtypes |
probyte_
pct | properbyte_cpu | propercall_cpu | prooutin_ratio
|        prosrc        |             probin

--------+----------------------+----------+---------+----------+--------------+---------------+-------------+----------+-----------+------------+-------------+---------
----+----------------+----------------+----------------+----------------------+---------------------------------374578
|plpgsql_call_handler |        1 |      13 | 
f        | t            | f             | f
|        0 | f         |          0 |             |
100 |              0 |              0 |            100
| plpgsql_call_handler |
/usr/local/pgsql/lib/plpgsql.sl


> 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='plpgsql';

Is it correct ?

> I'd be interested to know how you got into this
> state, though.
> I have to think that you dropped and recreated the
> handler function
> without going through the full
> 'droplang'/'createlang' cycle.

Hum ... no.
As first step, I have removed my data directory (rm
-rf /postgres/scheduling), the init the new database
(initdb -D /postgres/scheduling) and then, reimport
old data.
As I saw this error, I've removed PLSQL (drop
procedural language plsql;) and I've recreate it ...
but w/ the same result.

That seems very strange to me, is I've done the same
steps on my test invironment (under HP-UX 10.20 this
time) w/o any problem :-(

I'm hoping it's only a mistake on my own and not an
HP-UX 11.0 issu ...

>             regards, tom lane

Bye,

Laurent


=====
The misspelling master is on the Web.  _________    100 % Dictionnary Free ! /        /(/  Dico  / /    Pleins d'autres
fautessur 
/________/ /    http://go.to/destroyedlolo
(#######( /
Quoi, des fautes d'orthographe! Pas possible ;-D.

___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com