droplang [connection-option...] langname [dbname]
droplang [connection-option...] --list | -l [dbname]
droplang is a utility for removing an existing procedural language from a PostgreSQL database.
droplang is just a wrapper around the DROP EXTENSION SQL command.
| Caution |
droplang is deprecated and may be removed in a future PostgreSQL release. Direct use of the DROP EXTENSION command is recommended instead. |
droplang accepts the following command line arguments:
Specifies the name of the procedural language to be removed. (This name is lower-cased.)
Specifies from which database the language should be removed. 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.
Print the droplang version and exit.
Show help about droplang command line arguments, and exit.
droplang also accepts the following command line arguments for connection parameters:
Specifies the host name of the machine on which the server is running. If host begins with a slash, it is used as the directory for the Unix domain socket.
Specifies the Internet TCP/IP port or local Unix domain socket file extension on which the server is listening for connections.
User name to connect as.
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.
Force droplang to prompt for a password before connecting to a database.
This option is never essential, since droplang will automatically prompt for a password if the server demands password authentication. However, droplang 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.
Default connection parameters
This utility, like most other PostgreSQL utilities, also uses the environment variables supported by libpq (see Section 32.14).