From: Tom Lane <tgl@sss.pgh.pa.us>
To: jwieck@debis.com
Cc: alewis@themecca.net
Cc: apendleton@vgsinc.com
Cc: pgsql-sql@hub.org
Subject: Re: [SQL] plpgsql error
Date: Tue, 11 May 1999 10:28:38 -0400
Message-ID: <13418.926432918@sss.pgh.pa.us> (raw)
In-Reply-To: <m10h74Z-000EBXC@orion.SAPserv.Hamburg.dsh.de>
jwieck@debis.com (Jan Wieck) writes:
>> Change: as '${exec_prefix}/lib/plpgsql.so'
>> to: as '/usr/local/pgsql/lib/plpgsql.so'
>>
>> 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?
Actually, I thought the same until last night, when I realized that
mklang.sql is in fact being made wrong --- the ${exec_prefix} should
be expanded when the file is created, but it isn't. (There's another
bug in it too: .so is hardwired, when it should be DLSUFFIX.)
So now I think what's really going on is that people *are* faithfully
following the install directions, but it's not working because of this
screwup. Oops.
Fixing it is not quite as trivial as I first thought --- see related
messages in hackers list.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, jwieck@debis.com, alewis@themecca.net, apendleton@vgsinc.com, pgsql-sql@hub.org
Subject: Re: [SQL] plpgsql error
In-Reply-To: <13418.926432918@sss.pgh.pa.us>
References: <m10h74Z-000EBXC@orion.SAPserv.Hamburg.dsh.de> <13418.926432918@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox