From: | jwieck(at)debis(dot)com (Jan Wieck) |
---|---|
To: | alewis(at)themecca(dot)net (Andy Lewis) |
Cc: | apendleton(at)vgsinc(dot)com, pgsql-sql(at)hub(dot)org |
Subject: | Re: [SQL] plpgsql error |
Date: | 1999-05-11 07:35:27 |
Message-ID: | m10h74Z-000EBXC@orion.SAPserv.Hamburg.dsh.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-sql |
>
> Edit: /usr/src/pgsql/postgresql-6.4.2/src/pl/plpgsql/src/mklang.sql
>
> Change: as '${exec_prefix}/lib/plpgsql.so'
> to: as '/usr/local/pgsql/lib/plpgsql.so'
>
> Then: psql your_db < mklang.sql
>
> This should really be part of the documentation as I wasted two days on
> this same problem a few weeks back.
And this became IMHO an FAQ. Should we avoid it by installing
PL/pgSQL and PL/Tcl (if built) by default in the template1
database during intidb? Installing it in template1 would
have the effect that it will be available after every
createdb.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#======================================== jwieck(at)debis(dot)com (Jan Wieck) #
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Meskes | 1999-05-11 08:23:29 | Re: [HACKERS] ecpg fixes |
Previous Message | Oleg Bartunov | 1999-05-11 06:45:24 | problem compiling 6.5 cvs (Linux, gcc 2.7.2, egcs 1.12) |
From | Date | Subject | |
---|---|---|---|
Next Message | Carlos Peralta Ramirez | 1999-05-11 11:21:30 | More problems with arrays !!!!! |
Previous Message | Bruce Momjian | 1999-05-10 21:38:16 | Re: [SQL] plpgsql error |