Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id BAA42194 for ; Wed, 31 May 2000 01:58:48 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id BAA04922; Wed, 31 May 2000 01:58:37 -0400 (EDT) To: SL Baur cc: pgsql-sql@postgresql.org Subject: Re: Re: Pg/PLSQL Errors!! In-reply-to: References: <000530123634BP.00589@weba1.iname.net> <2495.959707175@sss.pgh.pa.us> Comments: In-reply-to SL Baur message dated "31 May 2000 13:31:23 +0900" Date: Wed, 31 May 2000 01:58:37 -0400 Message-ID: <4919.959752717@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200005/216 SL Baur writes: > Tom Lane writes: >> Uh, did you run the "createlang" script to install plpgsql into your >> database? It's not installed by default ... > Why isn't it installed by default? Just asking. Paranoia, mostly --- we weren't sure we wanted it to be enabled without an explicit decision by the dbadmin. I'm not sure I can point to any compelling reasons why it'd be dangerous, but on the other side it's not proven to be totally safe either. pltcl and plperl don't get installed by default either, and those I definitely wouldn't agree to enabling by default... they don't have enough track record. plpgsql is more of a borderline call. regards, tom lane