Message-Id: <m11P1pG-0003kLC@orion.SAPserv.Hamburg.dsh.de>
From: wieck@debis.com (Jan Wieck)
Subject: Re: [HACKERS] Problem enabling pltcl
To: lamar.owen@wgcr.org (Lamar Owen)
Date: Thu, 9 Sep 1999 12:53:10 +0200 (MET DST)
Cc: patrickdlogan@home.com, pgsql-hackers@postgreSQL.org
Reply-To: wieck@debis.com (Jan Wieck)
In-Reply-To: <37D69D22.8876C0C4@wgcr.org> from "Lamar Owen" at Sep 8,
	99 01:30:10 pm
Content-Type: text

>
> Patrick Logan wrote:
> >     ERROR: Unrecognized language specified in a CREATE FUNCTION:
> >     'pltcl'.  Recognized languages are sql, C, internal and the
> >     created procedural languages.
> >
> > The docs say that pltcl is enabled if it is built with the TCL
> > option. What am I missing?
>
> CREATE LANGUAGE (command line utility 'createlang').  See the regression
> test shell script (src/test/regress/regress.sh) for an example using
> plpgsql.  The PL's are not created and installed by default, apparently.

    Yepp  -  it's  a doc mistake because first I made it that way
    and we decided later not to install by default into template1
    and provide createlang instead.


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#========================================= wieck@debis.com (Jan Wieck) #