Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [206.210.65.6]) by hub.org (8.9.3/8.9.3) with ESMTP id KAA24915 for ; Tue, 11 May 1999 10:29:55 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id KAA13420; Tue, 11 May 1999 10:28:39 -0400 (EDT) To: jwieck@debis.com (Jan Wieck) cc: alewis@themecca.net (Andy Lewis), apendleton@vgsinc.com, pgsql-sql@hub.org Subject: Re: [SQL] plpgsql error In-reply-to: Your message of Tue, 11 May 1999 09:35:27 +0200 (MET DST) Date: Tue, 11 May 1999 10:28:38 -0400 Message-ID: <13418.926432918@sss.pgh.pa.us> From: Tom Lane 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