Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> wrote:
: 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.

Thanks. I also had to create the handler function as per the
documentation for creating new procedural language interfaces.

Boy, the documentation sure read to me like all that was supposed to
be done automatically by the Makefile when configured for pltcl.

Not a big deal, but it wasn't clear to me this had to be done for each
database created. Is this a bug in the documentation?

-- 
Patrick Logan    patrickdlogan(at)home(dot)com

In response to

• Re: [HACKERS] Problem enabling pltcl at 1999-09-08 17:30:10 from Lamar Owen

pgsql-docs by date

Next:	From: Tom Lane	Date: 1999-09-08 21:42:45
	Subject: Re: [HACKERS] Re: Problem enabling pltcl
Previous:	From: Lamar Owen	Date: 1999-09-08 17:30:10
	Subject: Re: [HACKERS] Problem enabling pltcl

pgsql-hackers by date

Next:	From: Edwin Ramirez	Date: 1999-09-08 21:05:38
	Subject: Re: [HACKERS] Postgres Performance
Previous:	From: Lamar Owen	Date: 1999-09-08 19:35:22
	Subject: Re: [HACKERS] PG_UPGRADE status?

pgsql-bugs by date

Next:	From: Tom Lane	Date: 1999-09-08 22:01:18
	Subject: Re: [BUGS] Set Transaction Isolation level bug
Previous:	From: Alois Maier	Date: 1999-09-08 18:21:06
	Subject: Set Transaction Isolation level bug