createlang1Applicationcreatelangdefine a new PostgreSQL procedural languagecreatelangcreatelangconnection-optionlangnamedbnamecreatelangconnection-option--list-ldbnameDescriptioncreatelang is a utility for adding a new
programming language to a PostgreSQL database.
createlang is just a wrapper around the
command.
Optionscreatelang accepts the following command-line arguments:
langname
Specifies the name of the procedural programming language to be
defined.
Specifies to which database the language should be added.
The default is to use the database with the same name as the
current system user.
Display SQL commands as they are executed.
Show a list of already installed languages in the target database.
createlang also accepts
the following command-line arguments for connection parameters:
Specifies the host name of the machine on which the
server
is running. If the value begins with a slash, it is used
as the directory for the Unix domain socket.
Specifies the TCP port or local Unix domain socket file
extension on which the server
is listening for connections.
User name to connect as.
Force createlang to prompt for a
password before connecting to a database.
This option is never essential, since
createlang will automatically prompt
for a password if the server demands password authentication.
However, createlang will waste a
connection attempt finding out that the server wants a password.
In some cases it is worth typing EnvironmentPGDATABASEPGHOSTPGPORTPGUSER
Default connection parameters
This utility, like most other PostgreSQL> utilities,
also uses the environment variables supported by libpq>
(see ).
Diagnostics
Most error messages are self-explanatory. If not, run
createlang with the
option and see under the respective SQL command
for details. Also, any default connection settings and environment
variables used by the libpq front-end
library will apply.
Notes
Use to remove a language.
Examples
To install the language pltcl into the database
template1:
$ createlang pltcl template1
Note that installing the language into template1
will cause it to be automatically installed into subsequently-created
databases as well.
See Also