c8h4/postgresql
1
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity

Residual cleanup from making pltcl unknown support always enabled.

Browse source
This commit is contained in:
Tom Lane 2001-10-13 15:24:23 +00:00
parent b2c37b4c51
commit f42b88d1b4
2 changed files with 3 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
src/Makefile.global.in
View file

@ -1,5 +1,5 @@
# -*-makefile-*-
# $Header: /cvsroot/pgsql/src/Makefile.global.in,v 1.139 2001/09/22 22:54:32 petere Exp $
# $Header: /cvsroot/pgsql/src/Makefile.global.in,v 1.140 2001/10/13 15:24:23 tgl Exp $
#------------------------------------------------------------------------------
# All PostgreSQL makefiles include this file and use the variables it sets,
@ -124,7 +124,6 @@ with_java = @with_java@
with_perl = @with_perl@
with_python = @with_python@
with_tcl = @with_tcl@
enable_pltcl_unknown = @enable_pltcl_unknown@
with_tk = @with_tk@
enable_odbc = @enable_odbc@
with_iodbc = @with_iodbc@

7
src/pl/tcl/modules/README
View file

@ -1,7 +1,4 @@
The module support over the unknown command requires, that
the PL/Tcl call handler is compiled with -DPLTCL_UNKNOWN_SUPPORT.
Regular Tcl scripts of any size (over 8K :-) can be loaded into
the table pltcl_modules using the pltcl_loadmod script. The script
checks the modules that the procedure names don't overwrite
@ -11,11 +8,11 @@
All procedures defined in the module files are automatically
added to the table pltcl_modfuncs. This table is used by the
unknown procedure to determine if an unknown command can be
loaded by sourcing a module. In that case the unknonw procedure
loaded by sourcing a module. In that case the unknown procedure
will silently source in the module and reexecute the original
command that invoked unknown.
I know, thist readme should be more explanatory - but time.
I know, this readme should be more explanatory - but time.
Jan