Re: [HACKERS] plpgsql problem..

I used mklang.sql in the plpgsql directory to install the language.. It's
the same thing I used on the working devel server..

--
-- PL/pgSQL language declaration
--
-- $Header: /usr/local/cvsroot/pgsql/src/pl/plpgsql/src/mklang.sql.in,v 1.4
1999/05/11 22:57:50 tgl Exp $
--

create function plpgsql_call_handler() returns opaque
as '/usr/local/pgsql/plpgsql.so'
lib/language 'C';

create trusted procedural language 'plpgsql'
handler plpgsql_call_handler
lancompiler 'PL/pgSQL';

That's the contents of that file and /usr/local/pgsql/plpgsql.so is exactly
where plpgsql.so is.

----- Original Message -----
From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Mitch Vincent <mitch(at)venux(dot)net>
Cc: <hackers(at)postgreSQL(dot)org>; <sevo(at)ip23(dot)net>
Sent: Tuesday, February 01, 2000 11:08 AM
Subject: Re: [HACKERS] plpgsql problem..

> "Mitch Vincent" <mitch(at)venux(dot)net> writes:
> > This might sound like an ignorant question but how does one dump the
> > function catalog?
>
> Try
> select * from pg_proc where proname = 'functionOfInterest';
>
> I think Sevo has identified the problem though: the CREATE FUNCTION
> command for the plpgsql_call_handler function needs to give an exact
> path name. What you are showing looks like the command tried to use an
> environment variable and the substitution didn't happen. Better review
> the procedure you used to install plpgsql. I'd recommend using the
> createlang script, btw, not doing it by hand.
>
> regards, tom lane
>