createlang(1) [suse man page]
CREATELANG(1) PostgreSQL Client Applications CREATELANG(1) NAME
createlang - define a new PostgreSQL procedural language SYNOPSIS
createlang [ connection-option... ] langname [ dbname ] createlang [ connection-option... ] [ --list ] [ -l ] dbname DESCRIPTION
createlang is a utility for adding a new programming language to a PostgreSQL database. createlang is just a wrapper around the CREATE LANGUAGE [create_language(7)] command. OPTIONS
createlang accepts the following command-line arguments: langname Specifies the name of the procedural programming language to be defined. [-d] dbname [--dbname] dbname Specifies to which database the language should be added. The default is to use the database with the same name as the current sys- tem user. -e --echo Display SQL commands as they are executed. -l --list Show a list of already installed languages in the target database. createlang also accepts the following command-line arguments for connection parameters: -h host --host host 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. -p port --port port Specifies the TCP port or local Unix domain socket file extension on which the server is listening for connections. -U username --username username User name to connect as. -w --no-password Never issue a password prompt. If the server requires password authentication and a password is not available by other means such as a .pgpass file, the connection attempt will fail. This option can be useful in batch jobs and scripts where no user is present to enter a password. -W --password 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 authentica- tion. However, createlang will waste a connection attempt finding out that the server wants a password. In some cases it is worth typing -W to avoid the extra connection attempt. ENVIRONMENT
PGDATABASE PGHOST PGPORT PGUSER Default connection parameters This utility, like most other PostgreSQL utilities, also uses the environment variables supported by libpq (see in the documentation). DIAGNOSTICS
Most error messages are self-explanatory. If not, run createlang with the --echo 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 droplang(1) 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
droplang(1), CREATE LANGUAGE [create_language(7)] Application 2010-05-14 CREATELANG(1)
Check Out this Related Man Page
CLUSTERDB(1) PostgreSQL Client Applications CLUSTERDB(1) NAME
clusterdb - cluster a PostgreSQL database SYNOPSIS
clusterdb [ connection-option... ] [ [ --verbose ] [ -v ] ] [ --table | -t table ] [ dbname ] clusterdb [ connection-option... ] [ [ --all ] [ -a ] ] [ [ --verbose ] [ -v ] ] DESCRIPTION
clusterdb is a utility for reclustering tables in a PostgreSQL database. It finds tables that have previously been clustered, and clusters them again on the same index that was last used. Tables that have never been clustered are not affected. clusterdb is a wrapper around the SQL command CLUSTER [cluster(7)]. There is no effective difference between clustering databases via this utility and via other methods for accessing the server. OPTIONS
clusterdb accepts the following command-line arguments: -a --all Cluster all databases. [-d] dbname [--dbname] dbname Specifies the name of the database to be clustered. If this is not specified and -a (or --all) is not used, the database name is read from the environment variable PGDATABASE. If that is not set, the user name specified for the connection is used. -e --echo Echo the commands that clusterdb generates and sends to the server. -q --quiet Do not display progress messages. -t table --table table Cluster table only. -v --verbose Print detailed information during processing. clusterdb also accepts the following command-line arguments for connection parameters: -h host --host host 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. -p port --port port Specifies the TCP port or local Unix domain socket file extension on which the server is listening for connections. -U username --username username User name to connect as. -w --no-password Never issue a password prompt. If the server requires password authentication and a password is not available by other means such as a .pgpass file, the connection attempt will fail. This option can be useful in batch jobs and scripts where no user is present to enter a password. -W --password Force clusterdb to prompt for a password before connecting to a database. This option is never essential, since clusterdb will automatically prompt for a password if the server demands password authentica- tion. However, clusterdb will waste a connection attempt finding out that the server wants a password. In some cases it is worth typing -W to avoid the extra connection attempt. ENVIRONMENT
PGDATABASE PGHOST PGPORT PGUSER Default connection parameters This utility, like most other PostgreSQL utilities, also uses the environment variables supported by libpq (see in the documentation). DIAGNOSTICS
In case of difficulty, see CLUSTER [cluster(7)] and psql(1) for discussions of potential problems and error messages. The database server must be running at the targeted host. Also, any default connection settings and environment variables used by the libpq front-end library will apply. EXAMPLES
To cluster the database test: $ clusterdb test To cluster a single table foo in a database named xyzzy: $ clusterdb --table foo xyzzy SEE ALSO
CLUSTER [cluster(7)] Application 2010-05-14 CLUSTERDB(1)