Re: [SQL] plpgsql error

From: jwieck(at)debis(dot)com (Jan Wieck)
To: michael(dot)j(dot)davis(at)tvguide(dot)com (Michael J Davis)
Cc: jwieck(at)debis(dot)com, alewis(at)themecca(dot)net, apendleton(at)vgsinc(dot)com, pgsql-sql(at)hub(dot)org
Subject: Re: [SQL] plpgsql error
Date: 1999-05-11 14:27:45
Message-ID: m10hDVa-000EBXC@orion.SAPserv.Hamburg.dsh.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

Michael J Davis wrote:

>
> Gets my vote. Should we also consider doing this for Perl too? I turn them
> all on in my installation. I don't use either Perl or TCL yet but want to
> make sure they are available if 1) I ever want to or 2) a need arises that
> is would be better suited to either Perl or TCL.
>
> 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.

I only spoke about installing the procedural languages that
got built (due to the config options used) by default in the
template1 database. NOT to turn on the config options by
default.

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) #

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Tom Lane 1999-05-11 14:28:38 Re: [SQL] plpgsql error
Previous Message Michael J Davis 1999-05-11 14:23:32 RE: [SQL] plpgsql error